User tests: Successful: Unsuccessful:
Continuing the JInstallerAdapter
implementations and standardizing the adapter paths, this PR focuses in on the update
path.
This PR mainly alters the logic for the component updates; every other adapter modified had already used this standard path. Again, the language adapter is excluded and the library adapter is not modified either because of its approach to updates right now.
Also fixed with this PR is a regression in the uninstall route where the uninstall queries were not being run.
The path now always follows the install route (which was being done for all extensions but components) and the internal code determines which actions to perform based on the active route. Since some of the shared component methods are updated to accommodate for the update route, you'll want to install extensions first. To test updates, you'll want to use a release that isn't the latest one for optimal testing. After confirming everything still installs OK, you'll want to update the extension now, and this should be done using any regular update method. The extensions should update correctly.
Now try to uninstall your test extensions. If they have uninstall queries (many components do), ensure those queries get executed.
Labels |
Added:
?
|
Category | ⇒ | Libraries |
Restarted
Worked for me!
Status | Pending | ⇒ | Ready to Commit |
moving to RTC or do we need need more tests here bevor we can move it to RTC? @mbabker
Milestone |
Added: |
Labels |
Added:
?
|
Thanks. Merging.
Status | Ready to Commit | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-01-16 12:56:54 |
Labels |
Removed:
?
|
Labels |
Added:
?
|
Travis fails here but it looks more on a issue on the travis side:
No output has been received in the last 10 minutes, this potentially indicates a stalled build or something wrong with the build itself.
https://travis-ci.org/joomla/joomla-cms/jobs/46886733
maybe we cen restart the jobs here?