WOOF plugin deactivates overnight
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Hi. I'm integrating the WOOF plugin to an existing site, as it seems in tests to be a lot more resource efficient over the previous search/filtering plugin that was in use. The site is using Elementor and a handful of other plugins, and for some reason, overnight, this one gets deactivated and I can't find anything in any logs that explains why...
Everything seems to run great with it, and then when i come back all i see is the shortcode; [woof] in our sidebar, and when i look in the plugins for the site, it's not active anymore.
- Woof v1.2.9.2 (free version)
- Wordpress 6.0.1
- Woocommerce 6.5.1
- Elementor 3.6.6 / Pro 3.7
I know that some of these are out of date by a minor version or two, but this is what i have to work with.
There were some plugins that were spewing warnings into the logs, but i have either removed or repaired them, and it has had no effect on the deactivation issue. the most frustrating thing is that I can't figure out how to trigger it (no wp-cron tasks seem to be the trigger, as far as i can tell) so i just have to make some changes and wait for hours...
I hope you can help.
Hello
My plugin does not have a self-disable feature.
And I doubt that any error can cause this behavior
What reasons can be:
1 Another site manager (it's better to ask your colleagues if someone has access to this site)
2 Third-party functionality that may affect the database
Unfortunately, I can't think of any other reason for this behavior.
I suppose I was unclear; what I meant was that it was getting deactivated by *something*. I didn't mean it deactivated itself.
Thanks for the ideas! Gonna dig into it more!
When I find out a solution, I'll respond here in case anyone else sees this (or something like it)
Thank you again for the suggestions and for the plugin. :D I'm nearly certain now that the actual culprit is WP Merge, copying over configurations from the live site, which didn't (until just now) have WOOF installed...
I totally hadn't considered that as an issue; we'd never seen anything like this happen before on any of our other dev environments. Thanks!
Hello
Ok! Great!
Thank you for your cooperation