Skip to main content

Upgrading tenants

Let's say you want to upgrade your product. You want to add WooCommerce so your customers can quickly start selling stuff online. How do we handle this?

First, create a new version and call it 'v2'. In the version's Snapshot Editor (click the Editor button), add the WooCommerce plugin. After it has been installed succesfully, head back to the console and Deploy the snapshot.

Now, head to the tenant you created in the previous part. You'll find the Move to version button under the Actions dropdown in the upper right corner. Click it and select the 'v2' version, the one you just now created.

After the move is complete, you'll find that you can activate WooCommerce in the tenant. It now has access to that plugin because a snapshot was deployed there with that plugin.


Note that even if you activated WooCommerce in the snapshot, it was not activated in the tenant. This is because the tenant's database is kept intact throughout its lifecycle.

Why would you create a new version just to add a plugin? Couldn't you just add the plugin in the Snapshot Editor of 'v1' and deploy that snapshot? Yes, you could - for a while. When you're working with 10, 20 or 1000 websites, you don't want to make changes to the whole product without safety measures. WPCS Versions are that safety measure. You can test out your changes before moving all your tenants over. Found the exception to the rule? That one tenant that has a certain setting that you didn't anticipate? Simply move it back and fix the problem in peace.