How to Update GPL Plugins and Themes Without Breaking Your Site
WordPress GPL · November 9, 2026

Updates are how plugins and themes receive security fixes and stay compatible with new versions of WordPress and PHP. For anything from the WordPress directory, you click Update. GPL copies of premium plugins and themes work differently, and this guide explains how updates reach you at WordPress GPL and gives you a routine for applying them without surprises.
Why GPL copies don't update from the dashboard
Plugins and themes from the directory get their updates from WordPress.org. Premium ones rely on an update checker built in by the developer, which asks the developer's server, and that server expects a valid licence key for your site.
A GPL copy doesn't include that key, so one of two things happens: no update notice appears at all, or WordPress reports that a new version exists with the note “Automatic update is unavailable for this plugin.” The auto-updates option on the Plugins screen can't help either, because there is nothing it is allowed to download. Updating is a manual step: get the newer ZIP and install it over the old copy.
How updates reach you at WordPress GPL
- Newer releases replace the old file. When a newer version of a product reaches our catalogue, it becomes the file you download from your account, straight away.
- Single purchases include newer versions for twelve months from the date of purchase. With the optional lifetime upgrade there is no twelve-month cut-off for that item, with up to 200 downloads in total.
- Memberships include newer versions of every plugin, theme and Elementor kit while the plan is active: open the product page and click Download now. When a plan ends, the files you downloaded stay yours to use, but new versions need an active plan again. Each plan is a single payment with no auto-renewal; compare them on the membership page.
- Need a release sooner? Sign in, open the product page and click Request a newer version. It costs nothing, and you'll be notified when the update is in.
One honest caveat: there can be a gap between a developer publishing a release and that release reaching our catalogue, and our terms say plainly that we don't promise the latest version at every moment. For a plugin a business depends on, a licence from the developer gives you their update service directly.
Know what each site runs
You can't update what you haven't noticed. For each site, keep a short list of its plugins and themes, the installed versions (shown on the Plugins and Themes screens) and where each one came from. Then:
- follow the developers' changelogs for the products you depend on;
- keep an eye on public vulnerability reports for WordPress plugins and themes, so security fixes get priority;
- check your account after a release you care about, and use the request button if it hasn't arrived.
If you work from the command line, wp plugin list and wp theme list print every item with its version.
A safe update routine
- Back up first. A full backup covers files and database, is stored somewhere other than the server, and has been test-restored at least once. Your host's snapshots or a backup plugin such as UpdraftPlus Premium will do the job.
- Use a staging copy. Many hosts offer one-click staging; a plugin such as WP Staging Pro or a local copy of the site works too.
- Read the changelog. Look for new minimum PHP or WordPress versions, removed features, add-ons that must be updated at the same time, and database changes.
- Update on staging. Download the newer ZIP and upload it through Plugins → Add New Plugin → Upload Plugin, or Appearance → Themes → Add New Theme → Upload Theme. WordPress spots the existing copy and shows the installed and uploaded versions side by side. Check that the uploaded one is newer, then confirm the replacement. Our guide to installing a plugin from a ZIP covers the upload errors you might meet.
- Run any database update the plugin asks for once the new version is in place.
- Test what matters: the homepage, key landing pages, forms, checkout and logins, on a phone and as a logged-out visitor. Check the PHP error log for new warnings.
- Repeat on the live site at a quiet time, one item at a time, then clear your caching plugin, server cache and CDN.
- Keep the previous ZIP and the backup until you are confident the update is good.
Themes, child themes and bundled plugins
Updating a theme replaces all of its files, so edits made directly inside the parent theme are lost. A child theme prevents that; see our guide to installing a theme and setting up a child theme. Themes that bundle companion plugins often ship newer copies of those plugins with each release, so after updating the theme, check its plugin notice for updates to them too.
Elementor kits don't update in place
Imported templates are copies stored in your site's database. A newer version of a kit doesn't touch pages you have already built; if you want a refreshed design, import that template again and apply it where you need it. Our guide to importing an Elementor template kit covers the steps.
If an update goes wrong
- Site down after an update? When a plugin or theme causes a fatal error, WordPress emails the site administrator a recovery-mode link. Use it to deactivate the culprit, or rename the plugin's folder in
wp-content/pluginsover SFTP. - Roll back the files by uploading the previous ZIP the same way. WordPress warns that you are installing an older version; take that warning seriously, because database changes made by the newer version aren't undone by swapping files.
- Restore the backup if the update changed the database or several things broke at once. That is exactly what it is for.
Whatever happens, don't reach for a nulled copy that promises automatic updates. Our guide to GPL vs nulled plugins explains why that trade is never worth it.
Updating many sites
If you look after client sites, batch the work: download each newer ZIP once, keep a folder of current versions, and use WP-CLI where you have SSH access. This command replaces the installed copy with the version in the ZIP:
wp plugin install ./plugin-name.zip --force
Test on one site before rolling out to the rest. A membership covers newer versions of every plugin, theme and kit in the catalogue while it is active, which suits anyone maintaining several sites.
Product names belong to their owners. WordPress GPL is an independent store and is not affiliated with or endorsed by the developers mentioned here.
FAQ
Why don't I see update notices for my GPL plugins?
Dashboard notices for premium plugins come from the developer's update server, which needs their licence key. Without it you see either no notice or one saying automatic update is unavailable.
How do I know a newer version is available at WordPress GPL?
Newer releases replace the file in your account as they reach the catalogue. Waiting for a particular release? The Request a newer version button flags it for us, and you're notified once the update is in.
Will uploading a newer version delete my settings?
No. Settings are stored in the database, and replacing a plugin's files leaves them alone. Deleting the plugin is different: some plugins remove their data when deleted.
Can I go back to an older version?
Yes. Upload the older ZIP and confirm the replacement. If the newer version changed the database, restore your backup instead.
What happens to updates when my membership ends?
You can keep using everything you've downloaded, on as many sites as you like. To download newer versions you start another plan, since nothing renews automatically. The FAQ has the details.
Comments
Be the first to comment.
Leave a comment
Comments are moderated before they appear.