The same three steps for every plugin we publish. The commands, with the figures filled in, are on the WordPress plugins page.
1. Download
Two ways, and the page gives you both:
- The archive. Fetch the release and unpack it into
wp-content/plugins. - git clone. Only if git is on the server. Updating is then one
git pull.
Either way the folder name matters: WordPress identifies a plugin by the directory it sits in, so unpack it as the page names it rather than renaming it.
2. Verify what you downloaded
The page publishes a checksum for each release, taken from the published file rather than typed by a person — which is the only reason checking it is worth the thirty seconds. Run the command the page gives you and compare.
If it does not match, do not install it. Download it again; if it still does not match, tell us.
Important
A checksum somebody typed by hand goes stale and teaches people to skip the check. Ours are measured from the release. If one ever fails, treat it as real.
3. Activate
In WordPress, Plugins → find it → Activate. Or wp plugin activate with the folder name, if you use WP-CLI.
Some plugins need WooCommerce active first. The plugin says so rather than half-working, and its page lists what it requires.
Updating
Fetch the current release and unpack it over the folder, or git pull if you installed that way.
Your settings survive an update. They are stored in WordPress, not in the plugin folder, so replacing the files changes nothing you configured. Deactivating keeps them too.
Removing
| What you do | What happens to your settings |
|---|---|
| Deactivate | Kept. Reactivating picks up where you left off |
| Delete through WordPress | Removed, because deleting runs the plugin's own uninstall step |
Products, orders and anything else that belongs to your store stay as they are either way — a plugin that deleted your shop's data on the way out would be a plugin nobody could risk trying.
If you are removing Agency Partner for WP, also revoke its key in your Agency space. See Manage your API keys.