? Success

User tests: Successful: Unsuccessful:

avatar mbabker
mbabker
30 Sep 2014

This PR will add an update channel for our update component which will allow for updates to the component to be distributed separate from a CMS release.

Why?

If we were to ever have a repeat of what happened with 3.1.1 through 3.1.4 or in a rare instance where an update to the component was required in order to update the CMS, the update component would potentially fail when trying to update its own files. Adding this update channel allows the update component to be updated with Joomla's integrated extension update mechanisms, which would not use the code in the update component, and provides a fallback in case of such an emergency.

Testing Instructions

A new installation should have new database entries in the #__update_sites and #__update_sites_extensions table for this stream. Upgraded installations should also get the channel but without known ID values (hence the subqueries in the update SQL files). Updates on this channel will not work at this time, an XML file has not been provisioned at the coded location.

avatar mbabker mbabker - open - 30 Sep 2014
avatar jissues-bot jissues-bot - change - 30 Sep 2014
Labels Added: ?
avatar Kubik-Rubik
Kubik-Rubik - comment - 30 Sep 2014

Looks good, thank you!

avatar dbhurley
dbhurley - comment - 30 Sep 2014

:+1: Code review looks good.

avatar nicksavov
nicksavov - comment - 30 Sep 2014

Could you do a test release for it (since no one else will have the update server)? That way we can try updating it on a test site.

avatar mbabker
mbabker - comment - 30 Sep 2014

@nicksavov I've replaced the files that the current Testing update channel is pulling with packages built from staging plus this pull. It'll take a few minutes for the SDN to sync up, should be good to test within 10 minutes.

avatar nicksavov
nicksavov - comment - 30 Sep 2014

Great

No updates available so far in administrator/index.php?option=com_installer&view=update , but I'll try again in another 10.

avatar mbabker
mbabker - comment - 30 Sep 2014

For 3.3.5, you can install in the Extension Manager with http://update.joomla.org/core/packages/Joomla_3.3.5_to_3.3.6-Stable-Patch_Package.zip. For 3.3.0 through 3.3.4 you can install in the Extension Manager with http://update.joomla.org/core/packages/Joomla_3.3.x_to_3.3.6-Stable-Patch_Package.zip.

avatar nicksavov
nicksavov - comment - 30 Sep 2014

Ah, sorry, I've misunderstood you. I meant an update for the Joomla Update component.

I've already gotten the test site up to 3.3.6 and tested that everything worked. I was now wanting to test the update channel for the update component.

Looks like the XML is not at http://update.joomla.org/core/extensions/com_joomlaupdate.xml though.

avatar mbabker
mbabker - comment - 30 Sep 2014

We'll need to devise a packaging script for the component, but yes, we can get something put together for that. I'll also get the XML file provisioned.

avatar mbabker
mbabker - comment - 30 Sep 2014

There's a package for the update component at http://update.joomla.org/core/packages/com_joomlaupdate.zip

Still need to provision XML (will do that momentarily)

Installing the package will throw errors about the language files since those aren't packaged.

avatar mbabker
mbabker - comment - 30 Sep 2014

And the XML is now present, you should be able to update the component within Joomla now. To verify, on the Extension Manager's Manage view, filter for the update component and verify the version number is 3.3.6-dev

avatar MAT978
MAT978 - comment - 30 Sep 2014

@test

able to reproduce then on a fresh install:

1) switch to the Testing update server and update to the 3.3.6 package
2) after the update, go to the extension manager’s update view and check for updates on the update component, install it
3) then version number appears is 3.3.6-dev

thanks a lot!!!

This comment was created with the J!Tracker Application at http://issues.joomla.org/.

avatar MAT978 MAT978 - test_item - 1 Oct 2014 - Tested successfully
avatar marijkestuivenberg
marijkestuivenberg - comment - 1 Oct 2014

Tested

Updated to 3.3.6
In The extension manager update view there is an update for the Joomla! Update component version 3.3.6-dev listed

This comment was created with the J!Tracker Application at http://issues.joomla.org/.

avatar mbabker mbabker - alter_testresult - 1 Oct 2014 - marijkestuivenberg: Tested successfully
avatar marijkestuivenberg marijkestuivenberg - test_item - 1 Oct 2014 - Tested successfully
avatar phproberto
phproberto - comment - 1 Oct 2014

@test :+1:

I updated a test v3.3.0 site to v3.3.6. When I purge updates again I get the 3.3.7-dev listed. I suppose that's normal being on testing.

On updater I searched for components and com_joomlaupdate v3.3.6 was there. I installed it without errors except the language files warning.

avatar mbabker mbabker - alter_testresult - 1 Oct 2014 - phproberto: Tested successfully
avatar mbabker
mbabker - comment - 1 Oct 2014

Merging based on the above tests and reviews. Thanks to all involved!

avatar mbabker mbabker - reference | f5d7b43 - 1 Oct 14
avatar mbabker mbabker - merge - 1 Oct 2014
avatar mbabker mbabker - close - 1 Oct 2014
avatar mbabker mbabker - close - 1 Oct 2014
avatar mbabker mbabker - change - 1 Oct 2014
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2014-10-01 00:12:37
avatar anjahage
anjahage - comment - 1 Oct 2014

@test
Updated to 3.3.6. In Extension Manager update view there is an update for the Joomla update component 3.3.6-dev. After update in the extension manager manage view the update component version number is 3.3.6-dev.

This comment was created with the J!Tracker Application at http://issues.joomla.org/.

avatar anjahage anjahage - test_item - 1 Oct 2014 - Tested successfully
avatar betweenbrain
betweenbrain - comment - 1 Oct 2014

@test

After updating a 3.3.5 site to 3.3.6, I do see an update for Joomla! Update Component and am able to update that extension from 3.0.0 to 3.3.6-dev using the Extension Manager: Update.

:+1:

Thanks all!

avatar mbabker mbabker - head_ref_deleted - 22 May 2015

Add a Comment

Login with GitHub to post a comment