Software Updates and Upgrades - Revision history

Derek Mueller: /* Updating to Beta Versions */

2014-12-04T00:32:22Z

‎Updating to Beta Versions

X2WikiAdmin: /* Using Backups */

2014-07-31T21:44:48Z

‎Using Backups

X2WikiAdmin: /* If The Update Failed After Applying Database Changes */

2014-07-31T21:43:17Z

‎If The Update Failed After Applying Database Changes

X2WikiAdmin: /* If The Update Failed After Applying Database Changes */

2014-07-31T21:42:57Z

‎If The Update Failed After Applying Database Changes

X2WikiAdmin: /* If The Update Failed After Applying Database Changes */

2014-07-31T21:42:14Z

‎If The Update Failed After Applying Database Changes

X2WikiAdmin: /* If The Update Failed After Applying Database Changes */

2014-07-31T21:41:44Z

‎If The Update Failed After Applying Database Changes

X2WikiAdmin: /* If The Update Failed After Applying Database Changes */

2014-07-31T21:39:16Z

‎If The Update Failed After Applying Database Changes

X2WikiAdmin: /* If The Update Failed When Applying File Changes */

2014-07-31T21:36:02Z

‎If The Update Failed When Applying File Changes

X2WikiAdmin: /* If The Update Failed When Applying File Changes */

2014-07-31T21:34:29Z

‎If The Update Failed When Applying File Changes

X2WikiAdmin: /* If The Update Failed When Applying File Changes */

2014-07-31T21:33:38Z

‎If The Update Failed When Applying File Changes

@@ Line 337: / Line 337: @@
 * '''It is not necessary to clear caches or user sessions when done.''' These operations are performed in updates to eliminate ephemeral (session-ingrained) data that may no longer be applicable and thus cause problems. Upgrades will rarely, if ever, invalidate this data.
 = Updating to Beta Versions =
 Beginning at version 4.1.2, after much advocacy to adopt this practice, X2Engine began a two-phase release process in which each version would be released first as a beta, then to the broader public after initial bug finds. The purpose behind this is to avoid updating production installations of X2Engine to new versions that have had zero public exposure, and thus avoid introducing bugs that were not found in initial QA testing (due to a incompatibility with a particular server environment or configuration of X2Engine) into sensitive production environments.
@@ Line 344: / Line 346: @@
 # Look for the following line, and in it, change "false" to "true": <syntaxhighlight lang="php">defined('X2_UPDATE_BETA') or define('X2_UPDATE_BETA',false);</syntaxhighlight>
-The advantage of enabling beta releases is that new features will be available much sooner. Additionally, fixes to bugs will also be available sooner. The main disadvantage of enabling beta releases is that they are never guaranteed to be as stable as non-beta releases. We encourage users to clone their installations of X2Engine, if able, and use beta versions on them, and report any issues they encounter for their particular server environment/special configuration/custom implementation of X2Engine. This way, any issues that arise can be fixed in the stable release. The more users participate in beta testing, the more stable the non-beta releases will become.
+The advantage of enabling beta releases is that new features will be available much sooner. Additionally, fixes to bugs will also be available sooner. The main disadvantage of enabling beta releases is that they are never guaranteed to be as stable as non-beta releases. We encourage users to clone their installations of X2Engine and use beta versions on them, and report any issues they encounter for their particular server environment/special configuration/custom implementation of X2Engine. This way, any issues that arise can be fixed in the stable release. The more users participate in beta testing, the more stable the non-beta releases will become.
 = Recovering From Failed Updates =

@@ Line 370: / Line 370: @@
 == Using Backups ==
-If a backup copy of the database is available, and the update failed in the middle of database changes, restoring the database to the backup can prove the easiest way to reset the database to a known state and saving effort in the recovery process. Doing so is recommended unless your database is exceedingly large (i.e. several hundred megabytes or more), in which case the restore operation will take a long time and possibly cause more damage if done improperly.
+If a backup copy of the database is available, and the update failed in the middle of database changes, restoring the database to the backup can prove to be the easiest way to reset the database to a known state and saving effort in the recovery process. Doing so is recommended unless your database is exceedingly large (i.e. several hundred megabytes or more), in which case the restore operation will take a long time and possibly cause more damage if done improperly.
 === Backup Validity and Applicability ===

@@ Line 363: / Line 363: @@
 <blockquote style="color:red">Encountered an issue after applying database changes.</blockquote>
-You can, in nearly all such cases, complete the update by performing these final steps of a manual update, from [[#Copying_new_files|copying the new files]] through [[#Clearing_caches_and_refreshing_the_application|cleaning up]]. Note, however, that if the error indicates that it failed to modify the configuration, i.e.
+You can, in nearly all such cases, complete the update by performing the final steps of a manual update from [[#Copying_new_files|copying the new files]] through [[#Clearing_caches_and_refreshing_the_application|cleaning up]]. Note, however, that if the error indicates that it failed to modify the configuration, i.e.
 <blockquote style="color:red">Failed to set version info in the configuration.</blockquote>

@@ Line 363: / Line 363: @@
 <blockquote style="color:red">Encountered an issue after applying database changes.</blockquote>
-You can, in nearly all such cases, complete the update by performing these final steps of a manual update: [[#Copying_new_files|copy new files]], [[#Deleting_old_files|delete old files]], [[#Editing_the_Configuration_File|update the version number in the configuration file]] and then [[#Clearing_caches_and_refreshing_the_application|clean up]]. Note, however, that if the error indicates that it failed to modify the configuration, i.e.
+You can, in nearly all such cases, complete the update by performing these final steps of a manual update, from [[#Copying_new_files|copying the new files]] through [[#Clearing_caches_and_refreshing_the_application|cleaning up]]. Note, however, that if the error indicates that it failed to modify the configuration, i.e.
 <blockquote style="color:red">Failed to set version info in the configuration.</blockquote>

@@ Line 359: / Line 359: @@
 == If The Update Failed After Applying Database Changes ==
-If this happened, the update is almost complete, and it is less effort to simply perform the final steps manually than trying to recover/reset the installation and start over. It should be indicated in an updater error message that begins with
+If this happened, the update is almost complete, and it is less effort to simply perform the final steps manually than trying to recover/reset the installation and start over. You will know if this is the case when it is explicitly indicated by an updater error message that begins with
 <blockquote style="color:red">Encountered an issue after applying database changes.</blockquote>

@@ Line 358: / Line 358: @@
 * '''The updater package for the version you attempted updating/upgrading from.''' This contains not just the important data but also flat data files that should prove helpful in diagnosing and fixing the problems. See "[[#Obtaining_the_Update_Package|Obtaining the Update Package]]."
-== If The Update Failed When Applying File Changes ==
+== If The Update Failed After Applying Database Changes ==
-If this happened, it should be indicated in an updater error message that begins with
+If this happened, the update is almost complete, and it is less effort to simply perform the final steps manually than trying to recover/reset the installation and start over. It should be indicated in an updater error message that begins with
 <blockquote style="color:red">Encountered an issue after applying database changes.</blockquote>
 You can in almost all cases complete the update by performing these final steps of a manual update: [[#Copying_new_files|copy new files]], [[#Deleting_old_files|delete old files]], [[#Editing_the_Configuration_File|update the version number in the configuration file]] and then [[#Clearing_caches_and_refreshing_the_application|clean up]].