Omar Reiss

Thanks John, that sounds good. Please send an email to [email protected] with the admin details and we’ll have a look.

@lehrer79 there’s a couple of things you could still try:

1) please make sure you include the snippet at the end of your wp-config.
2) Uncomment the line at the bottom of the snippet to see if it’s working. This can be done by removing the backslashes in front of that line. Then recomment it again once that’s verify. The line I am talking about looks like this //trigger_error( 'Testing 1..2..3.. Debugging code is working!', E_USER_NOTICE );
3) Make sure WP_DEBUG is set to true.

Hopefully this will give you a better error in your browser. Please share anything you can find.

You can also edit the path in this line to something that exists on your server: @ini_set('error_log', '/path/to/writable/file/logs/error.log'); This should give you an error log which I would really like to see. If you are able to produce it, could you please send us a copy at [email protected]?

Thanks a lot for your help so far in getting to the bottom of this.

@lehrer79 It’s the same snippet. Let me see if you need to configure anything else.

@catseo If you re-install wordpress-seo, you should have your settings back. You could try again to install the latest version. If that doesn’t work, you can install 2.2.1, which is the previous version.

Thanks lehrer79. All that tells me is that you have quite a lot of notices that are unrelated to this update, except for one:

“Fatal error: Call to a member function get() on a non-object in blog/wp-includes/query.php on line 28”

which is the error we’ve been talking about. What I would like to have is a callstack/backtrace/stacktrace which tells me which code was executed before the error was raised so I can locate the origin of the issue in the code. From there I’d have something to work with.

If you are able, could you include this snippet of code in your wp-config.php and see if you could raise the error again? https://gist.github.com/jrfnl/5925642

For more advanced users experiencing this issue:

Here’s an article that can help you get a stacktrace: https://www.barrykooij.com/white-screen-wordpress/

We understand there is an issue with wp_query, but we are unsure what’s causing it. For that we need to see from where wp_query was called

For more advanced users experiencing this issue:

Here’s an article that can help you get a stacktrace: https://www.barrykooij.com/white-screen-wordpress/

We understand there is an issue with wp_query, but we are unsure what’s causing it. For that we need to see from where wp_query was called.

Ok, so three different issues have been reported (by order of impact):

1) Fatal error: Call to a member function get() on a non-object in /domain/public_html/wp-includes/query.php on line 28

Reported: ~10 times

So far, we are unable to reproduce the issue. We would greatly appreciate a backtrace for this error. We think this is a plugin/theme conflict. We’d appreciate it if someone experiencing this error would disable all plugins except Yoast SEO and see if the issue still occurs. Please share plugin lists / themes used / PHP version / WordPress version.

2) Error: Call to undefined method Yoast_Api_Libs::load_api_libraries()

Reported: 3 times

The issue pops up in combination with versions of Google Analytics by Yoast older than 5.4.3. Can be solved by updating Google Analytics by Yoast to its latest version (currently 5.4.4)

3) “Your PHP installation appears to be missing the MySQL extension which is required by WordPress.”

Reported: 1 time

This seems to be completely unrelated to our plugin. Re-installing Yoast SEO seemed to have fixed the issue.

Like I said, you will not lose any data when uninstalling the plugin and installing 2.2.1 or a newer version.

KKerstin, you don’t have to worry about losing SEO settings. All settings and Post metadata remains in your database.

You can for the time being install WordPress SEO 2.2.1 in order to still have SEO functionality.

KKerstin I’m afraid you’ll have to rename the wordpress-seo folder on your server by using FTP or the File Manager in your host’s control panel (if there is one).

Then wait for us to release an update to resolve this issue. So far, we have not come up with a solution since we are unable to reproduce the issue.

TobyGr, I think that might very well be the problem, but I have no clear indication of anything in Yoast SEO causing that. Could you maybe get me a backtrace of the error and a list of plugins/themes/WP version/PHP version? I cannot reproduce.

@anjamo If I understand correctly, Google Analytics works fine now and Yoast SEO won’t activate anymore? I recommend you delete the Yoast SEO folder and install it again via the plugins installer.

Thanks @brightestspark.

@anjamo, that’s really strange, since you error refers to a piece of code that is no longer included in GA 5.4.4. It should technically be impossible for you to receive this error if you are running the latest version of GA. Could you try to uninstall Google Analytics for WordPress and install it again via the plugins installer?

@everyone We’re doing our best to reproduce the issue and find what’s causing it.

Is there maybe someone here who could get us a longer stacktrace from their server logs?

The reason we think this could be a plugin/theme conflict is because in most cases the update seems to work fine and plugin conflicts are actually a very common cause for these kinds of issues. Thereby we are not saying it’s another plugin’s or theme’s fault. We just want to find out if another plugin or theme is conflicting with ours so we can find the cause of that conflict and have it fixed.

anjamo if you install the latest version of Google Analytics for WordPress (5.4.4) you should be fine.