Plugin Author
Ajay
(@ajay)
Hi,
The current release used WordPress Transients to cache the search results for queries and speed up subsequent searches for the terms without the additional complex query. These are set to expire every hour.
You’ll find this at: https://plugins.trac.ww.wp.xz.cn/browser/better-search/trunk/better-search.php#L1004
Do you normally have a lot of different searches every hour?
not like this. the options table eventually reached 7gb. they were apparently never deleted. i like the way the plugin worked, but fear to repeat the problem on the new site.
Plugin Author
Ajay
(@ajay)
That’s quite an interesting point that you’ve raised. I’ve relied on WordPress’ transients, but seems like an inherent problem of not losing them. Have you been able to trace the issue to the transients?
I’ll add a new cronjob within the plugin in the next version to clean up the transients on a regular basis. You might also want to try using the below plugin until then.
https://ww.wp.xz.cn/plugins/delete-expired-transients/
The other option is to edit the plugin code as above to remove the setting of the transients. More specifically uncomment out the set_transients line: https://plugins.trac.ww.wp.xz.cn/browser/better-search/trunk/better-search.php#L1010
i was not aware that was how wp handled such things, so while i knew the file continued to grow, i had no idea why. having read some of the other threads about the use of that table, it makes perfect sense now.
there’s no way to do any forensics on the matter now. my partners had, for a while, wanted to change hosting services, and spin off each of the sub-domains at our site to it’s one domain. the move was a bloody nightmare as the old server seemed like it was actually fighting us, but we’re all on our own now.
i have installed the delete-expired-transients plugin since it looks like it would help fix any related quirks, and have re-activated better search. give me a day or two to monitor behaviour and results, and will advise.
thanks for the response.
Plugin Author
Ajay
(@ajay)
Thanks for the update. Do let me know how it goes. But, seeing the issues with transients, I’ll definitely put the cron job to clean up the entries as one of the things to add to the plugin.
Plugin Author
Ajay
(@ajay)
Instead of a cron job, I’ve implemented a button that will delete any transients set by the plugin. You’ll find this at the bottom of the settings page.
You’ll find this in v2.0.0 which was released today.