Skip to main content

Automatic Updates

How updates work​

Updates for the Flavor Starter Theme, the WP eCommerce Core Plugin, and Flavor Core itself are all managed from one place: the Flavor Dashboard in your WordPress admin. You don't use the standard WordPress Updates page for Flavor products.

When a newer version is available:

  1. Flavor Core checks automatically twice a day (every 12 hours).
  2. If a newer version exists, an amber Update to vX.Y.Z button appears on that product's card.
  3. Click it — the update downloads and installs on its own.
info

Flavor updates do not appear on the WordPress Dashboard → Updates page. Manage everything from the main Flavor page.

What you need to receive updates​

  • The Flavor Core plugin installed and active
  • An active, non-expired license
  • Your site activated on that license
  • Your server able to reach license.flavorteam.dev

Checking for updates manually​

Updates are checked automatically every 12 hours. To check right away:

  1. Go to the main Flavor page.
  2. Click Check for Updates.
  3. If anything is available, the update buttons appear on the relevant cards.

The dashboard also shows when your site last checked ("Last checked: … ago").

What gets updated​

Everything in your Flavor stack updates from the dashboard:

  • Products — the Theme, the Plugin, and Flavor Core itself. Each has its own card showing the installed version and, when a newer one exists, an Update to vX.Y.Z button.
  • Components — the individual payment gateways, shipping couriers, ERP modules and theme modules you have installed. These live in the Components tabs (Theme / Plugin / Core). When a component has an update, an Update v… badge appears next to it — click it to update just that component.

Components are checked on the same automatic 12-hour cycle as products.

note

Right after a product update, give the site a moment — the matching components finish downloading in the background (usually under a minute).

One-click update: what happens​

Every update is safe by design. When you click Update to vX.Y.Z, Flavor Core:

  1. Creates a backup of the current version first — automatically.
  2. Downloads the new version.
  3. Installs it only after confirming the download is complete and valid, so your live site is never left half-updated.
  4. Refreshes so the new version is active.

Your store data, settings and content are never changed by an update — only the product code is replaced.

Version history​

See what changed in each version:

Rolling back​

If an update ever causes a problem, you can return to the previous version yourself — no manual downloads, no support ticket needed.

Flavor Core saves a backup automatically before every update, so a restore point is ready whenever you need one.

To roll back:

  1. Go to Flavor → Rollback.
  2. Find the product or component you want to restore. Each shows the installed version and the available restore point (version, date and size).
  3. Click Rollback to vX.Y.Z.
  4. Confirm in the dialog. For a product you'll be asked to type the short confirmation text shown in the dialog; for a component you just confirm.
  5. Wait for the "Rolling back…" screen to finish.

You can roll back:

  • Products — the Theme, the Plugin, or Flavor Core.
  • Components — an individual module, gateway or courier, listed under Theme / Plugin / Core Components (only items that have a restore point appear here).
info

A rollback never touches your data. Only the product code returns to the earlier version — your products, orders, settings and content stay exactly as they are. (Database changes made after the backup are not reversed.)

Keeping more than one restore point​

By default Flavor Core keeps the most recent backup for each item. To keep more (up to three), open Flavor → Rollback, click ⚙ Settings, and choose how many backups to keep per item. Keeping more uses a little more disk space but lets you step back through several versions. The same panel shows how much space your backups currently use.

If there's no restore point​

A restore point only exists once an update has run on your site — the backup is made just before that update. If a product shows "No restore point yet", update it once and the previous version becomes available to roll back to.

caution

Rollback restores product code, not your database. Before a big change it's still good practice to keep your own full-site backup as well.

Testing upcoming versions (Beta)​

Prefer to try new versions on a staging site before they reach everyone? You can opt a site into the Beta channel. See Release Channels for how to request access and switch a site over.

Last updated on