Install Scripts offers to upgrade Joomla 1.0x to 1.5.x

Submitted by kenlyle on Thu, 11/05/2009 - 19:19

I have built over 100 Joomla sites since 2004, and I have never seen an upgrade script to "upgrade" Joomla 1.0 to 1.5. What I have seen is a component you can install in a 1.5 instance that will connect to the old database and port the content.

Anyway, there may need to be something in the Installer, a rule like "Prohibited Upgrade".

Or maybe you have written a custom thing, or found something with which I am not familiar....anyway, I skipped the upgrade, because it seemed odd.

Status: 
Closed (fixed)

Comments

Joe's picture
Submitted by Joe on Thu, 11/05/2009 - 19:31 Pro Licensee

Wait, are you saying that Install Scripts in the current version of Virtualmin is offering to upgrade Joomla from 1.0 to 1.5? That bug should have been fixed several revisions ago (and as far as I know, only existed for a short time).

Joe's picture
Submitted by Joe on Thu, 11/05/2009 - 19:31 Pro Licensee

Current version is 3.74, by the way.

Submitted by JamieCameron on Thu, 11/05/2009 - 20:01

If you try to do an upgrade from 1.0 to 1.5 in Virtualmin, it will actually be rejected. However, it sounds like I should fix the UI so that the offer to upgrade is never even made available ..

Submitted by beat on Fri, 11/06/2009 - 12:07

Also in mass-upgrades it still proposes upgrading joomla 1.0 to 1.5.

Submitted by JamieCameron on Fri, 11/06/2009 - 17:22

The next Virtualmin release will not even offer to do this upgrade anywhere ..

Submitted by kenlyle on Fri, 11/06/2009 - 19:22

GREAT!!!

I did a mass upgrade to 1.5.15, and DID see " Joomla cannot be upgraded from versions before 1.5 to version 1.5 or later

.. failed! See the error message above for the reason why."

And, I am only on 3.73 :( , so some of this logic, at least, is in there.

Hi Beat!

Submitted by Issues on Sat, 11/21/2009 - 11:19

Automatically closed -- issue fixed for 2 weeks with no activity.

Submitted by kenlyle on Sun, 11/22/2009 - 07:39

I don't like auto-close. Beat and I have put a bit of energy into reporting an observed anomaly. Is this fully resolved?

Submitted by beat on Sun, 11/22/2009 - 07:52

kenlyle,

Jamie wrote already above:

The next Virtualmin release will not even offer to do this upgrade anywhere ..

So he confirmed the fixes.

I just reported the small issue of mass-upgrades, and added it to this ticket as it was relevant to that ticket, instead of opening a new one. Jamie's reply was after that, and covers that too.

I didn't put energy in this little issue, just reported by the way another place while I saw it. Please don't write in my name without my consent, thanks. ;-)

Submitted by JamieCameron on Sun, 11/22/2009 - 13:04

The transition from "fixed" to "closed" happens automatically after 2 weeks of inactivity in the "fixed" state.

I set this to "fixed" when I implemented the code that will prevent the upgrade for inclusion in Virtualmin 3.75, which is now out. If this isn't working for you, please re-open this bug..

Joe's picture
Submitted by Joe on Sun, 11/22/2009 - 14:28 Pro Licensee

Just to be clear: Tickets are never automatically closed unless they have been fixed. Our development process is entirely transparent, and we always appreciate and respond to bug reports.

There are two state that indicate a problem has been dealt with. Fixed indicates someone has resolved it, either via code or via explanation. Closed indicates that everybody (including the submitter of the ticket) is happy with the resolution. If the submitter doesn't mark the ticket closed, or reopen, the ticket within two weeks it is assumed that everyone agrees and the system auto-closes it. Most submitters do not close their own tickets, so as a convenience, we close them automatically.