Freesoul php Limit Errors & Auto Plugin Deactivation

  • Resolved ehswift

    (@ehswift)


    4 years, 10 months ago

    The first error happened when trying to use the DIVI builder plugin to update the home page and occurs when trying to save it. It basically says to increase memory_limit_max_execution_time, upload_max_filesize, post_max_size, max_input_time, max_input_vars. It also said to check if Mod Security was blocking the program from running. I had my hosting provider look into all of these and said there should be no issues. At one point they even completely disabled Mod Security to rule that out. The above errors do not occur when the Freesoul plugin is not being used. Shortly after the first error occurs a 2nd one pops up and that says Freesoul Deactivate Plugins is not active, but its mu-plugin was not deleted. It then goes on to say to Delete the file /home/****/public_html/***/wp-content/mu-plugins/eos-deactivate-plugins.php

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Jose Mortellaro

    (@giuse)

    4 years, 10 months ago

    Hi @ehswift

    Freesoul Deactivate Plugins just saves the metadata related to the disabled plugins when you save the page. So, it’s very strange you exceed the maximum execution time limit.

    Are you sure you are not very near the limit and it’s enough a plugin more to exceed it? I mean, maybe disabling another plugin and keeping FDP active you may have no problems. I mean probably it’s not because FDP asks for more resources than other plugins during the saving process, but because it asks something that is enough to exceed a limit that was already near to be exceeded.

    In any case, you can exclude Freesoul Deactivate Plugins in the single page and during the saving process adding this single line of code:

    add_filter( 'eos_dp_user_can_metabox','__return_false' );

    Adding that code you will not see anymore the section of FDP on the single page, but you can still use the Singles settings in Freesoul Deactivate Plugins => Singles.

    I will also test it with Divi to see if I can reproduce the problem. Maybe FDP triggers a process of Divi that leaks memory. I will check.

    Plugin Author Jose Mortellaro

    (@giuse)

    4 years, 10 months ago

    Freesoul Deactivate Plugins is not active, but its mu-plugin was not deleted. It then goes on to say to Delete the file /home/****/public_html/***/wp-content/mu-plugins/eos-deactivate-plugins.php

    Have you disabled Freesoul Deactivate Plugins via FTP? If so, its mu-plugin that is included in wp-content/mu-plugin/ is still there. Only when you disable it in the standard way from the page of plugins it deletes that file. And when you reactivate it, it writes it again. If you have deactivated from the page of plugins it means you haven’t the right permissions to write in the folder wp-content/mu-plugin.
    That message is just telling you that the mu-plugin of Freesoul Deactivate Plugins is still active and running. If you want to completely disable FDP you need to delete that file.

    Plugin Author Jose Mortellaro

    (@giuse)

    4 years, 9 months ago

    Hi @ehswift

    I’ve tested Divi and have no problems.

    Have you tried with the suggested line of code?

    add_filter( 'eos_dp_user_can_metabox','__return_false' );

    Plugin Author Jose Mortellaro

    (@giuse)

    4 years, 9 months ago

    Hi @ehswift

    I will close this thread for inactivity. If you still need help don’t hesitate to open a new thread.

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

The topic ‘Freesoul php Limit Errors & Auto Plugin Deactivation’ is closed to new replies.