Update the core
Appearance Software update shows your version and installs a new one in one click.
- Download and check
The release is installed only if it carries a valid signature from WowCodes and every file matches it. A tampered or unsigned download is refused.
- Swap the files
While the files change, the storefront shows a short maintenance page. The admin stays open.
- Update the database
Missing tables, columns and indexes are added, and columns are only widened, never narrowed. Take a backup of your files and database before any update all the same.
- Health check
If the store doesn't come back healthy, the update is rolled back to the version you had.
The work is done in short steps, so it runs on shared hosting with the usual 30-second limit per request. If you need to, you can roll back one version from the same page.
Update plugins and themes
On Plugins and on Appearance Themes, press Check for Updates. It has three tabs:
- New: what your licence includes that isn't installed yet.
- Needs update: what has a newer version. Update one, or use Update all.
- All entitled: everything your licence includes.
Every package is signed. One that fails the check is never installed, and neither is an unsigned one. If a plugin's new version needs a newer core, it says so, and you update the core first.
What an update replaces
A core update replaces the core files, so any change you made to them is lost. A plugin or theme update replaces that plugin's or theme's whole folder, so edits inside it are lost too.
| What | On a core update |
|---|---|
Your settings file, .htaccess, .user.ini | Your own rules are kept. The store's routing block is added to .htaccess if it is missing. |
plugins/, storage/, logs/, admin/uploads/ | Never touched. Plugins update on their own. |
images/, assets/themes/, games/ | New files are added; existing ones are never overwritten. Themes and games update on their own. |
| Everything else | Replaced with the new version. A core update never deletes a file. |
Where to put your own changes
- Settings, content, menus, the homepage, translations and policies live in the database and survive every update.
- Code changes belong in a plugin of your own: a folder in
plugins/with aplugin.php. The admin's built-in guide shows how to write one. - Design changes belong in a theme of your own, in its own folder. See Customising a theme.
Add-ons
The Add-ons page, linked from Plugins and Themes, has two tabs:
- Browse: plugins, themes and bundles your store can buy, by category.
- Owned: what you own, with buttons to install and switch it on.
Buying uses your linked WowCodes account or a card checkout, and only the main Administrator can buy. Staff who manage settings can install what you already own.
Upgrading a store from an older version
If your store runs a BidKing version from before the plugin system, you can upgrade it in place. Your products, customers, orders, wallets and settings stay. It's the usual upload with one extra step: the setup wizard brings your database up to date.
This path has been tested on stores built on the PrizeX layout. If your store was customized, open a ticket before you start.
Before you start
- Back up your files and your database with your host's backup tool or a phpMyAdmin export, and keep the copy until you've checked the upgraded store.
- Keep a copy of anything you changed yourself. Code you edited and theme files you customised are replaced by the new version's files and aren't carried over; you'll need to re-apply those changes afterwards. Your logo and uploaded images are kept.
- Have your database name, user and password to hand. The wizard asks for them.
- Have your purchase code ready.
- Pick a quiet time. The store is offline from the upload until the wizard finishes.
Upgrade
- Upload all of the new version's files, not just some, over your store's folder, replacing the files that are there. Your own logo and images are kept.
- Open your site. The setup wizard starts.
- In the first three steps, check the requirements, enter your site details and purchase code, then your existing database's details.
- The wizard finds your store's data. Choose Keep the data and continue. Don't choose an option that deletes.
- Check your store name and settings. Your existing admin accounts are kept.
- The add-ons your store had switched on are ticked for you, and a feature you had switched off stays off. Continue to install them.
After upgrading
- Cron: straight away, replace your old cron entries with the one line the wizard's last page shows, which runs
cron/dispatch.php(Settings › Security Logs › Cron Logs shows it again later). Old entries run only some jobs, and one that calls a web address without your cron key does nothing, so until you change them, timed listings may not close and draws or payouts may wait. - Payment gateways: open Settings › Payment Gateways, switch on the gateways you use and check their keys.
- Customer wallets: if the Dashboard says customer wallets need correcting, open each listed customer and set their wallet to the right amount. Once none is left, click Finish the wallet switch on the same card to switch wallets to exact amounts. Do this soon after upgrading: until then, a few add-ons may save a balance with fewer decimal places than usual.
- Seller balances: on a marketplace store, a Dashboard card lists any seller balance the update didn't move. Settle each one yourself, then set the old balance to 0.
- Email templates: templates you had reworded are kept aside, and the store uses the new ones. The wizard names the reworded ones; copy any wording you want into Marketing › Notifications › Templates.
- Referral codes: where two customers shared a code, the one who signed up first keeps it and the other gets a new one.
Something wrong or unclear on this page? Tell us at [email protected], or see how to get help.