Latest compatible 2.x version with Joomla 1.5

[PostHistorie.nl]

Long overdue I'm in the middle of migrating an old Joomla 1.5 /Virtuemart 1 site for a client. (Yes, really, dont ask).
I was able to successfully upgrade Virtuemart 1.1.9 -> 2.0.4 with this tutorial:
http://forum.virtuemart.net/index.php?topic=95236.0

It was a bit tricky and took a few turns but I think it works.

But now I'm wondering what's the next step.

My big question is what is the latest Virtuemart 2.x version that will still work with 1.5?

From here I would think 2.0.26F:
http://forum.virtuemart.net/index.php?topic=120324.msg414552#msg414552

But there is no F version:
http://dev.virtuemart.net/projects/virtuemart/files

Because I would think I have to upgrade to the latest compatible 2.x version and THEN upgrade Joomla to 2.5 or 3 (and after that upgrade Virtuemart to version 3) right?

[GJC Web Design]

hmmm .. not the way I do it

Install fresh J2.5.latest/VM2.6.latest

migrate joomla into the new.. then migrate VM1.1.9 into VM2.6 with the native migrator

then VM2.6->VM3

then J2.5->J3

with the daycounts migrator it is possible I think (I don't use it) to go straight from J1.5/VM1.1.9 to J3/VM3

[PostHistorie.nl]

Hi!
What is the "native migrator"?

If this is the database tool thing in VM2: that only works on a running installation. And you say that you start fresh, so there is no VM database to migrate from/to.

And there is no database tool thing in 1.1.9.

[jenkinhill]

Personally I would use the Daycounts Migrator, as you can go from J1.5/VM1.1 to J3.4.6/VM3.0.12 in one step if you wish. IT really does woprk.
http://extensions.virtuemart.net/import-export/virtuemart-migrator-detail

Otherwise the built in migrator is covered in the docs: http://docs.virtuemart.net/tutorials/installation-migration-upgrade/77-upgrading-vm1-to-vm2.html

[PostHistorie.nl]

Well this would be my ultimate last resort (I dont want to pay for this).

I know a fair bit about MySQL and PHP (I wrote my own virtuemart mass product adder) so migrating manually should be doable I think?

My question still remains though 

[GJC Web Design]

Install fresh J2.5.latest/VM2.6.latest

migrate joomla into the new.. then migrate VM1.1.9 into VM2.6 with the native migrator

it is all there natively..

[PostHistorie.nl]

Uh.. I dont really understand then...

Do you mean that when I migrate the old Joomla to the fresh installation that I take the old VM database structure with it (so just the data, not the vm component/aio)?
So that the fresh VM2.6 migrator will recognize this data and then migrate the data/structure to the new VM?

[GJC Web Design]

yes... the old vm tables are named differently.. you import them into your fresh J2.5/Vm2.6  DB and use the vmTools->migrate to import from them into the VM2.6 tables

make sure you have migrated the Joomla 1.5 users into J2.5 first so they match up when you import shoppers and orders

when done delete the old vm1.1 tables

have done dozens.. works..

[PostHistorie.nl]

Ah  I see! Makes sense now, I'll give it a go tonight!
Thanks  so much already for replying.

[PostHistorie.nl]

Well that was fun!
All my 16,577 products and existing customers and orders were migrated successfully to Joomla 2.5.28 / Virtuemart 2.6.22.

Thanks GJC Web Design!

Couple of remarks for future reference:

- Start with a completely fresh/empty installation
- I used J2XML to migrate the users from the old website to the new (you need your users).
- I exported the old jos_virtuemart_* and jos_vm_* tables with phpMyAdmin to a SQL dump file.
- I imported the dumpfile with phpMyAdmin in the new fresh database
- However the tables in the new database had the prefix vfh17_ so migration would fail because it searches for: vfh17_* tables *
- So I edited the SQL dump to find/replace all table names with the right prefix ( :%s/jos_vm_/vfh17_vm_/g)
- Imported that SQL file again in phpMyAdmin to the new installation.
- Migration -> successful!
(- Now starts the long process of getting all my JA Purity template tweaks back in this new version.)

I was wondering what's the best next step to go to Joomla 3 / VM3?

* It was spitting out these kinds of errors:
vmError: port Products db error Table 'wp.nl.vfh17_vm_product' doesn't exist SQL=SELECT *,`p`.product_id as product_id FROM `vfh17_vm_product` AS `p` LEFT JOIN `vfh17_vm_product_mf_xref` ON `vfh17_vm_product_mf_xref`.`product_id` = `p`.`product_id` WHERE (`p`.product_id) IS NOT NULL GROUP BY `p`.product_id ORDER BY `p`.product_parent_id LIMIT 0,1000

[AH]

I was wondering what's the best next step to go to Joomla 3 / VM3?

Definitely go to VM3 - the team have done a lot of work on it and it will get further updates

And IMHO see no reason to stay with joomla 2.5 so upgrade that as well.

[PostHistorie.nl]

Eh yes that is the plan! 

My question was how to best go from J2.5/VM2 -> J3/VM3?

[AH]

Ah - sorry

If I remember rightly, I just updated my VM to VM3 from VM2, same with Joomla 2.5

Then dealt with the template changes.

[GJC Web Design]

yes.. vm first (easy.. never had a problem)

then J2.5 to J3..  can easily turn into a disaster esp. with earlier migrated 1.6/1.7..

but if u started with a clean 2.5.28 should be easy..  use the std. joomla installers.. live updaters are less solid..

[Milbo]

hmmm .. not the way I do it

Install fresh J2.5.latest/VM2.6.latest

migrate joomla into the new.. then migrate VM1.1.9 into VM2.6 with the native migrator

then VM2.6->VM3

then J2.5->J3

Actually it should work to use directly last version vm3. but I must admit:

with the daycounts migrator it is possible I think (I don't use it) to go straight from J1.5/VM1.1.9 to J3/VM3

We use it ourself and it works really very well. You can even migrate a j1.0 to j3. It is imho the best migrator for VirtueMart AND joomla!

http://extensions.virtuemart.net/import-export/virtuemart-migrator-detail

We just had it today, that we had a "finished" migration. But we used as base an old migration of another company. Users very half way migrated, no problem with the migrator of daycounts.

It even constructs better j3 menues from j1 and j2 installs then normal joomla updaters.