Difference between revisions of "Update"

Latest revision as of 13:23, 21 September 2012

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

Create a backup of your database
Download the latest version and unzip them
Upload new files and overwrite old files - the old config.php and attributes.php must be kept
Make sure, the old config.php and attributes.php are writable
Now delete your browser cache, so you'll get the most recent JavaScript files from the server
Run update.php in your browser
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 the update!
Enter all required information on the screen in your browser - no need to manually edit any files
In the last step of the update, the Galaxytool is automatically refreshed via OGame API - if this is not desired, cancel this step by closing the browser tab right after updating the tables
After a successful update you need to delete the update.php and install.php files.
Finally, remind all your users to delete their browser cache, otherwise things could look strange for them

@@ Line 1: / Line 1: @@
-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.
-== Update to the latest version ==
 After completing the following checklist, you should have no problems running the latest version.
-# Download the latest version
+# [http://www.ehow.com/how_2036600_create-database-php.html Create a backup of your database]
-# Modify config.php and attributes.php
+# [[Download]] the latest version and unzip them
-# Upload new files and overwrite old files
+# Upload new files and overwrite old files - ''' the old config.php and attributes.php must be kept'''
-# Run update.php
+# Make sure, the old config.php and attributes.php are [[How to set writable permissions|writable]]
-# modify everything until the update process can be started (the update.php will tell you which checks failed)
+# Now delete your browser cache, so you'll get the most recent JavaScript files from the server
-# 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!
+# Run update.php in your browser
+# 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 the update!
+# Enter all required information on the screen in your browser - '''no need to manually edit any files'''
+# In the last step of the update, the Galaxytool is automatically refreshed via OGame API - if this is not desired, cancel this step by closing the browser tab right after updating the tables
 # 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.
+# Finally, remind all your users to delete their browser cache, otherwise things could look strange for them
-== Update from 4.0->4.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 '''[http://www.ehow.com/how_2036600_create-database-php.html 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://bluetool.bluebird-allianz.org/viewtopic.php?f=9&t=13&p=13#p13 .
-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 [[Updates|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 [https://addons.mozilla.org/en-US/firefox/addon/8588 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 ===
-# 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)
 [[de:Update]]
 [[es:Updates]]

Difference between revisions of "Update"

Latest revision as of 13:23, 21 September 2012

Navigation menu

Views

Personal tools

Navigation

Galaxytool

Get in touch with support

Social Media

Search

Tools

In other languages