WowCodesDocs

An add-on or theme won't install or update

Add-ons and themes are checked before anything on your site changes: their signature, the versions they need, and whether your server can unpack them. A refused install or update leaves the installed copy as it was, and the message says which check failed.

Messages and what to do

MessageWhat to do
"Server is missing the Zip extension; cannot install packages."Ask your host to switch on PHP's zip extension, then try again.
"Install directory is not writable."PHP must be able to write to plugins/ (add-ons) or assets/themes/ (themes). See Folders your store must be able to write.
"… needs Kernel 1.x or later; this site runs 1.y. Update the site from Software update first."The add-on was made for a newer core. Update the core in Appearance Software update, then install the add-on again.
"… needs another plugin x or later (this site has y). Update it from Plugins first."Update the plugin it names, then try again. Themes ask for this when they style a plugin's pages.
"… is older than this site supports; it needs x or later. Install a newer version of it instead."Your core is newer than this copy of the add-on. Get its latest version with Check for Updates.
"The package is not signed, so it was not installed." / "…failed its signature check…" / "…signed with a key this site does not trust."Packages from the licence server are signed, and a package that fails the check is never installed. Download it again with Check for Updates; don't install a copy that was opened and changed. If it keeps failing, email us the message.
"This store uses virtual coins only, so "…", which moves real money, can't be switched on."Rewards (coins-only) stores can't run payment gateways, payouts or other add-ons that move money. This is by design.
"A plugin named "…" is already installed."Update it from Plugins instead of installing it again.
"This plugin contains code that can run commands or is obfuscated"The message lists the files. Review them, and only tick "install anyway" if you trust where the plugin came from.
"Could not move the plugin into place; the installed version was kept."Usually a full disk or a permissions change. Free some space or fix the folder's permissions, then try again.

An update shows but won't install

Check for Updates on Plugins and Appearance Themes offers the newest version your core can run. When an even newer one needs a newer core, it's shown so you know to update the site, but it's never installed, not even with Update all. Update the core first, then check again.

A strip warns about a plugin or theme

A strip at the top of your admin pages warns when something switched on can't fully run: a plugin older than your core supports, a plugin whose required core is newer (usually after rolling back), a plugin that failed while loading, or a theme that needs a newer core or plugin. It keeps running where it can. Update what the strip names. The Plugins page shows the full details.

An add-on you own isn't offered

  • Your store downloads add-ons from the licence server, so it needs outgoing HTTPS. If it can't connect, see Licence and activation problems.
  • Bought add-ons show on the Owned tab of the Add-ons page, with buttons to install and switch them on. If the licence server refuses your store, that page links to the licence page to verify it.

More on the add-on store in Add-ons and themes.

Something wrong or unclear on this page? Tell us at [email protected], or see how to get help.