Tools & Migration
The purpose of this section is to allow developers to never have to manually delete and reinstall VirtueMart. These tools are for developers ONLY for use in new stores, not live stores. THEY CAN DESTROY AN ENTIRE WEBSITE.
Migration Tab Allows developers to migrate your data from VirtueMart 1.1 to VirtueMart 2.
FOR DEVELOPERS ONLY. The Synchronize Media section is a copy of the SHOP - Media Files tool. See that section for instructions. More about the tools here
The tools in virtuemart 2 are meant for developers, testers, and in common professionals. Some people meant we should remove them, because they must use with care and they can just destroy your whole store. They should be never used in an already running store, except the "Install tables or if necessary update them". But on the other hand, they help webdevelopers and spare a lot work. So to protect users from themselves we added an extra security for this commands. They must be enabled in the shop configuration first.
When you use this tools right, you almost never have to reinstall virtuemart, even when you are tester and getting the newest svn daily.
Tools for installation
Renew config by file
Deletes the stored configuration in the database and reset it with the values from the file /administrator/components/com_virtuemart/virtuemart.cfg. Be aware that it does not take the values from the
virtuemart_defaults.cfg-dist. This file contains the default configuration shipped with the core. So you can adjust the virtuemart.cfg to your needs and use it as a kind of backup.
Restore System Defaults
This deletes and restores the standard tables of vm, this means tables wich are most time not user generated, for exampel, admin menu, countries, currencies, orderstatus, states,... . This command maybe removed.
Remove VirtueMart Data
This removes the user generated data, categories, products, manufacturers, calculation rules, ... This may help you, when you heavily customised your store with own currencies, countries, states and so on, but you want to remove the actually displayed data.
Remove VirtueMart Tables
This just removes all _virtuemart_ tables. It is meant, when you want to completly uninstall VM, it is not senseful to use it for a reinstall
Reset all tables and do a fresh install
One of the most interesting commands. It deletes all _virtuemart_ tables and executes the install function of the installer. So you have a completly renewed virtuemart. This is very interesting for developers, testers, and administrators for test purposes.
Reset all tables and install sample data
Does the same as above, but installs directly the sampeldata.
Install tables or if necessary update them
This is very important for people who use the svn. This executes the updater function of the installer and updates your tables to the newest layout.
Optimise database (since VirtueMart 3)
Using that tool will not do any harm to your database. It helps to cure a flaw in MySQL. Normally MySQL keeps table index automatically up-to-date to speed up database operations. VirtueMart is using - at least in most cases - a table model called MyISAM to guarantee a speedy performance. Sometimes the MySQL feature to automatically update the table indices does not work as it should do in case of MyISAM tables. The button 'Optimise Tables' will force the database to create proper indices. Especially in larger shops it can help to speed up the shop.
Tools for migration
Server settings of max execution time
When your server support max_execution overrides, then you can set here for the migration process an higher limit.
Memory limit of the server
When your server support memory_limit overrides, then you can set here for the migration process an higher limit.
The radiobox gives you the possibility to execute different tasks of the migration. You should use the given order.
This is importing the general data, medias, categories, manufacturers, etc
This is importing the user addresses
Imports the products
Imports the orders
Import everything in the right order
Set store owner
Here you can set your storeowner, when you provide an id, then to the userId, in the other case for the user who is executing the command.
Default category layout (browse page)
Enter here the default flypage, to prevent to be ported. This is quite important, because in the other case every category uses the overrides, which is bad to administrate.
Default category product layout (fly page)
Same as for the flypage, just for your browsepage
Write here the new storeowner id
Set here the new storeowner id, when you execute "Set store owner"