Highlight Search Terms
Highlights search terms within WordPress generated search results, both on the search results page and on each linked post page itself. This plugin is light weight and has no options. It started as very simple fusion between How to Highlight Search Terms with jQuery – theme hack by Thaya Kareeson and Search Hilite by Ryan Boren. It has since evolved with many optimizations, HTML5 and other plugin compatibility. Since version 1.6 it no longer depends on the jQuery library. Features Click through highlights: Highlights not only on WP search results page but also one click deeper inside a post page Character and case insensitive (lenient) highlighting Caching (WP Super Cache) compatibility Search terms wrapped in double quotes now considered as single term Compatible with: Woocommerce Search Filter Pro BuddyPress bbPress What does it do? This low impact plugin finds all search terms on a search results page inside each post and highlights them with a ... tag. Note that N is a number starting with 0 for the first term used in the search phrase increasing 1 for each additional term used. Any part of a search phrase wrapped in quotes is considered as a single term. What does it NOT do? There are no CSS style rules set for highlighting. You are free to use any styling you wish but to make the highlights visible in browsers that do not support HTML5 like Internet Explorer 8 or older you absolutely need to define at least one rule. Modern HTML5 browsers will use their own highlighting style by default, which usually is a yellow marker style background. So what do I need to do? In most cases, it should just work. But you can do two things to ensure backward browser and theme compatibility: Define CSS rules: There are no configuration options and there is no predefined highlight styling. You are completely free to define any CSS styling rules in your themes main stylesheet (style.css) or the Custom CSS tab if the WordPress theme customizer. You can find basic instructions and CSS examples in the FAQ’s. Check your theme: In most up to date themes (including WP’s own default theme) post and page content is shown inside a div with class hentry. This means search terms found in post and page content will be highlighted but not similar terms that accidentally show in the page header, sidebar or footer. If your current theme does not use the hentry class (yet), this plugin will look for IDs content, main and finally wrapper but if none of those are found, it will not work for you out of the box. See the last of the FAQ’s for ways to make it work. Available hooks and filters hlst_query_vars – The array of WordPress query variables that the plugin will identify as a search query. Must return an array. Default: ['search_terms','bbp_search'] (WordPress abd bbPress search) hlst_input_get_args – An array of GET variables that the plugin will identify as a search query. Must return an array. Default: ['hilite'] (for click-through highlighting) hlst_selectors – The array of possible HTML DOM element identifiers that the script will try. The first viable identifier it finds elements of will be scanned for search terms to mark, the rest is ignored. So the order is important here! Start with the element closest to, but still containing all the post/page title, excerpt or content. hlst_events – The array of DOM event listeners that the inline script will watch for. Default: ['DOMContentLoaded','post-load'] (on Document Ready and for Jetpack Infinite Scroll and others). hlst_inline_script – The inline script that will be added to the plugin script file. Can be used to add to or alter the inline script. Must return a string. Known issues & development If your theme does not wrap the main content section of your pages in a div with class “hentry” or HTML5 article tags, this plugin might not work well for you out of the box. However, you can make it work. See the last of the FAQ’s for an explanation. Josh pointed out a conflict with the ShareThis buttons plugin. Since then, that plugin has been completely rewriten so please let me know if the problem still exists. Thanks! Please file bug reports and code contributions as pull requests on GitHub.
Top keywords
- search17×2.34%
- page9×1.24%
- terms7×0.96%
- theme7×0.96%
- array6×0.83%
- css6×0.83%
- post6×0.83%
- script6×0.83%
- search terms6×0.83%
- content5×0.69%
- default5×0.69%
- highlights5×0.69%
search-into-subcategories
For Demo go here http://codescar.eu/projects/search-into-subcategories Search-Into-Subcategories plugin allows you to make a select-search shortcode for your own categories. You can use if everywhere you want and make a tree structure for your categories. [search-into-subcategories] Arguments you can pass: parent_category Default is 0 You can list only sub categories of the category id you give here. With 0 lists alla categories max_depth Default is 2 How many subcategories (children of the parent_category) to display, at least 1. search_input Default is 1 Display a text input for search. (You can turn it off with 0 value) labels Default is Labels for the inputs. Give them in the order you want with '|' as separator. example: Category1|Category2|Text search_text Default is Search The text to display in search button. hide_empty Default is 1 Hide categories without content, set to 0 to display all! exclude Default is Category IDs to exclude from listing. Separate them with ','. Example: 6,7,13 show_date_ranges Default is 0 Show from/to date ranges to filter publish date. Set it to 1 to use it. dates_format Default is DD-MM-YYYY It requires the show_date_ranges to be enabled. It uses Pikaday JS Library (a small one) to create a datepicker and manage the date formatting. (If you use spaces into the format, wrap it into single quotes 'like this'). (The formatting is generated by momentJS https://momentjs.com/docs/#/displaying/ ) custom_field Default is null List of custom meta-fields to search in (it will create a new input for every meta-field. ( Use , as separator, example: field1,meta_key,etc ) custom_field_labels Default is null List for labels in custom meta fields text input. (Use | as separator, example: name1|name2|etc) custom_post_types Default is null Post type to filter results posts_per_page Default is null Set result page posts per page custom_taxonomy Default is category Set custom taxonomy to walk. Example: [search-into-subcategories parent_category=0 max_depth=3 search_input=1 labels=cat1|cat2|cat3|Text search_text=Find hide_empty=0 exclude=7,6 show_date_ranges=1 custom_field=author,my_custom custom_field_labels=Author|Custom custom_post_types=documents posts_per_page=10 custom_taxonomy=my_taxonomy dates_format=YYYY-MM-DD]
Top keywords
- default14×3.63%
- custom13×3.37%
- search8×2.07%
- text