Hi guys, First of all, quick heads up: Joomla 1.5.26 just got released and is a security release. Would be nice to see it appear quite quickly in the Virtualmin upgrades as usual. ;-)
Joomla 2.5.3 security release got released (and appears as upgrade for Joomla 2.5.x installs in VIrtualmin too.
However, it does not appear as possible upgrade for Joomla 1.6 and 1.7 installs, while 2.5 is a minor upgrade to 1.6 and 1.7 releases, that can be applied with a files overwrite + database upgrade queries, and it would be good to have that upgrade possibility in Virtualmin in same way as e.g. 1.6.5 -> 1.6.6 upgrades.
This has become critical, since 2.5.3 fixes a high-level security vulnerability of Joomla 1.6, 1.7 too, and Joomla 1.6 and 1.7 are not supported anymore with security-releases.
Next Major joomla release will be 3.0 this automn, with hopefully in-app upgrade (not yet confirmed), then 3.1-3.5 should be minor ones.
(Finally less critical, Joomla 2.5.x supports in-app upgrades, but Virtualmin (for all Joomla versions) does not auto-detect which version is installed and still displays old version and proposes upgrades).
So is it possible to add 1.6.x->2.5.3 and 1.7.x->2.5.3 script upgrade paths in Virtualmin ?
Many thanks in advance for your consideration.
Comments
Submitted by andreychek on Wed, 03/28/2012 - 08:47 Comment #1
I'll hand this over to Jamie, who I think will have new Joomla versions available fairly soon.
Regarding the upgrade from 1.6/1.7 to 2.5 -- while there does appear to be an upgrade path there, it doesn't appear to be an automated process that the Virtualmin script installer can complete.
However, I'll talk to Jamie about whether there might be a way to solve that.
Submitted by beat on Wed, 03/28/2012 - 11:32 Comment #2
Thanks for the reply!
Hi Jamie, : For Joomla 1.6.x and 1.7.x (and 2.5.x) upgrades to 2.5.3, you may want to look at this page, and more particularly to method C (including the "Update the #__extensions Table" paragraph):
http://docs.joomla.org/Upgrading_from_an_existing_version
You may end the upgrade process with a direct link to the database upgrade page of joomla, like you do with e.g. Piwik and WordPress ?
A note before confirming the upgrade to check that the user has already upgraded his joomla extensions to support Joomla 2.5.3 would be good too. Joomla 2.5 extensions run usually fine on Joomla 1.6 and 1.7. But old 1.6 or 1.7 extensions don't run necessarily on 2.5, thus it's a good idea that the user upgrades his extensions before Joomla itself.
Submitted by JamieCameron on Wed, 03/28/2012 - 13:39 Comment #3
I've just released an installer update for Joomla 1.5.26. Will look into Joomla 1.7.x to 2.5.3 upgrade support..
Submitted by beat on Wed, 03/28/2012 - 16:30 Comment #4
Thank you Jamie !
This is the general releases-cycle for LTS/STS Joomla releases 1.5 - 3.0:
http://developer.joomla.org/development-status.html
When you look into Joomla 1.7 to 2.5.3 upgrade support, please keep in mind that Joomla 1.6.x upgrade to 2.5.3 should also be supported and should be exactly similar to 1.7.x to 2.5.3 upgrade. If a limiting factor restricts this to 1.6.6 to 1.7.0 (and then from 1.7.0 to 1.7.5 which is supported, and then from 1.7.5 to 2.5.3) it is imho also ok.
But i don't see any reason why the upgrade process from 1.6.x to 2.5.3 would be different than from 1.7.x to 2.5.3.
Looking forward to your solution soon, as there are quite a few sites Virtualmin-installed, that got stuck at 1.6.6 or at 1.7.5 that are in danger now that the high-level vulnerability fixed by 2.5.3 has been published, and uninstalling 1.6/1.7 to reinstall 2.5 in virtualmin is not really practical for many sites...
Please let me know if you see any road-blocker or have any joomla-related question, I'll try to help you. :-)
Submitted by JamieCameron on Thu, 03/29/2012 - 00:01 Comment #5
Thanks for pointing this out - I will fix Virtualmin in the next release to allow Joomla 1.6 -> 1.7 -> 2.5 upgrades.
Submitted by beat on Fri, 03/30/2012 - 01:25 Comment #6
Great! Thank you Jamie!
I suppose that customers having 1.6 or 1.7 will automatically get the standard notifications (if enabled) of upgrades available.
(i am not asking when the next Virtualmin release will be, because as you know that this is a high-level vulnerability, i'm sure it will be pretty soon as usual ;-) ).
Submitted by Issues on Fri, 04/13/2012 - 01:34 Comment #7
Automatically closed -- issue fixed for 2 weeks with no activity.