• I was one step away from giving it 5 stars, since until two weeks ago it was working great. But now, it returns the following error “The website returned the following HTTP status code: “500 Internal Server Error. By default, the profiler will always abort and throw an error if the server did not return a 200 HTTP status code. You can change that behavior in the Settings section if the page you are profiling needs to return a different code (3xx, 4xx or 5xx)”. And my website is not down, quite the opposite, it works perfectly. I have tried stopping the plugins and security systems, but it keeps giving me that error. Nor have I made too relevant changes in the structure that influence its operation.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author bruandet

    (@bruandet)

    It’s optional, you can disable it: go to the settings tab, and uncheck “5xx server errors (500 Internal Server Error, 503 Service Unavailable etc)”.

    Thread Starter adritin

    (@adritin)

    Hello. Thanks for the reply. I have already tried what you mention. And what I see is that with this option deactivated, the results of the measurements are very different from what was returning me before, when the error did not appear. ??

    Plugin Author bruandet

    (@bruandet)

    Keep the “5xx server errors…” option disabled for now, try to enable debugging in WordPress and see if there’s anything written to the PHP error log:

    1. Edit your wp-config.php script.
    2. Search for:
    define('WP_DEBUG', false);
    3. Replace with:
    define('WP_DEBUG', true);
    4. Add this line below:
    define( 'WP_DEBUG_LOG', true );

    Run the profiler and check the log, if any, which will be saved to “/wp-content/debug.log”.
    Paste its content here or, if there are too many lines, upload it to https://pastebin.com/ .

    After your test, don’t forget to undo the changes to your wp-config.php and to re-enable the “5xx server errors…” option in the “Settings” tab.

    Thread Starter adritin

    (@adritin)

    Good morning.
    I still could not carry out the actions suggested by you, since I am working. But I have found something suspicious in the code profiler log, and based on that, I disabled the plugin involved and the app works OK. Do you need any information to see if it is an incompatibility of Code Profiler with that application? Do you still need me to perform the actions you mentioned above?
    Thank you

    Plugin Author bruandet

    (@bruandet)

    If you can post more details about it, that would help to see why it throws a internal server error.

    Thread Starter adritin

    (@adritin)

    I sent you the log with the error in the last execution attempt I made.
    The parts that contain asterisks were replaced by me, since they contain data that I preferred to omit for security reasons, but if for any reason you need them, let me know.

    12-May-22 13:21:03 INFO Starting Code Profiler v1.4.1 for ********************** (profile: 2022-05-12_361661)
    12-May-22 13:21:04 ERROR Error: E_ERROR (Uncaught Error: Class 'RT\ThePostGrid\Controllers\Admin\PostTypeController' not found in /home/********/public_html/wp-content/plugins/the-post-grid/app/RtTpg.php:83 – Stack trace: – #0 /home/********/public_html/wp-content/plugins/the-post-grid/app/RtTpg.php(61): RtTpg->__init() – #1 /home/********/public_html/wp-content/plugins/the-post-grid/app/RtTpg.php(69): RtTpg->__construct() – #2 /home/********/public_html/wp-content/plugins/the-post-grid/app/RtTpg.php(210): RtTpg::getInstance() – #3 /home/********/public_html/wp-content/plugins/the-post-grid/app/RtTpg.php(213): rtTPG() – #4 /home/********/public_html/wp-content/plugins/the-post-grid/the-post-grid.php(34): require_once('/home/********/…') – #5 /home/********/public_html/wp-settings.php(418): include_once('/home/********/…') – #6 /home/********/public_html/wp-config.php(108): require_once('/home/********/…') – #7 /home/********/public_html/wp-load.php(50): require_once('/home/********/…') – #8 /home/********/public_html/wp-blog-header.php(13): require_once('/home/ – line 83 in /home/********/public_html/wp-content/plugins/the-post-grid/app/RtTpg.php)
    12-May-22 13:21:04 ERROR The website returned the following HTTP status code: 500 Internal Server Error. By default, the profiler will always abort and throw an error if the server did not return a 200 HTTP status code. You can change that behaviour in the Settings section if the page you are profiling needs to return a different code (3xx, 4xx or 5xx).

    I add as additional data, that in addition to the recent update of Code Profiler, the app that appears in the error (The Post Grid) was also updated very recently. And it is the only one that causes problems. By disabling that application, I can run the profiler without problems and without making any configuration changes.

    Thanks.

    Plugin Author bruandet

    (@bruandet)

    The error was introduced in the latest version 4.0 of The Post Grid plugin, not in the latest version of Code Profiler. If you install the previous Post Grid version 3.1.5 everything is working as expected.
    I recommend to open a thread in the Post Grid’s support forum ( https://www.ads-software.com/support/plugin/the-post-grid/ ) and to show the error log to the developers, I’m sure they will be happy to give you more details about that error and maybe to fix it if they have to.

    • This reply was modified 2 years, 6 months ago by bruandet.
Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Check the latest update please’ is closed to new replies.