Hello, i wanted to try the plugin but was overwhelmed, so i never used it. I reset everything, deactivated, then deleted the plugin. But there’s still the mu-plugin present (freesoul deactivate plugins [fdp]) and i can’t delete it anywhere. How do i remove it?
Anyway, if FDP for any reasons wasn’t able to delete the mu-plugin, you should:
See a clear notification in your backend.
Be able to access the file wp-content/mu-plugins/eos-deactivate-plugins.php via FTP.
If you don’t see them, it means there is no FDP mu-plugin left on your site.
The 100% safe way to delete it is to remove the file wp-content/mu-plugins/eos-deactivate-plugins.php via FTP. If you don’t see the file, there’s nothing to delete.
If via FTP you don’t see that file, but still see it in the mu-plugins page of your backend, it means the pages of your backend may be served by full-page cache. Be careful. Having cached backend pages would not be safe.
So i’ve deleted all caches and object caches (SQLite) and the file still appears and it also starts in the post editor. I’ve now contacted my hosting support, as i can’t find any file you mentioned and the mu-plugins folder is “empty” (no FDP files).
As I can see in your second screenshot, your mu-plugins folder is called wp-safe-mode. It looks like you don’t have a standard WordPress installation. Do you perhaps have a plugin or something else that changes the default WordPress folder names?
In any case, I suggest checking the wp-content/wp-safe-mode folder via FTP. You may find eos-deactivate-plugins.php in wp-content/wp-safe-mode.
I also see that you have 53 active plugins. You would really benefit from using FDP. Would you like to try using it again? If you have specific questions about how to use it, feel free to ask me.
For an easier FDP setup, I suggest first identifying the heaviest plugins using Code Profiler, and then using FDP to deactivate them where they aren’t needed. There’s no need to try to deactivate all unused plugins at once—focusing on a few heavy plugins will be much easier and still effective.
If you confirm this, I will test it and try to reproduce the same issue. I also suspect it may cause conflicts with FDP because it manipulates the set of active plugins.
Hi Jose, i used this in the past, but it’s removed. My hoster found the file and now removed it for me; it was actually saved in /wp-safe-mode/. Now everything is “clean” again. I will contact the WP Safe Mode Devs why the folder still exists. Thank you so much for your help!
Oh, and yes, i would probably benefit from it, but i’m on BunnyCDN with all premium features through my hoster, so i’m not that concerned about speed, as i’m happy with them. For me personally, your plugin is too complex as a starter, so i will keep it “as-is” for now. 🙂
It uses the WordPress core function wp_delete_file and the WordPress constant WPMU_PLUGIN_DIR, without hardcoding the folder name. Because of this, the conflict with WP Safe Mode can’t be solved by FDP. It has to be addressed by the authors of WP Safe Mode.
There is no way for FDP to know that WP Safe Mode changes the folder name and doesn’t use WordPress standards to reference the new mu-plugins directory.
I also believe WP Safe Mode can cause conflicts with many other plugins that use the mu-plugins folder.
