SearchWP News

View plugin news, catch up on recent releases, and find out what's coming to SearchWP!

SearchWP 2.9 brings a completely revamped settings UI. The interface updates also afforded the ability to make optimizations in other areas as well. This article aims to outline what’s new!

The settings UI continues on the premise that there is a Default search engine used for native WordPress searches. Along with the Default engine any number of supplemental engines can be created. All engines share the same configuration options, the only difference being that supplemental engines have a label so you can differentiate them.

ūüö® The Panic Button

Updating to SearchWP 2.9 did NOT alter your settings or your index

Please note that simply updating to SearchWP 2.9 has not made any changes to your existing settings nor has it altered your index in any way. The biggest change you’ll see is that your Weights look relatively “low” ‚ÄĒ because they are. There’s a new default weighting scale, and the old default weights were lower across the board than the new weights. You’re welcome to update your weights if you’d like but you do not have to!

A hook as been implemented that allows you to revert back to the pre-2.9 settings UI. To use the legacy UI simply add this hook to your theme’s functions.php and reload the page:

add_filter( 'searchwp_legacy_settings_ui', '__return_true' );

You can also add this hook to prevent the engine rules from being applied to the index, which was also added in 2.9:

add_filter( 'searchwp_indexer_apply_engines_rules', '__return_false' );

Note: By nature, the legacy UI will be missing some of the other improvements made to SearchWP 2.9

Enabling Post Types

There was some understandable confusion about the checkboxes over time, especially when it came to saving engines and subsequently making additional tweaks. When the settings screen reloaded, the top post type was given focus (as opposed to the post type you were working with prior to saving) which caused some headaches for customers.

Controls to add and remove post types from an engine

Gone are checkboxes to enable/disable post types in favor of a new approach entirely: if a post type is listed within an engine configuration it will be included in results. If a post type is not listed within an engine configuration it will not be included in results.

Sliders for Weights

Another point of confusion over the past few years has been the numeric value for assigned Weights. To improve the experience of working with Weight adjustments, you can now simply interact with the available slider instead of having to enter in a numeric value. When sliding, a tooltip is shown to provide a bit more context:

Using the Weight slider

By default the maximum weight is 100, so if you haven’t customized your weights since installing SearchWP your sliders may all sit at the low end of the scale. This is perfectly fine! The underlying implementation of the weighting system is still exactly the same, so you can continue using your settings as-is.

If you have customized your weights and have used a weight higher than 100, there is a new hook available to set the maximum weight for the sliders: searchwp_weight_max

Post type rules

Each post type has a set of rules that allow you to refine both what is excluded from the index as well as what the index is limited to. Exclusions were always available in SearchWP but prior to version 2.9 the exclusions applied only to the search algorithm. This made management of engine settings more straightforward, but it also meant that the index could have content that did nothing but take up extra space.

As of SearchWP 2.9 post type rules directly apply to the indexing process in addition to the search algorithm. This means that if you’re making use of post type rules your search results might have a free optimization waiting should you decide to rebuild your index. As the indexer runs, it checks the rules you have in place for all engines and indexes only the bare minimum so as to keep the index itself as lean as possible.

That’s not all! Prior to SearchWP 2.9 you could only exclude content, but now you can also limit to content as well!

As of SearchWP 2.9 you can also limit to certain taxonomy terms

These rules now apply to both the indexing process and the search algorithm. As a result, SearchWP will let you know when your index should be rebuilt so as to inherit the optimizations put in place by your engine(s)

Rebuilding the index now takes place in real time without leaving the settings screen, so you can keep your eye on it if you’d like! ūü§ď

Other details

All of the other underlying concepts of SearchWP remain the same in version 2.9 but the updates to the settings interface will hopefully squash any confusion when it comes to getting things¬†just right. While there’s a lot to see in the new UI I hope the low level behind-the-scenes updates are a welcome addition too!

SearchWP version 2.8.15 is now available and is a recommended update to all active license holders. This is a bugfix and maintenance release which will benefit all SearchWP customers.

  • [Improvement] Better handling of regex pattern matches
  • [Fix] Fixes an issue where Media-only default engines did not fully build index
  • [Update] Updated updater

Redirects version 1.0.4 is a bugfix release that is recommended for all active license holders.

  • [Fix] Fixed an issue that truncated query parameters on destination URLs

WooCommerce Integration has seen a number of updates since the last News post, each has been a maintenance release to improve compatibility with WooCommerce.

Full changelog since the last update:

1.1.17

  • [Fix]¬†Better enforcement when no results are found
  • [Improvement]¬†Prevent redundant search from running
  • [Update]¬†Updated updater

1.1.16

  • [Improvement]¬†Better integration with WooCommerce native sorting

1.1.15

  • [Fix] Fixed an issue that prevented final results from showing in some cases

1.1.14

  • [Fix] Fixed an issue that prevented final results from showing in some cases

1.1.13

  • [Fix] Fixed an issue with product visibility in WooCommerce 3.0

SearchWP’s Term Highlight extension has been improved to better handle multi-word exact matches. This maintenance release is recommended for all active license holders.

There is an extensive backlog of updates since the last News post, full changelog posted here for reference:

2.1.7

  • [Fix]¬†Fixes an issue where partial matches may result in less accurate global excerpts
  • [Improvement]¬†Improved exact match processing
  • [Update]¬†Updated updater

2.1.5

  • [Update]¬†Highlighting no longer auto-applies for searches in the Dashboard

2.1.4

  • [Fix]¬†Fixed improper variable initialization that may have resulted in an Error (props Vlad)

2.1.3

  • [Improvement]¬†Better support for serialized data when building global excerpt
  • [Fix]¬†Prevent global excerpt generation from defaulting to filename

2.1.2

  • [Fix]¬†Fixed an issue with overly aggressive tokenizing which may have resulted in a loss of formatting
  • [New]¬†New filter searchwp_term_highlight_occurrence to offset where highlighting begins (default is occurrence 1)
  • [Fix]¬†Improved handling of whole match check, resolved PHP Warning
  • [Update]¬†Updated updater

2.1.1

  • [Fix]¬†Better handling of operations with empty search string
  • [Fix]¬†Fixed PHP Warning
  • [Fix]¬†Fixed an issue when finding global excerpts with multiple terms flanked by encoded punctuation

2.1.0

  • [Improvement]¬†Check for whole matches before parsing individual search terms
  • [Improvement]¬†Better handling of pattern matches
  • [Update]¬†Updated updater

2.0.13

  • [New]¬†New filter searchwp_th_auto_highlight_content to disable automatic highlighting
  • [Improvement]¬†More priority given to exact search matches
  • [Improvement]¬†Improved performance of highlighting operation

2.0.12

  • [Fix]¬†Better highlight restriction when other SearchWP extensions are active
  • [Fix]¬†Better tokenizing when extracting highlight matches

2.0.11

  • [Improvement]¬†Apply appropriate filters for better interoperation with other SearchWP Extensions
  • [Change]¬†More appropriate initialization timing
  • [Update]¬†Updated updater

2.0.10

  • [Fix]¬†PHP Warning cleanup

2.0.9

  • [Fix]¬†PHP Warning cleanup

2.0.7

  • [Fix]¬†Fixed an issue that forced highlights to be lowercase

2.0.6

  • [Improvement]¬†Better Shortcode handling
  • [Improvement]¬†Better UTF-8 support
  • [Improvement]¬†Better handling of keyword stems
  • [Fix]¬†Fix an issue where redundant filter calls were in place

2.0.5

  • [Fix]¬†Fixed a bug that gave too much priority to manually populated Excerpts when the Excerpt did not have a highlight match but the post content did

2.0.4

  • [Fix]¬†Fixed a bug that ignored a specified Custom Field from which to generate a global excerpt

2.0.3

  • [New]¬†New filter searchwp_th_partial_matches which enables highlighting of partial term matches

2.0.2

  • [Fix]¬†Fixed PHP Warning, better short circuit when post ID is not defined

2.0

  • [Improvement]¬†Support for automatic updates based on your SearchWP license key

1.8.8

  • [Improvement]¬†Better word matching at boundaries
  • [New] Added Shortcode handling

SearchWP version 2.8.14 again improves compatibility with other plugins and is a recommended update for all customers.

  • [Improvement] Additional checks to prevent overrun with other plugins

A regression was introduced in version 2.8.11 that 2.8.13 resolves

  • [Fix] Fix a regression introduced to SWP_Query in 2.8.11 that may have prevented pagination from working as expected

Main query check improvements are also included in this release

  • [Fix] Additional main query checks to improve plugin compatibility

SearchWP’s Related extension has been updated to version 1.0.2 which is a small bugfix and maintenance release which is recommended for all users.

  • [Fix] Prevent PHP(<5.5) Fatal error Can't use function return value in write context
  • [Fix] Newly published entries are no longer automatically skipped if no keywords are entered, will use fallbacks by default
  • [Fix] Implementation of searchwp_related_excluded_post_types filter is now applied correctly and works
Fix Search on Your Site. No Coding Required!

Now you can utilize all of the content that's gone unrecognized by native WordPress search instantly with SearchWP

Get SearchWP