White screen of death after upgrading to 5.3.0

  • Resolved Jakob Smith

    (@diakrisis)


    6 years, 8 months ago

    After upgrading to version 5.3.0 from 5.2.4, I’m getting a white screen of death in the frontend of the site (not in wp-admin).

    I’m getting these errors (sitespecific information removed):

    [14-Mar-2018 00:37:44 UTC] PHP Fatal error:  Uncaught Error: Cannot instantiate abstract class WP_Typography in /wp-content/plugins/wp-typography/includes/wp-typography/data-storage/class-transients.php:120
Stack trace:
#0 /wp-content/plugins/wp-typography/includes/wp-typography/data-storage/class-transients.php(120): unserialize('O:23:"PHP_Typog...')
#1 /wp-content/plugins/wp-typography/includes/wp-typography/class-implementation.php(263): WP_Typography\Data_Storage\Transients->get_large_object('php_settings_2a...')
#2 /wp-content/plugins/wp-typography/includes/wp-typography/class-implementation.php(374): WP_Typography\Implementation->get_settings()
#3 /wp-content/plugins/wp-typography/includes/wp-typography/class-implementation.php(350): WP_Typography\Implementation->process('removed...', true, true, NULL)
#4 /wp-includes/class-wp-hook.php(286 in /wp-content/plugins/wp-typography/includes/wp-typography/data-storage/class-transients.php on line 120

    I reverted to 5.2.4 as a temporary solution.

Viewing 15 replies - 1 through 15 (of 21 total)

  • I have also been having some problems with the new typography update. The first prob (now I forget the exact error) I managed to fix .. just as I was about to post about it … by going into the plugin settings and selecting “clear cache.” However, now I am getting a new error, and cannot access the site:
    Fatal error: Cannot instantiate abstract class WP_Typography in /home/user/domain/includes/wp-typography/data-storage/class-transients.php on line 120

    Plugin Author pepe

    (@pputzer)

    I am sorry to hear that, @drriley and @diakrisis. Can you tell me something about your WordPress installations? PHP version? WP version? Are you using a persistent object cache plugin?

    I know what change is causing the issue, I’m just not sure why and I haven’t been able to reproduce it locally yet.

    @drriley: If you can’t get to the WordPress backend of your installation, you will have to change to the wp-content/plugins directory and rename wp-typography/ to something else to disable the plugin.

    Thread Starter Jakob Smith

    (@diakrisis)

    PHP: 7.0.28
    WP: 4.9.4
    Nginx: 1.10.3

    I’m not using a persistent object cache plugin.

    Theme:
    GeneratePress 2.0.2 with a child theme.

    Active plugins:
    Activity Log
    Advanced Sidebar Menu
    Breadcrumb NavXT
    CMS Tree Page View
    Co-Authors Plus
    Content Blocks (Custom Post Widget)
    Decent Comments
    Delete Expired Transients
    Disable Feeds
    Disable REST API
    Donation Thermometer
    Download Manager
    Easy FancyBox
    Email Log
    Fluid Video Embeds
    GP Premium
    Image Gallery Import
    iThemes Security
    Loco Translate
    Members Only
    My Calendar
    Peter’s Post Notes
    Remove Dashboard Access
    Shortcodes Ultimate
    Sidebar Login
    Soliloquy
    Subscribe to Comments Reloaded
    Subscribe2
    UpdraftPlus – Backup/Restore
    WP-Optimize
    WP-PageNavi
    WP-SimpleViewer-v1
    wp-Typography
    WPDM – TinyMce Button
    My own functionality plugin

    Plugin Author pepe

    (@pputzer)

    Thanks, that looks all quite normal. I’ve reverted the stable version to 5.2.4 for now to further investigate this issue.

    Plugin Author pepe

    (@pputzer)

    @diakrisis Just to be sure: You are not using the API class WP_Typography in your custom plugin?

    Thread Starter Jakob Smith

    (@diakrisis)

    No, I am not.

    Same problem here, had to disable the plugin to fix the blog.

    Plugin Author pepe

    (@pputzer)

    @firmdot, @diakrisis, @drriley: The backend has always remained accessible? The error has remained after using the “Clear Cache” button? In that case, it might be triggered by a setting. Could you maybe post screenshots of the settings tabs?

    Just to confirm this is also happening on client site.
    With upgrade to wp-typography 5.3.

    Bill

    (@chubbycrow)

    I also had the white-screen result with 5.3. I deactivated the plugin and left it that way while gone for a few hours. On reactivation the problem has gone away, and still seems functioning fine. Plugin cache? Browser cache?

    Thread Starter Jakob Smith

    (@diakrisis)

    Well, maybe I should just try deactivating/reactivating or “Clear cache”, but where can I get version 5.3.0 again?

    Thread Starter Jakob Smith

    (@diakrisis)

    Found out that I could use WP Rollback to upgrade to 5.3.0 again.

    I then went to the settings and clicked “Clear cache” and the issue is now resolved.

    Bill

    (@chubbycrow)

    Great. Maybe that’s all it takes?

    Plugin Author pepe

    (@pputzer)

    @drriley Can you weigh in on that? It looks like everyone else still has access to the admin backend and was able to fix things by using “Clear Cache”. Can you confirm trying that for the new error? Or might an additional thing be going on your site (e.g. another updated plugin)?

    If so, could you please look at your PHP error log for any additional information?

    @andybroomfield: Can you please also try to “Clear Cache” from the wp-Typography settings?

    @diakrisis, @chubbycrow: Thanks for fiddling with this. I’ve so far not been able reproduce the issue. My best guess is that you somehow had never changed settings since the initial 5.2.0 update (there was an issue with circular references in that release). In that case, clearing the cache should be enough to force creation of a new settings object without the incorrect reference to WP_Typography. (I had assumed that upgrading already cleared the transients, but maybe I changed that in the 5.0.0 refactoring.)

    @pputzer yes, clear cache has fixed the issue, thanks.

Viewing 15 replies - 1 through 15 (of 21 total)
  • The topic ‘White screen of death after upgrading to 5.3.0’ is closed to new replies.