• Has anyone else seen intermittent (and sometimes debilitating) white pages?

    Since 6.7.2, I’ve had many of my dashboard pages load as a white page. Reloading the page clears it up, but it’s been occurring off and on in nearly all my WP installs—it’s not specific to any one set-up.

    It’s even made one of my archived sites impossible to view (I’m technically “logged in,” but every site and admin page is just white—even the sliver of admin bar: white an unresponsive. The entire site is now inaccessible). After hours with my hosting co’s tech support last night, they were seeing errors that hinted at problems in WordPress Core (Permissions, permalinks, cache, htaccess, deactivating plugins and themes, downgrading php—nothing helps).

    I regret upgrading WP without thoroughly testing it on a junk site first.

    ?????♂?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator t-p

    (@t-p)

    – The exact reason for the errors should be visible in the error log, which you can find in your hosting area. If needed, your hosting provider’s support team can assist you with locating it.
    – Alternatively, you can enable debugging in WordPress to gather more information. To do this, add a few specific lines to your?wp-config.php?file. For full guidance and step-by-step instructions on enabling the debug log, refer to the WordPress Developer Documentation:?https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/.
    – In both cases, you should be able to identify the cause in the log file.

    You can also try:
    manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.
    – If that does not resolve the issue, access your server via SFTP or FTP, 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 (theme functions can interfere like plugins).

    Thread Starter kevinroman

    (@kevinroman)

    Ultimately, we ended up seeing a bunch of “Translation… triggered too early” errors for a handful of plugins, but even deactivating all the plugins and my active theme by FTP doesn’t make any changes.

    I’m pondering reinstalling WordPress by FTP or just trashing the whole site and rebuilding it from a backup—definitely not something I planned on needing to do just because of a maintenance WP release.

    Jorge Luiz

    (@jluizsouzadev)

    That after you enabled the WP debugging mode?

    The error/warning messages you mentioned above, were they got from the WP debugging mode?

    Please, if possible, post the messages you’ve got here in this thread, then we can analyze ones and try to find a possible solution.

    Thread Starter kevinroman

    (@kevinroman)

    [27-Feb-2025 05:20:38 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>updraftcentral</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href=”https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/xxxxxxxxxx/domains/xxxxxx.com/public_html/xxxxxx/wp-includes/functions.php on line 6114

    Several errors for plugins updraft central and wp-html-mail like the above before I deactivated all plugins. This was my main site that I replaced last night with a rebuilt version, so it only last night realized oh, it really is living archived in its own subdirectory now ?? (There’s now a new main site taking its place). When all the tricks that should have worked last night didn’t, I chocked it up to some galactic ghost cache hangin on from the planet Zoron (as good a guess!), and let it sit about 12 hours. Still stubborn this morning, but this afternoon I went in and deactivated the mu-plugins also (a staging and a disable-emails plugin) and then I finally could log in. Re-saved permalinks and slowly began activating some plugins and it’s holding steady.

    I pulled this site and db over from my last host a year ago and swore there was some cruft sticking around inside, which was why I rebuilt it this month. Let’s hope that’s what it was, though I’m keeping an eye on my other sites for any temporary white pages which might be a sign there’s something in 6.7.2 rubbing things the wrong way.

    ?????♂?

    In the new site, I only get a few such ‘deprecated’ errors. Everything is mostly running fine; keeping an eye out for any odd white pages:

    [28-Feb-2025 01:03:17 UTC] PHP Deprecated:  Creation of dynamic property Kirki\Field\Repeater::$compiler is deprecated in /home/xxxxxxxxxx/domains/xxxxxx.com/public_html/xxxxxx/wp-content/plugins/kirki/kirki-packages/compatibility/src/Field.php on line 305

    Jorge Luiz

    (@jluizsouzadev)

    Based on your log you posted here. Try to verify what PHP version your site’s running on. For that, on the Admin Dashboard, access the Site Health screen. Go to Tools > Site Health > Info.

    Then, check the PHP version against all the themes and plugins installed. Verify the minimum PHP version required.

    I presume by your log that could be ocurring some compability issue between your WP install, and your themes and plugins.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.