• Resolved Nate

    (@goseongguy)


    Very nice plugin! I have one question. I am using Freesoul Deactivate to disable plugins on various pages. The Code Profiler reports are reflecting the expected plugins that I’ve enabled/disabled, EXCEPT for the Homepage.

    The report for the Homepage always shows *every* plugin loading (along with their measured PHP exec. time), including those that should be disabled as in the other pages.

    I don’t know if it’s an issue with the now rather mature plugin Freesoul Deactivate or Code Profiler as both plugins look to be functioning properly. Freesoul’s simulation/verification tool shows that some are indeed disabled, and the logs in Code Profiler don’t show any warnings but simply reflect that all plugins are loading which matches the report.

    In the “select a page” dropdown I tried both “Homepage” and “Home” as well as different “User Agents”. Could it be a bug? Any other ideas to try?

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi @goseongguy

    Freesoul Deactivate Plugins doesn’t disable any plugin during the profiling process for the homepage. This is due to FDP. Code Profiler has nothing to do with this issue. Actually, it’s not really an issue. It works so because if FDP allowed disabling plugins on the homepage during an activity like the profiling, you would have serious issues during activities of third plugins that call the homepage instead of calling the file admin-ajax.php.

    In your case, to solve this issue you can go to Custom URLs => Frontend URLs, and using the match *CODE_PROFILER_ON* you can load only the selected plugins during the profiling process. This will affect all the pages.
    If you want it only for specific pages, you can use something that looks like *sample-page*CODE_PROFILER_ON*, where sample-page is the slug of the page that appears in the URL.

    I hope it helps.

    Thread Starter Nate

    (@goseongguy)

    Thanks for such a prompt reply Jose. I see. So frontend users will still experience the plugins disabled on the frontend homepage, but just during profiling they will all be activated for the homepage?
    Thank you to to creators of both plugins.

    You are welcome @goseongguy

    The next version of FDP will load the plugins like the other pages also on the homepage. And you will be able to choose between usual FDP settings and settings, especially for the profiling.

    If you have a staging environment if you want you can test it. You can download it with this link: https://downloads.www.ads-software.com/plugin/freesoul-deactivate-plugins.1.8.9.0.4.2.zip

    You will find the menu item “Code Profiler” under the gear in FDP navigation.

    With the beta version, you should remove the custom URL with the match *CODE_PROFILER_ON* if you want to use the new settings.

    In case of any issue let me know.

    • This reply was modified 2 years, 9 months ago by Jose.
    Thread Starter Nate

    (@goseongguy)

    Yes I just tried the new version and it works great! Cheers!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Issue with reports for Home/Homepage’ is closed to new replies.