Hi,
I've noticed what appears to be a bug when deleting WordPress applications in Enhance and I've reproduced this behaviour several times:
- A WordPress installation exists and is managed through Applications in Enhance.
- The WordPress application has its associated database.
- I delete the WordPress installation from Applications.
- The application is successfully removed.
- However, the associated database remains in Enhance and is not deleted.
This has happened repeatedly with different WordPress installations, so it doesn't appear to be an isolated case.
The problem is that, over time, this leaves orphaned databases behind for WordPress installations that no longer exist.
Expected behaviour
When deleting a WordPress application, I would expect Enhance to also delete the database associated with that application.
Alternatively, if retaining the database is intentional as a safety measure, the deletion dialog could offer an option such as:
☑ Delete the associated database
Actual behaviour
The WordPress application is deleted, but its database remains and has to be identified and removed manually afterwards.
Interestingly, this also seems different from the behaviour previously discussed in the community, where deleting an application was reported to delete the database as well:
Detach Application: https://community.enhance.com/d/2236-detach-application
Can anyone confirm if they are seeing the same behaviour?
Is this a known issue or a recent change in how application deletion works?
