500 error

  • Resolved bernardberry646

    (@bernardberry646)


    2 years, 7 months ago

    I actually installed this for:

    
14. HOOKS:
Filterable list of action and filter hooks from WordPress core with description, originating file path and link to WordPress Code Reference for each hook
List of action and filter hooks from the active theme, with description, originating file path and link to file preview in the theme file editor
List of action and filter hooks from active plugins, with description, originating file path and link to file preview in the plugin file editor

    WordPress v5.8.3 | Web Server: Apache fpm-fcgi | CENTOS 7.9 Linux
    I only get a list for WP Core. For EVERY plugin and theme I get 500 error!
    Status: 500 Internal Server Error
    Content-type: text/html; charset=UTF-8

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Bowo

    (@qriouslad)

    @bernardberry646 is that shared hosting with cPanel? Have you checked if shell_exec and exec are enabled in PHP?

    Plugin Author Bowo

    (@qriouslad)

    @bernardberry646 also, can you access the error log and see what kind of PHP error is causing the 500 HTTP response?

    Thread Starter bernardberry646

    (@bernardberry646)

    Hostgator.. VPS.. shell_exec is enabled (I manually enabled it myself)
    The 500 error is for Plugin Hooks..

    Plugin Author Bowo

    (@qriouslad)

    @bernardberry646 noted. Scanning the plugin hooks is a complex process, and probably the the single thing that takes the most time on the dashboard. I’m a bit at a lost I’m afraid, as to what might be causing the error. Have you tried looking into the error log? Or enable WP debug log first and try loading the dashboard again so it logs the specific error.

    Plugin Author Bowo

    (@qriouslad)

    @bernardberry646 without further error info, I’m unable to troubleahoot this. Would you like me to go into your site and try to troubleshoot there? Another option is to install Debug Toolit plugin and see if that generates useful info when the error shows up. You may need to delete the plugin via command line / file manager once you get the necessary info.

    Plugin Author Bowo

    (@qriouslad)

    @bernardberry646 since I have not heard back for more than 1 month, I’m marking this thread as resolved. Please report in a new thread if the issue still persists on your end, and provide as much info around the error. Thank you.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘500 error’ is closed to new replies.