News:

You may pay someone to create your store, or you visit our seminar and become a professional yourself with the silver certification

Main Menu

What version of VM am I running? What steps to update?

Started by t68, February 14, 2019, 10:56:27 AM

Previous topic - Next topic

t68

Think I might have posted this in the wrong thread before so I repost here. Hope that´s ok:

Hi!
Im afraid I´ve slipped a bit with my updates.
Joomla is updated to 3.9.3
And I ran VM updates through the joomla extension auto updates (both main update and AIO). Think it was 3.4 version. I got error messge on the VM update but not the AIO. But now joomla doesn´t flag for any available updates, but in VM it states that VM is running 3.2.12 which seems really old.
Can this be correct? Can I check this in some other wy?

If I need to update, can I run latest VM update manually (the zipfilea through extension update)?
Or do I have to update in steps?
Lots of questions :-), I know. But greatful for any advice!

jenkinhill

You can check extension versions in Joomla/extenstions/manage/manage

You can install updates using the standard Joomla installer - with the new  xxx_package_or_extract.zip you can simply drop the whole package into the upload/installer and it will update VM, aio  (and TCPDF if necessary).
http://dev.virtuemart.net/projects/virtuemart/files

Of course, test all updates on a copy of the site first.
Kelvyn
Lowestoft, Suffolk, UK

Retired from forum life November 2023

Please mention your VirtueMart, Joomla and PHP versions when asking a question in this forum

t68

Thanks Kelvyn!
So no need to do the update in steps since I seem to be running quite an old VM?

jenkinhill

Should update OK. But as I stated before - test before updating the live site.
Kelvyn
Lowestoft, Suffolk, UK

Retired from forum life November 2023

Please mention your VirtueMart, Joomla and PHP versions when asking a question in this forum

t68

Upgradet and everything seems to run ok! The issue was that Joomla was setup for mysql database. Reading the error message a bit closer (the fine print...) this prompted to switch to MySQLi :-).
Change the Joomla config and then the update ran smoothly.