Viewing 10 replies - 31 through 40 (of 40 total)
  • @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.

    @omarreiss: I run a clone site of the original one, for testing and dev purposes.

    The original site is where the issue occurred.
    The cloned site is exactly the same as the original, and always updated at the same time as far as themes and plugins are concerned, with the sole exception that it doesn’t have the whole original site’s content and that I don’t have ALL plugins active (such as the cache one, etc).

    The same way, your SEO plugin was not active at clone site but I updated it and this test site still works.

    If you give me your email, I can give you full admin access to this testing site so that you may try activating latest version there by yourself and see what happens. There is no risk of damage there as everything is precisely for testing purposes.I will only ask you to revert back to original any changes you make there – other of course to those of your own plugin itself.

    PS: both sites are WPMU installations.

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

    Hi,

    I’ve managed to get version 2.3 working again.

    Here’s what happened and what I did to get around the Fatal Error.

    1. I clicked the update button for specifically Yoast SEO plugin version 2.2.1 on the Plugins page on my WordPress admin console.
    2. Upon updating, my entire website crashed and I got the error code “Fatal error: Call to a member function get() on a non-object in /home/ipadclub/public_html/mybeanbean.com/wp-includes/query.php on line 28”.
    3. I login to my CPanel, and accessed the File Manager. Went into WP-Content/Plugins/Wordpress-SEO folder and renamed it to WordPress-SEO-temp.
    4. My entire website was back online and the latest version 2.3 Yoast SEO plugin was listed as “Deactivated” in the Plugins page on my WordPress admin console.
    5. I went ahead and click “Activate” Yoast SEO plugin version 2.3 from the wordpress admin console.
    6. The latest version 2.3 of Yoast SEO plugin worked again without any trouble to my website.

    I hope this helps.

    Thanks @keanpoh, we’ve been getting similar reports. Apparently in many cases, the issue is resolved after deactivating and reactivating the plugin. I’ve gotta say that doesn’t make it easier for us to find what’s causing this. But it might help users get to the 2.3 version of Yoast SEO already, which includes lots of nice improvements and cool new features.

    I’ve just tried running the back trace code, as soon as updated the plugin it failed and gave me just same error as before:

    PHP Fatal error: Call to a member function get() on a non-object in /wp/www/cluster/mysite/wp-includes/query.php on line 28

    I’ve followed the instructions above from @keanpoh and that gets the plugin to work for me.

    I get the following output at the foot of the site

    Backtrace from warning ‘Undefined variable: transient’ at /nas/wp/www/server1/mysite/wp-content/plugins/untappd-checkins-widget/untappdwidget.php 221:

    /nas/wp/www/server1/mysite/wp-content/plugins/untappd-checkins-widget/untappdwidget.php 155 calling getTransient()
    /nas/wp/www/server1/mysite/wp-includes/widgets.php 329 calling widget()
    calling display_callback()
    /nas/wp/www/server1/mysite/wp-includes/widgets.php 1272 calling call_user_func_array()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/lib/structure/footer.php 51 calling dynamic_sidebar()
    calling genesis_footer_widget_areas()
    /nas/wp/www/server1/mysite/wp-includes/plugin.php 496 calling call_user_func_array()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/footer.php 17 calling do_action()
    /nas/wp/www/server1/mysite/wp-includes/template.php 501 calling require_once()
    /nas/wp/www/server1/mysite/wp-includes/template.php 477 calling load_template()
    /nas/wp/www/server1/mysite/wp-includes/general-template.php 85 calling locate_template()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/lib/framework.php 51 calling get_footer()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/index.php 15 calling genesis()
    /nas/wp/www/server1/mysite/wp-includes/template-loader.php 74 calling include()
    /nas/wp/www/server1/mysite/wp-blog-header.php 16 calling require_once()
    /nas/wp/www/server1/mysite/index.php 17 calling require()

    Backtrace from warning ‘rss.php is deprecated since version 3.0! Use wp-includes/class-simplepie.php instead.’ at /nas/wp/www/server1/mysite/wp-includes/functions.php 3448:

    /nas/wp/www/server1/mysite/wp-includes/functions.php 3448 calling trigger_error()
    /nas/wp/www/server1/mysite/wp-includes/rss.php 19 calling _deprecated_file()
    /nas/wp/www/server1/mysite/wp-content/plugins/xan-mania-lastfm-widget/lastfm.php 112 calling include_once()
    calling widget_lastfm()
    /nas/wp/www/server1/mysite/wp-includes/widgets.php 1272 calling call_user_func_array()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/lib/structure/footer.php 51 calling dynamic_sidebar()
    calling genesis_footer_widget_areas()
    /nas/wp/www/server1/mysite/wp-includes/plugin.php 496 calling call_user_func_array()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/footer.php 17 calling do_action()
    /nas/wp/www/server1/mysite/wp-includes/template.php 501 calling require_once()
    /nas/wp/www/server1/mysite/wp-includes/template.php 477 calling load_template()
    /nas/wp/www/server1/mysite/wp-includes/general-template.php 85 calling locate_template()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/lib/framework.php 51 calling get_footer()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/index.php 15 calling genesis()
    /nas/wp/www/server1/mysite/wp-includes/template-loader.php 74 calling include()
    /nas/wp/www/server1/mysite/wp-blog-header.php 16 calling require_once()
    /nas/wp/www/server1/mysite/index.php 17 calling require()

    Backtrace from warning ‘Undefined property: stdClass::$error’ at /nas/wp/www/server1/mysite/wp-includes/rss.php 497:

    /nas/wp/www/server1/mysite/wp-content/plugins/xan-mania-lastfm-widget/lastfm.php 130 calling fetch_rss()
    calling widget_lastfm()
    /nas/wp/www/server1/mysite/wp-includes/widgets.php 1272 calling call_user_func_array()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/lib/structure/footer.php 51 calling dynamic_sidebar()
    calling genesis_footer_widget_areas()
    /nas/wp/www/server1/mysite/wp-includes/plugin.php 496 calling call_user_func_array()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/footer.php 17 calling do_action()
    /nas/wp/www/server1/mysite/wp-includes/template.php 501 calling require_once()
    /nas/wp/www/server1/mysite/wp-includes/template.php 477 calling load_template()
    /nas/wp/www/server1/mysite/wp-includes/general-template.php 85 calling locate_template()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/lib/framework.php 51 calling get_footer()
    /nas/wp/www/server1/mysite/wp-content/themes/genesis/index.php 15 calling genesis()
    /nas/wp/www/server1/mysite/wp-includes/template-loader.php 74 calling include()
    /nas/wp/www/server1/mysite/wp-blog-header.php 16 calling require_once()
    /nas/wp/www/server1/mysite/index.php 17 calling require()

    @omarreiss: email just sent out.

    @everyone we’ve done a change that will hopefully solve your problem.

    Would you be so kind to test the beta we’ve created for you?

    You can download it here: https://uploads.yoast.nl/wordpress-seo-2.3.1-beta.zip

    We have received positive feedback from a couple of users. The patch (2.3.1) has been released. Marking this topic as resolved

    Worked also for me, thanks!

Viewing 10 replies - 31 through 40 (of 40 total)
  • The topic ‘White Screen with latest update’ is closed to new replies.