after upgrade to 4.9.2 my site is gone – just a white screen

Hi @krinake.,

Try downloading WordPress again, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and delete then replace your copies of everything except the wp-config.php file and the /wp-content/ directory with fresh copies from the download. This will effectively replace all of your core files without damaging your content and settings.
Some uploaders tend to be unreliable when overwriting files, so don’t forget to delete the original files before replacing them.

If you want further help I’ll be happy to assist.

Thanks.,
Rajan V

So I did that. Now when I try to access my site I see this:

Warning: require_once(/hsphere/local/home/vinnie/jliacademy.org/wp/wp-includes/widgets/class-wp-widget-archives.php): failed to open stream: No such file or directory in /hsphere/local/home/vinnie/jliacademy.org/wp/wp-includes/default-widgets.php on line 20 Fatal error: require_once(): Failed opening required ‘/hsphere/local/home/vinnie/jliacademy.org/wp/wp-includes/widgets/class-wp-widget-archives.php’ (include_path=’.:/hsphere/shared/php53/include/php/PEAR’) in /hsphere/local/home/vinnie/jliacademy.org/wp/wp-includes/default-widgets.php on line 20

Since I deleted the wp-includes folder . . .

Feeling a little sick . . .

okay. I re-uploaded the class-wp-widget-archive file. Now my site is again just a white page, as it was before I reloaded 4.9.2. Note that original upgrade to 4.9.2 was from my admin page, second was from a downloaded copy of 4.9.2 through my webhosting file manager.
Any ideas?

Another note: I’ve deactivated all plugins that don’t specifically say they are compatible with 4.9.2 — no change. Site is still a blank white screen.

Can you find errorlog file?

I had to add the debug function to the wp-config file. I did that, defining debug & debug_lot to true. But I don’t see a debug.log file in the wp-content. Any ideas?

Went to the gym, then attempted to reload the site a few times. The debug file has materialized. Here’s the entire contents:

[25-Jan-2018 18:48:21 UTC] PHP Notice: Undefined index: moesia-masonry-portfolio/moesia-masonry-portfolio.php in /hsphere/local/home/vinnie/jliacademy.org/wp/wp-content/plugins/moesia-masonry-portfolio/wp-updates-plugin.php on line 45
Next steps?

I do have current version of Moesia-masonry-portfolio installed and activated . . .

• This reply was modified 6 years, 10 months ago by krinaker.

error_log file located in your main root folder

Just rename “moesia-masonry-portfolio” this plugin then try

Thanks
Rajan V

I don’t understand what I’m supposed to rename? I could deactivate or delete the Moesia – Masonry Portfolio plug in from my admin page. I guess I can rename the plug in itself from my hosting control panel.

Still can’t find anything called error log anywhere. The snippet that targets the masonry portfolio is from a file called “debug.log” that’s located in my wp-content folder.

RE: Moesia-Masonry-Portfolio: Deactivation – no help. Renaming file – no help.

Found a log – not called error log. Latest entry is:
66.249.69.213 – – [25/Jan/2018:02:19:39 -0500] “GET /wp/wp-content/uploads/2017/06/gravity-207×300.png HTTP/1.1” 304 – “-” “Googlebot-Image/1.0”

Had with a client’s site the same problem after updating to 4.9.2 (caused by a 3rd party theme).
Adding this to wp-config.php did the trick:
define(‘WP_USE_EXT_MYSQL’, true);

Note: In this case WordPress defaults to mysql instead of mysqli. Since PHP 7.0 does not support mysql anymore, you are limited to PHP 5.6 or lower. So if this work, it is more a work around rather than a real fix.

Sigh. No luck adding the mysql definition. I am using theme Moesia from Athemes. I’m on php5. I have access to admin page — but have kept that open since this happened, so not sure whether I could access it again or not. The site is just a blank white screen.

Rolling back to earlier wp seems difficult. Would it be worth it to try that?

Okay, got it – the hard way, of course. I managed a manual roll back of WP. That involved deactivating all plugins. As I reloaded them I discovered that SlimStat plug in was the culprit. Maybe the whole rollback was unnecessary, but my site is back up, so I’m happy. Thank you Rajan & webtailors for your support during this, for me, stressful learning process.