Hi @khobs
to be honest I don’t think I have understood the issue.
Please, help me to understand, by correcting or confirming my statements and answering my questions.
– The plugin SIP Reviews Shortcode Pro WooCommerce 1.5.4 is the PRO version of this plugin: https://ww.wp.xz.cn/plugins/sip-reviews-shortcode-woocommerce/
– SIP Reviews Shortcode Pro WooCommerce 1.5.4 was disabled without you want to disable it, and you don’t know how this could happen.
– Can you see SIP Reviews Shortcode Pro WooCommerce 1.5.4 in the usual WordPress page of plugins? Is it only disabled or fully deleted?
– The plugin is not fully deleted, you can see it in the page of plugins, but you are not able to activate it again. Is this the issue?
– Does that plugin require the presence of the free version?
– Does that plugin require the presence of WooComemrce? I suppose so. Is WooCommerce active on the pages where you expect to have SIP Reviews Shortcode Pro WooCommerce active?
After fully understand what is the issue I will be happy to help you if possible.
Thread Starter
khobs
(@khobs)
Hello @giuse
– Yes it is
– Yes, the plugin is automatically disabled on the entire website. Each time I activate it (from the plugins wordpress page), it lasts some random time then it is disabled again.
– Yes, only disabled and I can enable it again.
– I can but I don’t know why it is keep being disabled alone.
– No it doesn’t need the free version.
– Yes and yes. But I have just checked before answer you and the SIP plugin was disabled on the Freesoul dashboard where I need it to be enabled. I mean I have done the settings but it looks like it have changed. So I edited it right now and I will check back later.
Thanks
thank you for the information @khobs
Look at the main file of the free version: https://plugins.trac.ww.wp.xz.cn/browser/sip-reviews-shortcode-woocommerce/tags/1.2.2/sip-reviews-shortcode-woocommerce.php
On line 73 the plugin deactivates itself if WooCommerce is not active.
That is the free version, but I suppose the PRO version does the same.
This means that if somewhere you have disabled WooCommerce but not SIP Reviews Shortcode Pro WooCommerce, it disables it itself.
I suggest you check the settings of Freesoul Deactivate Plugins. Everywhere WooCommerce is disabled, also SIP Reviews Shortcode Pro WooCommerce must be disabled. Doing so you should not have the same issue any more.
Do you have the last version of Freesoul Deactivate Plugins? If so, FDP should check the dependencies between WooCommerce and its add-ons, and it would be strange that you were able to disable WooCommerce but not SIP Reviews Shortcode Pro WooCommerce. In that case, I will investigate why the dependencies check didn’t work.
Let me know if you find some settings where WooCommerce was disabled but SIP Reviews Shortcode Pro WooCommerce was active. This is for me the most probable cause of this issue.
Thread Starter
khobs
(@khobs)
Thank you very much for those informations @giuse
I will check that and do some tests and come back to you with the updated infos.
Thread Starter
khobs
(@khobs)
Hello @giuse
So I can confirm that was the issue, the plugin was activated when Woocommerce was not on some pages.
Since I’ve changed that, I did multiple actions and it still working fine then.
But through your plugin I had no information about that condition. Maybe because my dashboard is buggy, there are some conflicts with multiple plugin I’m using.
Hi @khobs
thank you for the confirmation.
For me, the dependency check works fine. FDP will not warn you, it simply unchecks WooCommerce in the matrix if you uncheck one of its add-ons. But this is only done when you set the unused plugins.
I suppose you activated SIP Reviews Shortcode Pro WooCommerce after you had already disabled WooCommerce on some pages. In this case, FDP doesn’t detect any more risk. This is a weak point that I will try to improve.
In a future version when WooCommerce is disabled, all its add-ons will be disabled and that’s it. Where WooCommerce is disabled, you never need its add-ons, so the user will not decide on this, and this kind of issue will not occur anymore.
