Record the current state
Write down the installed plugin version, WordPress version, PHP version and connected addons. Create a complete file and database backup before changing anything.
Test the update on staging
Install the new ZIP on a staging copy, clear caches and test the workflows the plugin controls. Check the front end, WordPress admin, forms, scheduled jobs and integrations rather than relying only on a successful activation message.
Update production with a rollback path
Use the WordPress upload-and-replace flow when supported, or follow the product-specific note. Keep the previous ZIP and backup available until production checks are complete.
PluginNest is independent and not affiliated with original product developers. GPL downloads do not include official vendor license keys, SaaS accounts or official vendor support.
FAQ
Will a manual plugin update delete my settings?
Normally settings are stored in the database and remain in place, but plugins can run database migrations. A tested backup is still essential.
Should I deactivate the plugin first?
It depends on the product. Follow its important note when one is provided and use staging if the plugin controls checkout, security, membership or other critical workflows.
What if the new version breaks the site?
Restore the previous plugin version or site backup, document the error and report the exact versions and message to support.