WordPress Static Build Revert & Rollback Functionality

Next up on the long list of most-requested features is the ability to revert and rollback to a previous Static deploy.

First, Let’s set the context

Anytime you initiate a push — full, partial, deletion, or single page — the following workflow happens:

1. We convert the page(s) to Static on your WordPress website
2. We send those Static files to Cloudflare
3. Cloudflare deploys your site fully Static with those changes. This is what your end user interacts with.
4. It marks that version as your latest deployment branch

We show you all of these logs in the Cult Portal on a site-by-site basis. 

The build logs are essentially a full “backup” and/or historic versions of your site as it develops.

How You Can Revert to a Previous Static Version

Now, as you review the last 20 most-recent build logs, you can select one to revert to by simply clicking the “Revert Here” button.

Again, think of build logs like “backups” of your site.

Reverting restores you that “backup” or previous version.

But, As Opposed to Traditional WordPress: It’s Fast as Hell

Because this is a Static Repository of files, you don’t have to wait for database, files, and all that to spin back up, overwrite, and then deploy.

Cloudflare Static deployments revert nearly instantly within just a few seconds.

This GIF is in real time.

When You’re Done, It Records History

Reversions are specified with the date and time they were initiated and completed.

You can also revert back later, if you need by clicking “Revert Again.”

Cloudflare Network Users Only

If you’re using our Enterprise AWS integration, this option is not available at this time.