News:

Looking for documentation? Take a look on our wiki

Main Menu

Upgrade from VM 2.0.20b in one or two stages?

Started by austega, April 29, 2015, 02:13:08 AM

Previous topic - Next topic

austega

My client is ready to upgrade from VM2.0.20b operating on J2.5.28/php 5.3.29 (on a test site j3.sag.org.au) using RocketTheme Afterburner template with no VM template overrides. This is a precursor to upgrading to J3.4.1 with a new template.

I have read the forum/tutorial on VM upgrades and see the process is basically:
1. Check for 3rd party VM plugins/extensions
2. Install the VM and AIO over the top of the existing installation
3. Sort out any issues with the 3rd party items/layout overrides etc

Is there any reason to upgrade to VM2.6.18 as an intermediate step? If so should this be a normal over-install or some copying of data tables like recommended in https://forum.virtuemart.net/index.php?topic=128709.0? Are there any other tips or factors I should take into account?

Thanks - David

GJC Web Design

it may not be totally necessary but I would go to 2.6.18 first
then 3.0.8

with both core and AIO - both are just normal Joomla installs
GJC Web Design
VirtueMart and Joomla Developers - php developers https://www.gjcwebdesign.com
VM4 AusPost Shipping Plugin - e-go Shipping Plugin - VM4 Postcode Shipping Plugin - Radius Shipping Plugin - VM4 NZ Post Shipping Plugin - AusPost Estimator
Samport Payment Plugin - EcomMerchant Payment Plugin - ccBill payment Plugin
VM2 Product Lock Extension - VM2 Preconfig Adresses Extension - TaxCloud USA Taxes Plugin - Virtuemart  Product Review Component
https://extensions.joomla.org/profile/profile/details/67210
Contact for any VirtueMart or Joomla development & customisation

austega


austega

Here is my report back - any comments on the installation screen warnings/notifications would be very welcome.

1. After backup I installed VM 2.6.18 component and did not see an installation success screen but rather was taken to the site control panel (with no apparent error messages)
2. Installed VM 2.6.18 AIO and saw an Installation Successful message but also saw a range of warnings/notifications - see attached
3. VM front end and back end seemed to be working fine with some minor layout tweaking issues
4. After backup installed VM 3.0.8 component and saw an Installation Successful message with a range of warnings/notifications - see attached 2 images
5. Installed VM 3.0.8 AIO and saw an Installation Successful message with a range of warnings/notifications - see attached
6. VM front end and back end seemed to be working fine with a larger range of layout tweaking issues though some shipment methods were absent or no longer showed their costs
7. Installed VM 3.0.8 TCPDF - installation successful - no warnings

Overall I think this was successful and have asked the client to test, though I would appreciate someone with experience casting an eye over the images attached to see if any of the notifications should be causing me concern.

I am rusty with VM and expect the layout tweaking to involve some research and trial and error - and would like to do this on a stable platform.

Thanks for your help - David

GJC Web Design

GJC Web Design
VirtueMart and Joomla Developers - php developers https://www.gjcwebdesign.com
VM4 AusPost Shipping Plugin - e-go Shipping Plugin - VM4 Postcode Shipping Plugin - Radius Shipping Plugin - VM4 NZ Post Shipping Plugin - AusPost Estimator
Samport Payment Plugin - EcomMerchant Payment Plugin - ccBill payment Plugin
VM2 Product Lock Extension - VM2 Preconfig Adresses Extension - TaxCloud USA Taxes Plugin - Virtuemart  Product Review Component
https://extensions.joomla.org/profile/profile/details/67210
Contact for any VirtueMart or Joomla development & customisation

onlyrealone

Yes it possible. I had done this


Sent from my iPhone using Tapatalk

austega

Thank you.

In case it is useful to others or if there is a better solution, I did face and solve one ancillary transition issue. My client shop manager is a member of the Joomla Administrator group - and lost her access to the VM backend during the upgrade. I resolved this by giving her user group configuration access to the VM component via the ACL Mgr installed on the site. I note that this had not been required on the live site which is still running VM 2.0.20b.

David