Tools » History » Version 4
Max Milbers, 10/23/2011 10:23 PM
1 | 1 | Max Milbers | h1. Tools |
---|---|---|---|
2 | |||
3 | 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. 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. |
||
4 | When you use this tools right, you almost never have to reinstall virtuemart, even when you are tester and getting the newest svn daily. |
||
5 | |||
6 | 4 | Max Milbers | h2. Tools for installation |
7 | |||
8 | 3 | Max Milbers | h3. Renew config by file |
9 | |||
10 | 1 | Max Milbers | 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 |
11 | 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. |
||
12 | |||
13 | 3 | Max Milbers | h3. Restore System Defaults |
14 | |||
15 | 1 | Max Milbers | 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. |
16 | |||
17 | h3. Remove VirtueMart Data |
||
18 | 3 | Max Milbers | |
19 | 1 | Max Milbers | 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. |
20 | |||
21 | h3. Remove VirtueMart Tables |
||
22 | 3 | Max Milbers | |
23 | 1 | Max Milbers | 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 |
24 | |||
25 | h3. Reset all tables and do a fresh install |
||
26 | 3 | Max Milbers | |
27 | 1 | Max Milbers | 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. |
28 | |||
29 | h3. Reset all tables and install sample data |
||
30 | 3 | Max Milbers | |
31 | 1 | Max Milbers | Does the same as above, but installs directly the sampeldata. |
32 | |||
33 | 3 | Max Milbers | h3. Install tables or if necessary update them |
34 | |||
35 | 1 | Max Milbers | 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. |
36 | 4 | Max Milbers | |
37 | h2. Tools for migration |
||
38 | |||
39 | h3. Server settings of max execution time |
||
40 | |||
41 | When your server support max_execution overrides, then you can set here for the migration process an higher limit. |
||
42 | |||
43 | h3. Memory limit of the server |
||
44 | |||
45 | When your server support memory_limit overrides, then you can set here for the migration process an higher limit. |
||
46 | |||
47 | h3. Migration tasks |
||
48 | |||
49 | The radiobox gives you the possibility to execute different tasks of the migration |
||
50 | |||
51 | h4. general |
||
52 | |||
53 | This is importing the general data, medias, categories, manufacturers, etc |
||
54 | |||
55 | h4. users |
||
56 | |||
57 | This is importing the useraddresses |
||
58 | |||
59 | h4. products |
||
60 | Executes general and imports then the products |
||
61 | |||
62 | h4. orders |
||
63 | |||
64 | Executes products and imports then the orders |
||
65 | |||
66 | h4. everything |
||
67 | |||
68 | Import everything in the right order |
||
69 | |||
70 | h4. Set store owner |
||
71 | |||
72 | 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. |
||
73 | |||
74 | h3. Default category layout (browse page) |
||
75 | |||
76 | 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. |
||
77 | |||
78 | h3. Default category product layout (fly page) |
||
79 | |||
80 | Same as for the flypage, just for your browsepage |
||
81 | |||
82 | h3. Write here the new storeowner id |
||
83 | |||
84 | Set here the new storeowner id, when you execute "Set store owner" |