Scripts Update Error: "Newer than latest"

After the recent Virtualmin update I'm now getting this on mass Joomla (1.6 & 1.7) and Magento script updating:

"Failed to upgrade scripts : None of the selected servers have scripts installed that can be upgraded to the selected version"

When I look at the accounts themselves, it erroneously shows: "Newer than latest"

Brian

Status: 
Closed (fixed)

Comments

What version does Virtualmin show is installed currently for Joomla in those domains?

Jamie,

Joomla is actually my fault. I have several Joomla 1.6 sites that I updated from within the respective Joomla control panels to 1.7 (nice new Joomla upgrade feature). 1.7 is really more of a bug fix and a bit misleading that they choose to label it 1.7 oppose to 1.6.7. I'm not sure it was necessary for you to separate 1.7 from the 1.6 upgrades.

However that still leave Magento having the reported error. I have 12 Magento sites that are either 1.5.0.1 or 1.5.1.0 and all of them are being reported as "Newer than latest", which is 1.6.0.0.

Brian

Did you perhaps perform a manual upgrade of your Magento sites to 1.6.0.0 ?

No, not the case with the Magento installs.

While we're on the topic of script installs, All NMS::FormMail 3.14c1 installs now say "Manually deleted".

I just tested a brand new install and even it shows:

NMS::FormMail 3.14c1 /cgi-bin/FormMail.pl None Manually deleted

Ok, I see the issue .. the message is wrong when it says "Newer than latest". What it should really say is that you cannot upgrade from the current 1.5.x version to 1.6, as this is not supported by Magento. I will fix that message in the 3.89 Virtualmin release, and the FormMail error you reported.

Ok, I see the issue .. the message is wrong when it says "Newer than latest". What it should really say is that you cannot upgrade from the current 1.5.x version to 1.6, as this is not supported by Magento. I will fix that message in the 3.89 Virtualmin release, and the FormMail error you reported.

Very good - Thanks Jamie.

Brian

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