-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Execute sql uninstall query (if exists) on extension install abort #13376
Conversation
I haven't tested this yet, but one question comes to mind: |
that's why i putted the But please test that scenario also |
I have tested this item ✅ successfully on f504164 Note: I also tested installing the extension completely (by removing the exception) and then re-installing the broken one (with the addition of an exception in the This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13376. |
Exactly my fear it would be destructive, i will test too I mean i ll test to "update" an already installed extension with a broken package |
I have tested this item ✅ successfully on f504164 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13376. |
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13376. |
Pull Request for New Issue.
Summary of Changes
Currently when a extension install is aborted and the install sql query already run we get a broken install.
The extension is uninstalled but the database tables will stay in joomla.
This PR proposes to change that by adding a step to rollback the sql (if an uninstall sql exists).
Testing Instructions
#__test
. Notice you get the extension install rollback but you stay with the#__test
table in the database#__test
table#__test
table is also removed.Documentation Changes Required
None.