WP 6.7.1 results in error 500

[dapike]

Yesterday my WP site was on version 6.7 and was working fine.

Today it automatically updated to 6.7.1 and I am now unable to perform admin functions. When I attempt to do so (for instance, when I login to the admin dashboard), instead of seeing a webpage (with the dashboard, for instance) I get a single line of text appearing in my web browser with info about my IP address, my browser, etc., and "500" at the end of the line.

[desrosj]

Thanks for this, @dapike. And welcome to Trac!

Let's try to get to the bottom of this. First, linking the possibly and suspected related tickets for context: [59430]/#62337.

Could you take a look in your debug.log? If you're unfamiliar, it's in the wp-content folder.

Some additional questions:

• Is the front end of your site loading and working fine?
• What is the default language for your site?
• Have you tried the usual ​common troubleshooting items (especially reinstalling WordPress via FTP to ensure all of the files were updated properly)?
• Do you have any translation related plugins active?
• What theme are you using?

[dapike]

There is no file named debug.log in the wp-content folder on the website.

The only language used on the website is English.

The front-end of the site does seem to be working normally (the site is www.fhsnl.ca)

No, I have not tried doing a manual re-installation.

No, there aren't any translation plugins in use.

The theme is (if I recall correctly) Weaver Xtreme.

[desrosj]

The debug.log file will only be created if you have WP_DEBUG_LOG defined as true in your wp-config.php file (​docs).

Make sure to also include define( 'WP_DEBUG_DISPLAY', false ); if it's a production site so that error messages won't display on the front end.

Then click around the site and reproduce the problem, and check if the log file has anything relevant in there.

[dapike]

I've revised the wp-config.php file and the debug.log file has been created. There are four recurring messages:

PHP Deprecated: Function create_function() is deprecated in /home/fhsnl/public_html/wp-content/plugins/baw-login-logout-menu/bawllm.php on line 13

PHP Notice: Function is_feed was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. Please see <a href="​https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.1.0.) in /home/fhsnl/public_html/wp-includes/functions.php on line 6114

PHP Notice: Function wp_deregister_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>admin-bar</code> handle. Please see <a href="​https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /home/fhsnl/public_html/wp-includes/functions.php on line 6114

PHP Notice: Function wp_deregister_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. This notice was triggered by the <code>admin-bar</code> handle. Please see <a href="​https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /home/fhsnl/public_html/wp-includes/functions.php on line 6114

[swissspidy]

Hmm, these are just notices from the baw-login-logout-menu plugin, they shouldn't cause any 500 error. Are you still seeing that error? Any other messages in the log file when that error happens? Can't hurt to temporarily disable the baw-login-logout-menu plugin and try again.

[dapike]

Yes, the error still happens, when I try to edit a page, when I try to view users, and when I simply logging in as admin to get to the admin dashboard. Because I cannot access the dashboard or other admin functions, I cannot disable any plugins as you suggest.

The debug_log only contains the four messages (multiple times) that I previously mentioned.

However, I have now noticed that the error_log has an entry from Nov 21st as follows. There are no subsequent entries in the error_log.

[21-Nov-2024 23:50:29 UTC] PHP Fatal error: Uncaught Error: Call to undefined function wp() in /home/fhsnl/public_html/wp-blog-header.php:16
Stack trace:
#0 /home/fhsnl/public_html/index.php(17): require()
#1 {main}

thrown in /home/fhsnl/public_html/wp-blog-header.php on line 16

[dapike]

Here's the error message again, this time with better formatting:

[21-Nov-2024 23:50:29 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wp() in /home/fhsnl/public_html/wp-blog-header.php:16
Stack trace:
#0 /home/fhsnl/public_html/index.php(17): require()
#1 {main}
  thrown in /home/fhsnl/public_html/wp-blog-header.php on line 16

[dapike]

This bug continues to affect my website. I'm wondering when a patch might become available. Thanks.

[desrosj]

@dapike I'm sorry that you're still experiencing problems with your site. I am still unable to reproduce the problem with the steps provided. Unfortunately, a patch cannot be created until others can reliably reproduce the issue and the cause can be determined.

Are you able to spin up a staging or local copy of the site to see if the problem still occurs? Could you try deactivating plugins one by one to see if the issue resolves? If you could, please also reach out to your hosting company to see if they can share any additional insight into what is happening.

[dapike]

I don't know how to spin up a copy of the site. I'm also unable to try temporarily deactivating plugins, since the bug is preventing me from accessing the WP admin dashboard.

I can reach out to the hosting company and see if they have any comments.

Meanwhile, I have a question: is there an easy way to revert to WP 6.7 ?

Thanks.

[Ipstenu]

Hi @dapike - So this appears to be an issue with your specific install, and not a widespread one in WordPress. That means the support forums are your best choice for help (trac tickets are for issues with WP core)

Downgrading can be done, but it's very risky unless you have a solid backup and know how to restore it.

Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don't have access to your admin panel, try manually resetting your plugins (No Dashboard access required!! You don't have to be able to log in to do this!).

​https://wordpress.org/support/article/faq-troubleshooting/#how-to-deactivate-all-plugins-when-not-able-to-access-the-administrative-menus

If that resolves the issue, reactivate each one individually until you find the cause.

If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don't have access to your admin panel, access your server via SFTP or FTP ( ​https://wordpress.org/support/article/ftp-clients/ ), or a file manager in your hosting account's control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

If that does not resolve the issue, it's possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account's control panel, and rename the .htaccess file. If you can't find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we'll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

If you need further assistance, you should post about this in the forums.

[dapike]

@Ipstenu Thank you for the link with instructions on how to disable all plugins (via the ftp method) and then reactivate them one at a time. This enabled me to get back in to the admin dashboard. And yes, the issue appears to have been a plugin conflict (specifically with the former bbp-toolkit plugin).