... >` but wraps the post/page content in a `
...
`. You can do two things to solve this:
A. Change your theme and stylesheet so the post/page content div has either `class="hentry"` or ``. TIP: Take a look at how it is done in the Default theme included in each WordPress release. But this might involve some real timeconsuming tinkering with your stylesheet and several theme template files.
B. Change the source of wp-content/plugins/highlight-search-terms/hlst.php so that the array starting on line 55 contains your main content ID or class name. In the above example that can be either `'#common',` or `'.content',` where a prefix '#' is used for ID and '.' for class.
C. Switch to a theme that does abide by the current WordPress conventions :)
== Screenshots ==
1. An example image provided by [How to Highlight Search Terms with jQuery](http://weblogtoolscollection.com/archives/2009/04/10/how-to-highlight-search-terms-with-jquery/ "How to Highlight Search Terms with jQuery | Weblog Tools Collection") on which this plugin is largely based.
== Other Notes ==
Many blogs are already top-heavy with all kinds of resource hungry plugins that require a lot of options to be set and subsequently more database queries. The Highlight Search Terms plugin for WordPress is constructed to be as low impact / low resource demanding as possible, keeping server response and page load times low. This is done by going without any back-end options page, no filtering of post content and no extra database entries. Just two action hooks are used: wp_footer and wp_head. The rest is done by jQuery javascript extention and your own CSS.
To get you started with your own CSS styling that fits your theme, see the following examples.
= CSS Instructions =
Go in your WP admin section to Themes > Edit and find your Stylesheet. Scroll all the way to the bottom and add one of the examples (or your modification of it) on a fresh new line.
= Basic CSS Examples =
.hilite { background-color:#D3E18A }
For a moss green background highlighting.
.hilite { background-color:yellow }
Yellow background highlighting.
.hilite { background-color:#9CD4FF; font-weight:bold }
A light blue background with bold font.
.hilite { background-color:#FFCA61; color:#000000 }
Orange background with black font.
For more intricate styling, see the advanced example below.
= Advanced CSS Example =
If you want to give different terms used in a search phrase a different styling, use the class "term-N" where N is a number starting with 0, increasing 1 with each additional search term, to define your CSS rules. The below example will make every instance of any term used in the query show up in bold text and a yellow background except for any instance of a second, third and fourth term which will have respectively a light green, light blue and orange background.
.hilite { background-color:yellow; font-weight:bold } /* default */
.term-1 { background-color:#D3E18A } /* second search term only */
.term-2 { background-color:#9CD4FF } /* third search term only */
.term-3 { background-color:#FFCA61 } /* fourth search term only */
Keep in mind that for the _first_ search term the additional class "term-0" is used, not "term-1"!
= Known issues =
1. If your theme does not wrap the main content section of your pages in a div with class "hentry", this plugin will not work for you out of the box. However, you can _make_ it work. See the last of the [FAQ's](http://wordpress.org/extend/plugins/highlight-search-terms/faq/) for an explanation.
2. [Josh](http://theveganpost.com) pointed out a conflict with the [ShareThis button](http://sharethis.com/wordpress). I have no clue why this happens but since version 0.5 jQuery is used in so called NoConflict mode. Please let me know if the problem still exists. Thanks!
3. When search engine referrer is using SSL (notice the https:// in the URL, usually when logged in as Google user) and your WordPress site is not, then the search terms cannot be determined. There is no way to get around that issue.
Thank you, [Jason](http://wordpress.org/support/profile/412612) for pointing out a bug for IE7+, fixed in 0.2.
Please provide me with a bugreport, suggestion or question if you run into any problems!
== Changelog ==
= 1.2.2 =
Date 2012-10-11
* Search terms wrapped in double qoutes now considered as single term
* Caching compatible
* Second click highlighting: not only on the search results page but also inside any of the found pages
* Speed improvement
* More search engines supported
* BUGFIX: Undefined variable: cache_compat
= 1.2.1 =
Date 2012-07-27
* BUGFIX: non HTML5 browser (IE8 and older) support failing
= 1.2 =
Date 2012-07-25
* NEW: Caching (WP Super Cache) compatibility
* NEW: Highlights not only on WP search results page but also one click deeper inside any of the found pages
* NEW: Search terms wrapped in double qoutes now considered as single term
* support many more search engines: AOL, Dogpile, Search.com, Goodsearch.com, Mywebsearch.com, Webcrawler.com, Info.com
* rebuilt as Class
* plugin speed improvements
= 0.8 =
Date 2012-04-18
* HTML5 mark tag support
* No more word boundery limit for non-latin based languages compatibility
= 0.7 =
Date: 2011-01-03
* BUGFIX: conflict with Cufon script
= 0.6 =
Date: 2010-09-06
* limit highlited search terms to word boundery
* added Bing, Ask, Baidu and Youdao search engines
* now automatically check for and highlights in multiple theme div areas
* BUGFIX: cloning first result excerpt to all excerpts
= 0.5 =
Date: 2010-08-07
* using jQuery in no-conflict mode and $hlst instead of $ to avoid conflict with prototype
* split variables and moved js extention in compacted form to static file
* moved jQuery and extention to footer + only when actually needed for faster pageload
= 0.4 =
Date: 2010-04-07
* fixed Regular Expression to allow parts of words to be highlighted
* search term wrapping limited to .hentry divs
= 0.3 =
Date: 2009-04-16
* Bugfix for Firefox 2+ (forcefully highlights now limited to div#content)
= 0.2 =
Date: 2009-04-15
* Allowing for multiple search term styling + Bugfix for IE7 / IE8
= 0.1 =
Date: 2009-04-14
- Basic plugin aimed at low impact / low resource demand on your WP installation using client side javascript.