Forums › Forums › Search & Filter Pro › WordPress 4.2 Update
- This topic has 12 replies, 4 voices, and was last updated 9 years, 7 months ago by Ross.
-
Ross Moderator(Private) May 1, 2015 at 9:51 pm #16426
Soooooo
I’m confident the latest issues caused by WP 4.2 are now resolved in the latest version of Search & Filter (1.4.3), however I’m seeing a lot of posts of people panicking and immediately assuming that there are problems with the latest version of Search & Filter with WordPress…
So, you are having problems, and if Search & Filter is not to blame then what could it be!?
Well, there are a few possibilities…
1) You have updated Search & Filter from an older version or this is the first time you’ve updated Search & Filter in a while (there is roughly a release every month)
Well, upgrading from a really old version of S&F can have some undesirable effects – there have been many changes and improvements over time, and if you’ve been keeping up with updates, you’ll have hopefully not noticed any problems upgrading, but if you’ve upgraded from an old version I suggest to try the following:
a) go through all the new settings thoroughly, check the new options are set how you want… please also check and read the docs – theres definitely room for improvement but they’ve been updated to cover some of the important newer features.
b) some of the biggest changes revolve around the “display results” tab – to reset some of the “under the hood” settings I recommend changing this method on your search form (ie switch from “archive” to “shortcode”), save the form, and then switch back to the method you wish to use, and save the form again.
If you are still having problems after checking through the docs and trying the above, please open a new support ticket.
2) When upgrading WP to 4.2, you’ve also updated a bunch of other plugins
Well guess what, if you’ve upgraded WordPress, upgraded a lot of plugins on your site and have no formal testing method in place – its quite likely something else has gone wrong in your site which in turn is causing issues with S&F.
Once of the biggest problems is JavaScript errors – check your JavaScript console to see if there are any errors, and fix them. Then test S&F again. If the errors are coming from S&F, please open a new ticket and provide these details.
There may be other errors at work here though, which are not JS related and may be harder to track down. First you should Enable debugging and then install the Debug Bar plugin. Resolve any errors found here and test again. If any errors are being generated from Search & Filter then please open a new ticket.
3) Last but not least, a good tip for ensuring your search form is not misconfigured (there are settings under the hood which users don’t have access to)..
Something that is always worth a shot, if S&F is not behaving as expected, from an upgrade or otherwise, is to recreate your search form – don’t duplicate it, but create a new search form, and apply all the same settings as you would – this will certainly help isolate any problems with specific search and would hopefully fix any misconfiguration issues.
I’ll add more things to this list as I think of them. The real purpose of this post is to make you aware that when making big changes to your site such as a WP upgrade, all kinds of things *could* go wrong – especially if you’ve also updated a bunch of plugins – and although you perceive the problem to be with a specific plugin (aahh my search stopped working!), there is a chance that it is actually caused by another plugin – this is advice for plugins and themes in general.
Thanks
RossRoss Moderator(Private) May 2, 2015 at 2:49 pm #16518As mentioned above open a new ticket and explain your problem/setup 🙂
Thanks
Ross Moderator(Private) May 5, 2015 at 10:02 am #16679Hey Rosario
I think you’ve found a bug that was introduced a couple of versions ago – I just emailed you another update – please can you test?
Thanks
Ross Moderator(Private) May 5, 2015 at 10:35 am #16682Please clear you cache and try again – because the version I gave you was BETA (and the plugin version number didn’t change), your cache probably hasn’t cleared.
If this still doesn’t work, as mentioned above, please open a new ticket.
Thanks
-
AuthorPosts