Hi Edwin,

Virtuemart 1.1.4 just released. There is a mysql script. Is it safe to upgrade to virtuemart 1.1.4 for all the slave site?

Thanks

Can you be more precised where we can review the VM mysql script.
We have not found it.

If they change the DB layout with a mysql script you probably have to apply it on all the websites as you share the same files and folders on the disk.

When we have a look in their zip concerning the update 1.1.3 to 1.1.4, we have not found the mysql script that you have mentionned.

Anyway, with VM, you must always take care for the update.
I advise you to have a backup before executing any VM update.
I also suggest that you repeat the operation on a copy of your website before doing it in production.
Personnally each time we had to update VM, we have encountered problem with their scripts. So a backup and test the operation offline is strongly recommended.
This is not JMS related. The same problem can occurs on a standalone joomla.

During our review on VM 1.1.4, we have identified a change in VirtueMart 1.1.4 that require a new patch definition in JMS.
The patch will be delivered in new JMS patches definition 1.2.14.

Until this delivery, it is adviced to not install VM 1.1.4 because you will not be able to install the JMS patches and that will create errors that can not be fixed with current JMS patches 1.2.13.

Hello Edwin;

I have virtuemart 1.1.4 and your most recent patches v.1.2.18.

Virtuemart works great on master...but in the Slave_1 site it malfunctions in a weird way. First the images dont show up...so it means that the path is not created properly for some reason. And the second error is very strange. The administrator template for virtuemart is not being used and the display is messed up.

All remains perfect on the master site but any slave site that is created, virtuemart 1.1.4 does not work. All other components are great and everything else seems perfect except this new version of virtuemart.

Some help would be great

What does not work in the VM slave site.
Have you update their VM administration parameter to check the URL and SECUREURL they are using.
Save the VM slave administration configuration to create the specific slave site configuration with your new parameters.