Hi @japenz
good idea. Please, if you have a staging environment try v. 2.0.0.beta-2 which you can find here: https://downloads.wp.xz.cn/plugin/freesoul-deactivate-plugins.2.0.0.beta-2.zip
You will find something that looks like “Any Product Categories (Products)” directly in the FDP main navigation under the menu item Archives.
Update the plugin from the page of plugins by clicking on Add New => Upload Plugins => Choose File, and confirm you want the new version.
If you don’t see the new FDP menu items, click on the triangle on the top right to expand the top admin bar, and then click on “Refresh FDP navigation”.
Please, let me know if it works, or if you have any suggestions to make it clearer.
Have a great day!
Jose
Thread Starter
JapeNZ
(@japenz)
Hi @giuse,
Thank you for getting back to me 🙂
So I tested the beta version, and ‘Any Product Categories’ is exactly what I was talking about, great job!
Having an ‘Any *’ for the archives, attributes etc will make things far more managable.
I did however receive a ‘Your Site is Experiencing a Technical Issue’ email from WordPress once the beta was active, here are the error details:
WordPress version 6.2.2
Active theme: Comic Book Shop Child (version 1.9.22)
Current plugin: Freesoul Deactivate Plugins (version 2.0.0.beta-2)
PHP version 8.2.7
Error Details
=============
An error of type E_ERROR was caused in line 20 of the file /nas/content/live/comicbookshop/wp-content/plugins/freesoul-deactivate-plugins/admin/fdp-admin.php.
Error message: Uncaught Error: Failed opening required ‘/nas/content/live/comicbookshop/wp-content/plugins/freesoul-deactivate-plugins/admin/classes/abstracts/abstract-fdp-superclass.php’ (include_path=’.:/usr/share/pear/php:/usr/share/php’) in /nas/content/live/comicbookshop/wp-content/plugins/freesoul-deactivate-plugins/admin/fdp-admin.php:20
Stack trace:
#0 /nas/content/live/comicbookshop/wp-content/plugins/freesoul-deactivate-plugins/freesoul-deactivate-plugins.php(171): require()
#1 /nas/content/live/comicbookshop/wp-settings.php(406): include_once(‘/nas/content/li…’)
#2 /nas/content/live/comicbookshop/wp-config.php(125): require_once(‘/nas/content/li…’)
#3 /nas/content/live/comicbookshop/wp-load.php(50): require_once(‘/nas/content/li…’)
#4 /nas/content/live/comicbookshop/wp-admin/admin.php(34): require_once(‘/nas/content/li…’)
#5 {main}
thrown
I didn’t actually notice my site go down as a result of this error, but obviously receiving the warning made me revert back to the current stable version of your plugin.
Thanks again for your help 🙂
Hi @japenz
you are welcome!
If we consider version 2.0.0.beta-2, at line 20 of the file fdp-admin.php there is no call to the file abstract-fdp-superclass.php. Actually, the file abstract-fdp-superclass.php doesn’t exist in the FDP 2.0.0.beta-2 folder, and it’s never required by any file.
You can see here line 20 of fdp-admin.php of the beta version 2.0.0.beta-2.
Instead, the actual stable version requires that file at line 20 of the file fdp-admin.php. You can see here.
So, the error was surely caused by fdp-admin.php of the stable version 1.9.5.8, not by the beta version.
I don’t know how you updated the plugin, but I suspect the error was caused while the files of the plugin were transferring, and you still had fdp-admin.php of the stable version, but the file abstract-fdp-superclass.php didn’t exist anymore. That file exists only in version 1.9.5.8.
If you have all the files of the beta version, or all the files of the stable version, you should not have any problem. But if you have a mix of them, even if it’s only temporary, you have issues.
I hope it helps.
Have a great day!
Jose
Thread Starter
JapeNZ
(@japenz)
Hi @giuse,
Right okay, yeah that would make sense.
I updated the plugin to the beta by manual upload replacing the existing stable plugin, which would explain why they were both briefly there and caused the error.
Thanks again for your help!
Thread Starter
JapeNZ
(@japenz)
Hi @giuse,
I’m trying to do some unrelated testing that requires me to deactivate and reactive the plugin.
Seems there might be a caching issue, here’s the error I receive when using the beta:
Freesoul Deactivate Plugins is not active, but its mu-plugin was not deleted.
Normally, when you deactivate FDP, it automatically deletes its mu-plugin file.
If you still have that file, it means you disabed FDP via FTP or something went wrong during the deactivation process.
Delete the file wp-content/mu-plugins/eos-deactivate-plugins.php if you want to completely disable FDP.
Clearing the WP Engine server cache fixed the issue, just figured I should let you know for beta testing purposes… perhaps including a suggestion to clear serverside caching in the error message might be useful.
HI @japenz
thank you very much for your suggestion.
Does WP Engine cache also the backend pages? This would be strange for me.
The code to show that message is written in a mu-plugin located in wp-content/mu-plugins, and it is triggered only if the standard plugin of FDP is deactivated.
If you saw that message, there are only two possibilities:
- The FDP backend page where you saw the message, was cached when the standard plugin was disabled
- You really still had the FDP mu-plugin located in wp-content/mu-plugins, but the standard plugin was disabled
I think the second possibility is more probable. Maybe it was something only temporary, and when you cleared the server cache it wasn’t so anymore, but not because of the cache.
You also had an issue with a missing file. Both issues are probably caused by the way the plugin was updated.
If during the update the mu-plugin file is still present, but the standard plugin is temporarily disabled, during that time you have the conditions to trigger that message.
Usually, when you update a plugin from the page of plugins by clicking n Upload Plugin, this should not happen, because first, the files of the new plugins are transferred, and only when you confirm the old files are deleted. I suspect the update wasn’t done in a standard way. Maybe WP Engine manipulates that process.
In any case, it seems an issue that was only temporary, and I’m almost sure the message disappeared also if you didn’t clear the server cache.
If on the contrary, it was really a problem related to the cache, you should ensure the backend pages are not cached. This is not only for the FDP backend pages but for all the backend pages. In another case, you would have a lot of issues, especially with security.
Have a great day!
Jose
