Plugin deactivates plugin

  • Resolved mikandreas

    (@mikandreas)


    4 years, 9 months ago

    Hi,

    First the plugin was just brilliant – for the couple of hours I had it working!
    I’m hoping there’s a simple fix because it’s so useful. I have “too many” plugins – or that’s what I keep getting told so this is a Godsend.

    I was going page-by-page deactivating plugins that were not needed on the various pages.

    Then suddenly, it seems that ALL the plugins that I had deactivated on various pages actually deactivated completely on the entire site</strong. Including the FDP plugin – so the FDP was listed the inactive plugin list.

    In addition I got the following message on the WP admin dashboard:

    “Freesoul Deactivate Plugins is not active, but its mu-plugin was not deleted.
    Normally, when you deactivate FDP, it 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 /home/nginx/domains/[site url]/public/wp-content/mu-plugins/eos-deactivate-plugins.php

    Then, FDP will not exist anymore in your installation.”

    I didn’t try to deactivate the FDP plugin at all or do anything via FTP.

    I did try to reactivate FDP and all the others but still was given the above error message.

    I know this may be difficult to diagnose without more detail but just hoping!

    PS: Assuming this is fixable, I will definitely be a PRO using when its available,

    Thanks

    • This topic was modified 4 years, 9 months ago by mikandreas.
    • This topic was modified 4 years, 9 months ago by mikandreas.
Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Jose Mortellaro

    (@giuse)

    4 years, 9 months ago

    Hi @mikandreas

    thank you very much for your thread.

    Another user reported the same issue after the update to 1.8.8.7. You can see here the issue https://ww.wp.xz.cn/support/topic/plugin-is-completely-deactivating-plugins/. It looks you have the same problem.

    I’m still waiting for a response from the user who reported the same issue, this is why I set the official version back to 1.8.8.6.

    First, can you please tell me which version you are using?

    If it’s 1.8.8.7, you can solve it by rolling back to 1.8.8.6 until this issue is not solved. Or testing 1.8.8.7.1 (that will help me to find the solution).

    Thread Starter mikandreas

    (@mikandreas)

    4 years, 9 months ago

    Hi @giuse

    Thank you for the super fast response.

    I actually downloaded the version that is available via WordPress – I’ve just checked which version is available and its 1.8.8.6.

    Hope that helps and you find the issue.

    Plugin Author Jose Mortellaro

    (@giuse)

    4 years, 9 months ago

    Thank you very much @mikandreas

    Can you please provide me the list of all your plugin? You can download it from Fresoul Deactivate Plugins => Favorite Plugins => Export => Export the list

    Thread Starter mikandreas

    (@mikandreas)

    4 years, 9 months ago

    Ok @giuse

    I have the list – do you want me to past it here or send it to you in another way? I exported the txt file but it shows:

    <html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>
    Plugin Author Jose Mortellaro

    (@giuse)

    4 years, 9 months ago

    @mikandreas I forgot to clarify the message related to “Freesoul Deactivate Plugins is not active, but its mu-plugin was not deleted….”.
    This is caused by the fact Freesoul Deactivate Plugin itself was disabled.
    When you activate FDP, it writes a file in wp-content/mu-plugins. The code of that file runs before any other plugin.
    When you deactivate FDP, it deletes that file.
    But, if FDP is disabled in a nonstandard way, as in this case, the file in wp-content/mu-plugins remains there.
    If that file is still there, but FDP is disabled, it triggers a self debugging that warns you something is wrong. This usually happens when you delete FDP via FTP, this is why you see that message. It’s just saying “FDP is disabled, but a part of it is still there”.
    Don’t care about that message. It’s normal in this situation. The real problem is that you have plugins globally disabled including FDP (that causes the message).

    About the list of plugins. Probably it’s forbidden for issues related to the folder permissions.

    If you want you can use the contact form at https://freesoul-deactivate-plugins.com/contact/ to provide me the list.

    Thread Starter mikandreas

    (@mikandreas)

    4 years, 9 months ago

    Hi @giuse

    I sent you the plugin list via the link you provided.

    Thank you

    Thread Starter mikandreas

    (@mikandreas)

    4 years, 9 months ago

    Upadte:

    @giuse – thanks for your awesome support and expertise. I’ve now got the plugin active on our live site and it’s working like a dream. 100% score for performance and structure on GTMetrix. Looking forward to the pro version.

    Plugin Author Jose Mortellaro

    (@giuse)

    4 years, 9 months ago

    Perfect! I’m very happy it works. In case of any issue, don’t hesitate to open a new thread.

    Plugin Author Jose Mortellaro

    (@giuse)

    4 years, 9 months ago

    Hi @mikandreas

    for solving the issue that happened on your site, now other plugins that depend on third plugins are causing fatal errors on some installations when the third plugins are selectively disabled.

    I will write a post to explain in more detail why some plugins cause this problem.

    There are basically two kinds of issues

    1) The issue you had on your site. Some plugins are globally disabled if a plugin saves the option of active plugins.
    2) A plugin triggers a fatal error if it depends on a third plugin and that plugin is disabled by FDP.

    It’s impossible to prevent both issues, and the number of issues of type 2) that the users reported after the last update are a lot higher than the number of users like you who reported the issues of kind 1)

    So, I need to release a new version of Freesoul Deactivate Plugins that as default it prevents the issues of type 2).
    It will be still possible to prevent the issue that you experienced, but you need to write a line of code in wp-config.php.

    I suggest you do the following:

    – Add this line of code before the comment /* That’s all, stop editing! Happy blogging. */

    define( 'FDP_REMOVE_FILTERS_BEFORE_FIRST_PLUGIN',true );

    – Download version 1.8.8.7.4 from this link: https://downloads.wp.xz.cn/plugin/freesoul-deactivate-plugins.1.8.8.7.4.zip
    – Update the plugin (go to the plugins page, click on “Add New”, click on “Upload Plugin”, select the downloaded zip, confirm you want the new version).

    Until you have define( ‘FDP_REMOVE_FILTERS_BEFORE_FIRST_PLUGIN’,true ); in wp-config.php, Freesoul Deactivate Plugins will be as it is now on your installation and you should not have problems.

    Maybe test it first on your staging environment.
    After you confirm that it works, v 1.8.8.7.4 will become the new official version.

    Plugin Author Jose Mortellaro

    (@giuse)

    4 years, 9 months ago

    Hi @mikandreas

    Version is 1.8.8.7.4 is now public. Before to update it’s very important you add the line of code in wp-config.php as mentioned in my previous comment, in another case you risk again the issue.

    Before the comment /* That’s all, stop editing! Happy blogging. */ in wp-config.php:

    define( 'FDP_REMOVE_FILTERS_BEFORE_FIRST_PLUGIN',true );

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Plugin deactivates plugin’ is closed to new replies.