Update

First you need to figure out what has changed in the config.php file. [[[1]] A detailed description of the config.php is shown at the Installation guide.

Update to the latest version

After completing the following checklist, you should have no problems running the latest version.

1. Create a backup of your database
2. Download the latest version
3. Modify config.php and attributes.php
4. Upload new files and overwrite old files
5. Run update.php
6. modify everything until the update process can be started (the update.php will tell you which checks failed)
7. 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!
8. After a successful update you need to delete the update.php and install.php files.
9. After updating from any version below 4.0 to the latest version, delete your old tables. They are not needed any more.

Some information on old updates can be found in the following passage. Please note, that you have to execute update.php only once, so you can directly update from any 4.x version to the latest one!

Update from v4.8 to v4.9

Important: The file config.php contains a new table name for the new report archive feature. In order to update properly, make a backup of your old config.php-file and copy the settings of the old file into the new file. This way the new table name can't be forgotten.

The attributes.php-file didn't change, so you can simply take the old one.

Another important thing is to remove your old Galaxytool files completely and re-upload all files.

If you are user of the Bluetool: Please look at the following page http://en.bluetool.eu/wiki/Download . That is is the update of the Bluetool, which belongs to v4.8 of the Galaxytool. Please notice, that you may have to execute another update.php for the Bluetool itself. For more information look at the corresponding link above.

Before you start the update create a backup of the database. Use only phpmyadmin for this job. Mysqldumper will not copy the TRIGGERs.

After creating the database backup and uploading all the new files to your webspace, open the update.php with your browser, select the previous version of your Galaxytool and click on "Submit".

Note: After the update on v4.8, the Galaxytool works only with the Firefox AddOn v2.6 or above. You should get this version automatically via AutoUpdate-function of Firefox. If that doesn't work, you can download the most recent version here.

Note: After updating you may notice some issues viewing some pages. Please empty your browser cache in order to solve the problems.

Update from v4.6 to v4.7.1

Important: The file config.php contains new table names for the new features. In order to update properly, make a backup of your old config.php-file and copy the settings of the old file into the new file. This way the new table names can't be forgotten. Besides, this file contains a new variable $dbprefix. You can set this variable, if you need a prefix at every database table name. This way you don't have to rename every table name by hand in the config-file.

The attributes.php-file didn't change, so you can simply take the old one.

Another important thing is to remove your old Galaxytool files completely, because the folder structure has changed, and otherwise some files may be redundant or obsolete on your webspace (when only overwriting the old files).

If you are user of the Bluetool: Please look at the following page http://en.bluetool.eu/wiki/Download . That is is the update of the Bluetool, which belongs to v4.7 of the Galaxytool. Please notice, that you may have to execute another update.php for the Bluetool itself. For more information look at the corresponding link above.

Before you start the update create a backup of the database. Use only phpmyadmin for this job. Mysqldumper will not copy the TRIGGERs.

After creating the database backup and uploading all the new files to your webspace, open the update.php with your browser, select the previous version of your Galaxytool and click on "Submit".

Update from v4.0->v4.5.4 to v4.6

Important: The files attributes.php and config.php have their own directory now ('config'). Besides, the content of these files has changed. Therefore, it is better to create a copy of those two files, and copy the settings from the old files into the new ones.

On top of that, you should create a backup of the database before. After updating to 4.6 you shouldn't use mysqldumper but phpmyadmin to create database dumps, since mysqldumper doesn't export TRIGGERs in the current version (1.24).

Instead of overwriting all files, you should delete all the old files and upload the new files after that (some files became obsolete).

If you are user of the Bluetool: Please look at the following page http://en.bluetool.eu/wiki/Download . That is is the update of the Bluetool, which belongs to v4.6 of the Galaxytool and works only with that version. Please notice, that you have to execute another update.php for the Bluetool itself. For more information look at the corresponding link above.

After noting all the advice and uploading all new files you can execute the update.php as usual. More on this topic here.

Please note, that the Galaxytool requires PHP5 and MySQL5 from now on. If you would like to use the 'Historical Overview', you'll need PHP5.1. Besides, you need from MySQL v5.1.6 TRIGGER-rights at the database, before this version you need SUPER-rights.

Note: After the update on v4.6, the Galaxytool works only with the Firefox AddOn v2.4 or above. You should get this version automatically via AutoUpdate-function of Firefox. If that doesn't work, you can download the most recent version here.

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

1. Make a backup of all needed notices, notices will not be imported to the new version!
2. 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.
3. Do not interrupt the update process, it will take a while!
4. 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.
5. 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)