I am trying to migrate a Joomla 1.5.26 site to Joomla 3.3.6. But I am facing troubles with virtuemart migration, using SP Upgrade.
This extension did the job related to core Joomla and other extensions, except Virtuemart.
The reason is that we have to instal a especific version of Virtuemar in both sites (source 1.5.26 and destination 3.3.6): Virtuemart 2.0.22a
http://cyend.com/extensions/extensions/components/documentation/24-user-guide-how-to-migrate-to-joomla-16?showall=&start=8
In the joomla 1.5.26 ok I got. But it is not possible (I think) to install Virtuemart 2.0.22a in Joomla 3.3.6.
So I am asking for help here. is there a way I can install virtuemart 2.0.22a in joomla 3?
Anyone knows how to migrate virtuemart using sp upgrade, as I think it is very difficult to do this job "mannually"...
Tks a lot for your help, in advance.
Regards from Rio, Brazil.
Lenildo
have no idea if this is the correct way.. but - this is what I do
1. is there a way I can install virtuemart 2.0.22a in joomla 3? - definitely not
once j3 is up and running I instal VM3
then copying the the vm1.1 images to the correct folder (images/stories/virtuemart/.... )
then copy all the vm1.1 tables into the J3 database (change the prefixes if necessary)
then use the native VM3 migration (this is the std. VM migration technique - have never got SPUpgrade to work with VM1.1-> to higher)
Has always worked for me except the last one I did didn't fill the category_media table and I had to manually attach the images to the cats in the admin
It worked for me too. Great solution! Thanks a lot for your step by step guide on this migration problem.
Only saying that I transfered the virtuemart tables (VM2 and VM1 - both were in J1.5 site database as result of anterior migration) before the VM3 instalation on Joomla 3 and the migration occured during the VM3 instalation.
Best Regards,
Lenildo
Excellent .. just to further explain ->
Quotehave never got SPUpgrade to work with VM1.1
as I understand it SPUpgrade for extensions does a 1 to 1 DB tables transfer - as VM1.1 table structure is completely different to VM2/3 this will never work