• Resolved Robert Poth

    (@rpweb777)


    I used the plugin to roll back the plugin FooGallery from 3.3.7 to 3.3.3, which ended with an error message saying that the rollback didn’t work. Actually it did work, but WP Rollback kept the whole site in maintenance mode. The only way I could solve this issue was to delete WP Rollback and install it again.

    Is there another way to get WP Rollback to turn off the maintenance mode, without deleting/reinstalling?

    Up to now, this has happenend only with the mentioned FooGallery versions.

Viewing 1 replies (of 1 total)
  • Plugin Author Devin Walker

    (@dlocc)

    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!

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.