Hey @rpweb777,
Thanks for reporting this, and for including the FooGallery versions. That’s what let me reproduce it.
Here’s what happened. FooGallery 3.3.7 includes a library that 3.3.3 doesn’t. Right after WP Rollback swapped in the older files, PHP’s cache kept running some of the 3.3.7 code, which looked for the files that had just been removed and crashed. The rollback itself had already worked, but the crash hit WP Rollback’s last step, which is the one that turns maintenance mode back off.
WP Rollback 3.2.0 (coming soon), fixes both parts. It clears PHP’s cache right after replacing files, the same way WordPress does during an update, and it turns maintenance mode off as soon as the files are in place.
Maintenance mode turns itself off after 10 minutes, or you can delete the .wpr-maintenance file in your WordPress root folder (the same folder as wp-config.php). It only shows to logged-out visitors, so the site looks normal while you’re logged in as an admin.
Please let me know if you have any more questions and my apologies for the late reply!
Hi Devin,
thanks a lot for your helpful reply – and it wasn’t late!
Your information that the foogallery version 3.3.7 includes a new library could prove very helpful as well. The rollback to 3.3.3 was required because the new version triggers a server error on production sites but not on my development sites on localhost, despite everything being identical (plugins etc.). I’ll check if this library (‘action-scheduler’) has something to do with it (maybe some security settings in the hosting environment).
