WordPress.org

Ready to get started?Download WordPress

Forums

P3 (Plugin Performance Profiler)
[resolved] Causes Server error 500 (4 posts)

  1. nbquidditch
    Member
    Posted 2 years ago #

    My webhost is shared and the main website is set in the root directory. Five other websites are located as subdomains (see structure below):

    The P3 plugin worked with subdomains but caused an 500 server error in the main domain:

    /public_html/
    /public_html/wp code of main domain
    /public_html/wp-admin/ - maindomain wp code
    /public_html/wp-content/ - maindomain wp code
    /public_html/wp-content/plugins/ - maindomain wp code
    /public_html/wp-content/themes/ - maindomain wp code
    /public_html/wp-includes/ - maindomain wp code
    /public_html/subdomain_name/ - subdomain wp code
    /public_html/subdomain_name/wp_admin/ - subdomain wp code
    /public_html/subdomain_name/wp_content/ - subdomain wp code
    /public_html/subdomain_name/wp_admin/plugins/ - subdomain wp code
    /public_html/subdomain_name/wp_admin/themes/ - subdomain wp code
    /public_html/subdomain_name/wp_includes/ - subdomain wp code
    etc

    http://wordpress.org/extend/plugins/p3-profiler/

  2. Kurt Payne
    Member
    Plugin Contributor

    Posted 2 years ago #

    Are you getting a 500 error on activation, or on use?

  3. nbquidditch
    Member
    Posted 2 years ago #

    As I recall it accepts activation but I didn't run it immediately because I wanted to install it on other (sub)domains.

    When I went back to the main domain to run it crashed when I tried to get admin access. I contacted my webhost about the server 500 error and they identifed P3 as the culprit and disabled it by moving it to another folder.

    Regards

    Will

  4. Kurt Payne
    Member
    Plugin Contributor

    Posted 2 years ago #

    Hi Will,

    Do you have the specific error they found? If so, I'd like to investigate this more thoroughly. For right now, I'm taking an educated guess ...

    I've seen this happen most commonly when a site was running very close to its memory limit. When you activate P3, it pushed it just over the limit and this error happened.

    Removing P3 should fix the error right now. For the long term, consider raising the memory limit. You can confirm this is the case by looking for errors related to "memory limit" in your error logs.

    To remove P3, remove the following files and folders via FTP:

    wp-content/plugins/p3-profiler (the whole folder)
    wp-content/mu-plugins/p3-profiler.php (if it exists)

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic