Submitted by glimmung on Thu, 11/21/2013 - 06:28 Pro Licensee
Hi,
The version of Magento offered by the installer under 4.03 Pro is 1.8.0.0 - however, I have a client who is having issues with this version and wants to use an earlier one, which raises two questions: -
Is it possible to configure Virtualmin so that, as for some other apps, it offers a choice of versions of Magento, specifically 1.7.0.2 & 1.8.0.0. Failing that, is it possible to modify the installer so that only 1.7.0.2 is offered?
Alternatively, is there a way to expose the "Install Unsupported Version" tab to specific server admins?
--
Cheers,
PhilK
Status:
Active
Comments
Submitted by andreychek on Thu, 11/21/2013 - 08:36 Comment #1
Howdy -- there are indeed some cases where multiple versions of an installer are offered.
That occurs when that particular application has multiple supported branches.
For example, with an app such as Joomla, there is an LTS release, along with multiple non-LTS releases.
With Magento in this case -- it appears that 1.8.0.0 is the only supported Magento branch, and that 1.8.0.0 solves security issues in previous Magento versions.
Because of the unsupported nature of the old version, and that it appears to contain security issues, we wouldn't recommend installing that on your server.
If you'd like to do that anyway though, let us know and I can talk to Jamie about the best way to do that.
Submitted by glimmung on Thu, 11/21/2013 - 09:17 Pro Licensee Comment #2
Hi,
OK, understand the logic re. multiple supported branches, and on the reason for only one being offered for Magento.
From a general PoV, I do think that others will have this issue with Magento - both because it is new enough that many add-ons have not been updated to be compatible with 1.8.x, and because (based on my client's experience) there are still some teething problems with the new version (specifically related to OOTB checkout configuration). However, I can see why you would be wary of addressing this based on that alone.
From the client PoV, they are definitely stuck on 1.7.0.2 for now, as the store was under development before 1.8.x was released, and both because of the checkout issue and because of add-on availability, they are unable to upgrade at this point.
In a perfect world, I would find and clone the script that installs 1.8.x, make a copy for 1.7.0.2, and make it available to this client only - some pointers as to how to do that would sort me out. Giving the client access to the "install unsupported version" functionality would also help, but is less desirable.
Hope that makes sense!
--
Cheers,
PhilK
Submitted by JamieCameron on Thu, 11/21/2013 - 15:36 Comment #3
You may be able to install an older version from within Virtualmin, as follows :
I can't guarantee this will work though - it may fail if the install process has changed between 1.8 and 1.7.