From WP v5.3.2 used Switch to ClassicPress - it wasn’t sure about something but said it was ready to go. Progress was displayed quickly, then the blank screen appeared. Later the site was on ClassicPress. Seems to be stable after that, but not a reassuring first experience.

[image] james: That was Error: undefined function `classicpress_version()` immediately after migration · Issue #288 · ClassicPress/ClassicPress · GitHub from a while ago. Makes sense, I guess I kept looking at issues on ClassicPress/ClassicPress-Migration-Plugin - I can do some test on Larave…

Hi James, I didn’t have a screenshot but I think it had already upgraded at that point as I saw the status lines flash past quickly before it went blank - it was trying to display the post-upgrade page URL (it just appeared blank but I did not check page source.) Maybe I can go back to a previous b…

One of the quick (temporary) solution can be just write a warning, that “during migration your screen can be Black/White/BeerAd, don’t panic, this is the caching (or, whatever it can be) consequence, migration still in progress, reload after a few beer.” This will reduce stress significantly.

I’ve been able to reproduce (but not isolate) this. The following after restoring the ClassicPress site to WordPress v5.3.2 and restoring all user content. ( it’s not a 100% image as I can’t justify rolling back that server.) Run Switch to ClassicPress URL appears: /wp-admin/about.php?updated (…

[image] LinasSimonis: One of the quick (temporary) solution can be just write a warning, that “during migration your screen can be Black/White That may help, for now.

Got some error messages with WP_DEBUG true. Hope it helps. ( @james ? ) Switching from WordPress v5.3.2 to ClassicPress https://URL_REDACTED/wp-admin/about.php?updated Fatal error: Uncaught Error: Class 'ParagonIE_Sodium_Compat' not found in /path_redacted/htdocs/wp-includes/sodium_compat/lib/…

Thanks for the additional info. It looks like your web server is loading old versions of some files (something that requires sodium_compat, and something from the fatal error handler, neither of which we include in ClassicPress). This does not represent the order in which things actually happen dur…

Could this be an issue with OPcache? Just searching around, here are a couple of threads I came across: Apache not reading changes to PHP files Delay in page refresh

Could be. I’m not very familiar with the PHP opcache, but if that’s what it is then the fix should be as simple as calling opcache_reset after an upgrade completes: if ( function_exists( 'opcache_reset' ) ) { opcache_reset(); }

Blank screen when using the migration plugin

Support

ozfiddler February 25, 2020, 8:22pm 10

This sounds similar to a problem I had. It varied, but mostly was stalling and leaving me stuck in maintenance mode. It was hosting-related.