Forums › Forums › Search & Filter Pro › Results only appearing after setting first filter
- This topic has 18 replies, 2 voices, and was last updated 8 years, 8 months ago by Anonymous.
-
Anonymous(Private) March 3, 2016 at 1:22 pm #38569
Hey Ross,
same results, even when using the standard results.php, having only WooCommerce, ACF and Search and Filter activated, using hard-coded shortcode and using vanilla wordpress/storefront themes… It usually works fine until cache rebuild hits about 2500 of the mentioned 4000 products. Then suddenly it says no results found. Really weird, we’ve invested a lot of time into the issue and hope we can somehow get it fixed.
If you have any input, idea, whatsoever, we’d be really thankful!
Sebastian
Ross Moderator(Private) March 3, 2016 at 1:52 pm #38573Hey Sebastian
Ok so that sounds like some pretty useful info that I didn’t know before – that the results show fine until cache gets to around 2500…
This sounds like a limit is being reached somewhere.
Can you enable WP_DEBUG, and logging:
define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', true);
and then see if any errors are being generated – be sure to check the log file as well which will be created in the wp-content folder and let me know any errors you find?
When its all enabled anyway and I’ll take a look too.
Thanks
Anonymous(Private) March 3, 2016 at 2:22 pm #38585Interestingly, with the debug options turned to true, cache rebuilding doesnt even start/work. Even when starting it and then turning debug mode on, it just stops. Frontend shows now relevant errors. I might try it on a different server later and check if there’s serverside restrictions. Maybe I could see something in the MySQL tables for the cache?
Ross Moderator(Private) March 3, 2016 at 3:18 pm #38593Ah ok, well this is good(ish) news, its a matter of debugging the various errors – but at least we’re getting errors that we can act upon.
I’ll take a look via ftp later on today and see if I can make sense of them.
Thanks
Ross Moderator(Private) March 9, 2016 at 1:23 am #39031WP Engine was killing the query because it was long – this is a known issue with a few other search plugins I found out.
To get around this add this to wp-config:
define('WPE_GOVERNOR', false);
This should allow the long queries to get through 🙂 I added this on staging, I’m assuming you’ll need to add this on the live site.
Thanks
-
AuthorPosts