We recently received a report on WordPress.org from a user who experienced a critical error when trying to delete DesignSetGo through the Plugins dashboard. We take reports like this seriously, and we’ve shipped a fix in version 2.0.45.
What happened
Two issues were identified:
- Uninstall error on some hosting environments: The plugin’s cleanup routine (
uninstall.php) called a cache function that isn’t available on all WordPress hosts. When that function wasn’t present, it caused a fatal error — which prevented WordPress from completing the deletion. - Deactivation scanning was automatic: When deactivating the plugin, a content scan started immediately without user consent. This was designed to help convert DesignSetGo blocks to core WordPress blocks, but the automatic behavior understandably raised concerns.
What we fixed
Uninstall is now fault-tolerant
The cleanup routine now wraps each step in error handling so that one failure doesn’t prevent the rest of the cleanup — or the deletion itself — from completing. We also added compatibility checks for cache functions that may not exist on every host.
Deactivation scan is now opt-in
The deactivation modal no longer automatically scans your site. Instead, you’ll see a clear choice:
- Scan & Convert Blocks — Voluntarily scan your content and convert DesignSetGo blocks to standard WordPress blocks before deactivating.
- Just Deactivate — Skip the scan entirely and deactivate immediately.
- Cancel — Close the modal and keep the plugin active.
No scanning happens unless you explicitly choose it.
How to update
If you’re currently unable to delete the plugin through the dashboard, here’s what to do:
- Go to Plugins → Installed Plugins in your WordPress admin.
- If DesignSetGo shows an available update to 2.0.45, update it first.
- After updating, you can deactivate and delete normally.
If you already had to delete via FTP, no further action is needed — the plugin files are already removed.
Our commitment
A plugin should always uninstall cleanly. We’ve added automated CI tests that verify the full activate → deactivate → delete lifecycle on every release to make sure this doesn’t happen again.
If you run into any issues, please reach out on our WordPress.org support forum or open a GitHub issue. We appreciate the feedback — it makes the plugin better for everyone.