Upgrading VM1 to VM2 with provided packages » History » Version 5
Max Milbers, 09/18/2011 11:20 AM
| 1 | 1 | Max Milbers | h1. Upgrading VM1 to VM2 with provided packages |
|---|---|---|---|
| 2 | |||
| 3 | 5 | Max Milbers | The order of steps in short: |
| 4 | 1. First uninstall all old vm extensions. |
||
| 5 | 2. Just install vm2 as upgrade over vm1 (just use the joomla install view) |
||
| 6 | 4. Make your life easy and use the sampeldata. |
||
| 7 | 3. Copy your vm1 images into the desired folders (you can also adjust the paths in the config to your old vm folders) |
||
| 8 | 4. Go to Migration and Tools in the backend. |
||
| 9 | 5. Use on the second tab the option all and fire the button. |
||
| 10 | 1 | Max Milbers | |
| 11 | 5 | Max Milbers | Very important! Depending on your shops size and your server, the migration process may stop. Then just repeat the migration. The migrator is resuming. This means the migrator stores the already ported data and does not import it twice. In theory you can press the buttons as often as you want. |
| 12 | 1 | Max Milbers | |
| 13 | |||
| 14 | 5 | Max Milbers | Be sure that you *disabled/uninstalled ALL Vm1.1* related plugins and modules. |
| 15 | 1 | Max Milbers | |
| 16 | 5 | Max Milbers | Just *install VM2 over VM1*. Dont uninstall VM1, or you would lose your data. The VM2 installer package is also suitable for upgrading. You need not to fear that your database data gets lost. Of course you should have a backup for emergency problems (you may use akeeba backup). |
| 17 | |||
| 18 | The migrator *does not look on plugins, components or modules.* So when you have vm1 extensions, you need to check first if an update for this extension is available. |
||
| 19 | |||
| 20 | The best order is already used, when you use the optoin "all". It is just using all options from left to right. The sequel is media, shoppergroups, users, categories, manufacturerCategories, manufacturers, products, orders. |
||
| 21 | |||
| 22 | 3 | Valérie Isaksen | When you get an error while the migration process, nothing is lost. The tools provide buttons for this. Use the "Remove Virtuemart Tables" to delete all user generated data, after that use one of the migrationtools. The migrator should be able to handle data which is already there. Because the migrator does not just copy the db data. The migrator gets the information of the old _vm_ tables and adds them to vm2 using the VM2 models. This means for exampel, when your old products used the ids from 100-500, they will have the ids 1-401 in VM2. |
| 23 | 1 | Max Milbers | |
| 24 | The button "Reset all tables and install sampledata" deletes ALL _virtuemart_ tables and reinstalls all tables and inserts the sample data. This is like a completly new install regarding the SQL. The button "Restore System Defaults" is kind of the opposite of "Remove Virtuemart Tables". It reinstalles all VM2 information, which is normally not user generated, this are states, countries, currency, orderstatus, adminmenu,... |
||
| 25 | 2 | Max Milbers | |
| 26 | When you have trouble and getting strange errors, please check if your toolbar.virtuemart.php is deleted. |