Error 500 after activating the troubleshooting mode

  • Resolved Mike Castro Demaria

    (@mikecastrodemaria)


    6 years, 4 months ago

    Help, error 500 after activating the troubleshooting mode.
    How to deactivate it without an back-office acces ? ???

    mod_fcgid: stderr: PHP Warning: require(…/wp-content/themes/medicare/inc/custom-header.php): failed to open stream: No such file or directory in …/wp-content/themes/twentyfifteen/functions.php on line 443

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Marius L. J.

    (@clorith)

    Hi,

    You can disable it by clearing your cookies, or losing all browser windows (if you are not sure if all browser windows are properly closed, restarting your computer will do that for you as well).

    Moderator Bet Hannon

    (@bethannon1)

    I’m having this issue too. Clearing cookies does fix it. But it happens every time I try to go to troubleshooting mode. Are there just some sites/themes where Health Check won’t work?

    Plugin Author Marius L. J.

    (@clorith)

    There’s some configurations of plugins/themes that won’t work without the other active (relying on other code without checking if it exists, thus causing 500 errors). It’s usually poor implementations of code, but it’s frequent enough that we are working on solutions to this for version 1.2.0.

    i just had the same thing happen to me.

    i was able to resolve it by removing the file:
    health-check-troubleshooting-mode.php

    from /mu-plugins

    i couldn’t figure out what was causing the issue at first, so i looked at my logs. it would appear that there’s a call to /twentyseventeen/functions.php in there, that might be causing this issue to happen?

    [11-Jul-2018 18:01:24 UTC] PHP Fatal error: require(): Failed opening required ‘/wp-content/themes/betheme/inc/custom-header.php’ (include_path=’.:/opt/alt/php72/usr/share/php:/opt/alt/php72/usr/share/pear’) in /wp-content/themes/twentyseventeen/functions.php on line 592

    Plugin Author Marius L. J.

    (@clorith)

    Yes, it’s a known issue with child themes right now, we’ve already got it patched for the next version of the plugin. For now if you do find your self stuck in Troubleshooting Mode due to a fatal error like this for example, you can leave it by clearing your cookies, or closing your browser as it’s tied in to a session-cookie that goes away when the browser is completely closed.

    I do apologize for any inconvenience.

    Hi,

    We have the same issue for a client’s site. Do you have an estimated date that this patch will be released?

    Thanks

    Plugin Author Marius L. J.

    (@clorith)

    Hi,

    It should be out by the end of the weekend if all goes to plan, if not early next week at the latest.

    Thread Starter Mike Castro Demaria

    (@mikecastrodemaria)

    Ok thanks, we are waiting … thanks for your feedback Marius.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Error 500 after activating the troubleshooting mode’ is closed to new replies.