Difference between revisions of "Update"
From Galaxytool wiki
m (→updates from 3.x to version 4.0) |
(structure) |
||
| Line 19: | Line 19: | ||
| + | == Update from 3.x to version 4.0 == | ||
| + | You should no longer do this unless you really, really want to keep your antique data. If you have version 3.x please consider dropping this installation and installing the newest version. | ||
| − | === prerequisites | + | === prerequisites === |
# Make a backup of all needed notices, notices will '''not''' be imported to the new version! | # Make a backup of all needed notices, notices will '''not''' be imported to the new version! | ||
# Rename the alliances at allyhistory to its corresponding names. (If the allyname is 'main' or 'wing' the update process does not know the real allyname!) Otherwise the alliance history won't be imported to the new version. You would only be able to see the player history, but not the history of your alliance. | # Rename the alliances at allyhistory to its corresponding names. (If the allyname is 'main' or 'wing' the update process does not know the real allyname!) Otherwise the alliance history won't be imported to the new version. You would only be able to see the player history, but not the history of your alliance. | ||
# Do not interrupt the update process, it will take a while! | # Do not interrupt the update process, it will take a while! | ||
| − | # After the update you will not see "last update" at the galaxyview or the database status. This is the normal | + | # After the update you will not see "last update" at the galaxyview or the database status. This is the normal behavior! You can update the system again and everything will be updated as usual. The "last update" time is not imported to 4.0. |
# If you leave the variables $allyhistory and $playerhistory blank, you won't have the statistics. But this will save some space at your database. See [[Installation#config.php]] for details. | # If you leave the variables $allyhistory and $playerhistory blank, you won't have the statistics. But this will save some space at your database. See [[Installation#config.php]] for details. | ||
| − | === | + | === updating === |
You have to adjust the config.php and remove the /* and */ on line 28 and 39. After that you must fill in the old database table names (you may copy them from your old config.php). | You have to adjust the config.php and remove the /* and */ on line 28 and 39. After that you must fill in the old database table names (you may copy them from your old config.php). | ||
Revision as of 16:58, 19 December 2010
First you need to figure out what has changed in the config.php file.
A detailed description of the config.php is shown at the Installation guide.
Contents
Update to the latest version
After completing the following checklist, you should have no problems running the latest version.
- Download the latest version
- Modify config.php and attributes.php
- Upload new files and overwrite old files
- Run update.php
- modify everything until the update process can be started (the update.php will tell you which checks failed)
- Select your current version from which the tool should be updated to the latest version. If your version is not listed, you do not need to run that file!
- After a successful update you need to delete the update.php and install.php files.
- After updating from any version below 4.0 to the latest version, delete your old tables. They are not needed any more.
Update from 3.x to version 4.0
You should no longer do this unless you really, really want to keep your antique data. If you have version 3.x please consider dropping this installation and installing the newest version.
prerequisites
- Make a backup of all needed notices, notices will not be imported to the new version!
- Rename the alliances at allyhistory to its corresponding names. (If the allyname is 'main' or 'wing' the update process does not know the real allyname!) Otherwise the alliance history won't be imported to the new version. You would only be able to see the player history, but not the history of your alliance.
- Do not interrupt the update process, it will take a while!
- After the update you will not see "last update" at the galaxyview or the database status. This is the normal behavior! You can update the system again and everything will be updated as usual. The "last update" time is not imported to 4.0.
- If you leave the variables $allyhistory and $playerhistory blank, you won't have the statistics. But this will save some space at your database. See Installation#config.php for details.
updating
You have to adjust the config.php and remove the /* and */ on line 28 and 39. After that you must fill in the old database table names (you may copy them from your old config.php).
After you have done that and entered the new table names in the variables of line 13-22 you can start the update.php.
After a successful update you can delete the old tables and the variable names at config.php as well. (Line 29-38)
