• Resolved markofapproval

    (@markofapproval)


    Hey guys, trying out the plugin from here. I noted on the multisite I get an error message that will not go away. This happens when one of the sites does not have the plugin install. While the issue is not affecting site, the notice is bothersome and cannot be dismissed and shows on every page of the admin area.

    Is there anyway to not show the notice and not allow the MU part of the plugin to trigger on sites from the network that do not use this plugin?

    The notice says

    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.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Jose

    (@giuse)

    Hi @markofapproval

    thank you for reporting this issue.

    FDP needs a mu-plugin inside wp-content/mu-plugins.
    It may happen that some users disable or remove FDP via FTP and they are not aware of the mu-plugin file, so they don’t delete it. That file is automatically deleted only when you deactivate FDP from the page of plugins or through WP-CLI.
    This message is for those users who think they have deactivated FDP, but its mu-plugin is still there and runs.

    The mu-plugin will be not effective on the subsites where you have disabled FDP but the same you see that message because, in the case of a multisite installation, you have one single mu-plugin file for the entire network, and that file detects the absence of FDP on that subsite.

    In any case, this will be fixed with the next version, and you will not see anymore that message.

    The new version should come soon. I can’t be sure, but I would say in a couple of days.

    As a temporary solution, you can maybe activate FDP on the subsites where you don’t want to see that message. Take into account that the consumption of FDP is practically zero in the backend pages that aren’t FDP pages (it just adds the FDP admin menu items), and in the frontend, it doesn’t run (only the mu-plugin runs on the frontend).

    Have a great day!

    Jose

    Thread Starter markofapproval

    (@markofapproval)

    Thanks Jose! Sure that is what I will do for now. Although my multi site only has a handful of users so not a problem at this stage.

    Look forward to checking out this nifty plugin esp for optimising landing pages!

    Plugin Author Jose

    (@giuse)

    Many thanks to you @markofapproval !

    The new version v.1.9.3 is public now.
    Please, let me know if you still have issues.

    Have a great day!

    Jose

    Thread Starter markofapproval

    (@markofapproval)

    Thank you Jose for jumping on this so quickly. Indeed the notice is gone but the site is crashing when I try and go into Elementor. This is the error log:

    Fatal error: Uncaught TypeError: in_array(): Argument #2 ($haystack) must be of type array, string given in xxx/public_html/wp-content/mu-plugins/eos-deactivate-plugins.php:484 Stack trace: #0 xxx/public_html/wp-content/mu-plugins/eos-deactivate-plugins.php(484): in_array() #1 xxx/public_html/wp-settings.php(372): include_once('/home/795074.cl...') #2 xxx/public_html/wp-config.php(132): require_once('/home/795074.cl...') #3 xxx/public_html/wp-load.php(50): require_once('/home/795074.cl...') #4 xxx/public_html/wp-blog-header.php(13): require_once('/home/795074.cl...') #5 xxx/public_html/index.php(17): require('/home/795074.cl...') #6 {main} thrown in xxx/public_html/wp-content/mu-plugins/eos-deactivate-plugins.php on line 484
    There has been a critical error on this website.

    I deactivated it for now. For sure take your time to fix, I can always revert to an older version if needed.

    With gratitude,
    Mark.

    Plugin Author Jose

    (@giuse)

    Hi @markofapproval

    many thanks to you for reporting this other issue.
    The new version 1.9.3.3 should fix it. I suggest you update to v. 1.9.3.3.

    Let me know if it’s solved also on your installation.

    Have a great day!

    Jose

    Thread Starter markofapproval

    (@markofapproval)

    Hi Jose will certainly try it.

    Many thanks for being so fast on this.

    Reply back soon! ??

    Plugin Author Jose

    (@giuse)

    Hi @markofapproval

    you are welcome!

    When you have the time, just let me know if you still have issues.

    Have a great day!

    Jose

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Multisite issues’ is closed to new replies.