Recent versions: ||| Galaxytool: v5.1 ||| Galaxytoolbar: v2.6.32 |||

Difference between revisions of "Update"

From Galaxytool wiki
Jump to: navigation, search
m (Reverted edits by 89.34.102.202 (Talk); changed back to last version by ThePatriot)
m
 
(39 intermediate revisions by 15 users not shown)
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 from any Version to the latest version ===
 
 
 
After completing the following checklist, you should have no problems running 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
+
# [[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 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
 
 
 
 
 
 
=== prerequisites to upgrade to version 4.0 ===
 
 
 
# 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. 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!
 
  
Note: version 4.0 is '''not''' available yet
+
[[de:Update]]
 +
[[es:Updates]]

Latest revision as of 13:23, 21 September 2012

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 and unzip them
  3. Upload new files and overwrite old files - the old config.php and attributes.php must be kept
  4. Make sure, the old config.php and attributes.php are writable
  5. Now delete your browser cache, so you'll get the most recent JavaScript files from the server
  6. Run update.php in your browser
  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 the update!
  8. Enter all required information on the screen in your browser - no need to manually edit any files
  9. 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
  10. After a successful update you need to delete the update.php and install.php files.
  11. Finally, remind all your users to delete their browser cache, otherwise things could look strange for them