Update HelSup, roll back or uninstall
Back up your installation, replace the plugin package and verify the updated workspace.
On this page
Before updating
Back up the WordPress database, plugin files, and uploads. Read the release notes and test the new version on staging with representative tickets, forms, email, portal, chat, and background jobs.
Apply an update
- If WordPress or the plugin offers an authorized update, review its version and compatibility before installing it. Update availability depends on the configured provider and entitlement.
- Otherwise upload the new installable HelSup ZIP through WordPress Plugins → Add New → Upload Plugin and follow the replacement prompt.
- Keep the installed folder name elegantsupport and replace the complete package; do not mix old and new assets.
- Open WordPress admin so pending schema migrations can run.
- Reload the workspace and review System Status.
- Submit a test ticket, reply through an enabled channel, and verify cron and queue progress.
If an update fails
Record the error and installed version, check PHP logs and System Status, and confirm the upload is complete. An interrupted migration can be retried by loading WordPress admin. Avoid editing schema-version options manually. A code-only rollback can conflict with migrated data; restore database and files from the same backup point when necessary.
Deactivate versus uninstall
Deactivation disables plugin runtime. It does not run uninstall.php. By default, deleting the plugin retains its business tables and options. Enable Remove data on uninstall under Settings → System → System only when you intend to wipe the plugin data, and take a backup first.
Exact scope of the uninstall wipe
When enabled, uninstall drops tables named with your WordPress prefix followed by helsup_support_, removes es_ options and plugin transients, and removes es_preferences user metadata. The current routine does not erase uploaded files or legacy es_ tables. Review those separately if your data-removal process requires it.