Updating - Revision history

SarahK: /* Database Privileges */

2023-02-08T21:47:58Z

‎Database Privileges

SarahK: /* Down for Maintenance or Update in Progress */

2022-11-16T15:30:44Z

‎Down for Maintenance or Update in Progress

SarahK: /* Updating Manually */

2022-10-20T19:43:59Z

‎Updating Manually

SarahK: /* Distributions */

2022-10-20T18:48:55Z

‎Distributions

SarahK: /* Updating Manually */

2022-10-20T16:28:04Z

‎Updating Manually

SarahK at 22:42, 11 March 2022

2022-03-11T22:42:55Z

SarahK: /* Updating Manually */

2022-01-18T20:56:06Z

‎Updating Manually

SarahK at 20:16, 18 January 2022

2022-01-18T20:16:18Z

Show changes

SarahK at 19:27, 18 January 2022

2022-01-18T19:27:30Z

John: /* For a Full Release Version */ Removed reference to automatic redirect to install.php due to CORE-16818

2021-07-13T17:19:44Z

‎For a Full Release Version: Removed reference to automatic redirect to install.php due to CORE-16818

@@ Line 11: / Line 11: @@
 ===Database Privileges===
-Updating requires that the database user have access to the following privileges:
+Updating requires that the database user has access to the required privileges.
-−
-*<tt>ALTER</tt>
+For more information and a list of required privileges, see [[System_Environment_Guide#Database_Privileges|System Environment Guide]].
 ===Customisations===

@@ Line 65: / Line 65: @@
 ===Down for Maintenance or Update in Progress===
-If, after uploading the files from a Patch Set, you see a "Down for Maintenance" or "update in progress..." warning message, then this indicates that the patch set files you attempted to apply are not compatible with the version of WHMCS you were previously running.
+If, after uploading the files from a Patch Set, you see a '''Down for Maintenance''' or '''update in progress...''' message,  the patch set files you attempted to apply are not compatible with the version of WHMCS you were previously running.
-To complete the update you will need to download the latest [[Updating#For_a_Full_Release_Version|Full Release]] version and update using the regular update process above.
+To complete the update, download the latest [[Updating#For_a_Full_Release_Version|Full Release]] version and update using the regular update process above.

@@ Line 38: / Line 38: @@
 You can also update your WHMCS installation manually using one of two methods:
-* You can use your hosting control panel's file management system to manage the necessary files. For more information, see [https://go.whmcs.com/1709/Updating-WHMCS-Manually Updating WHMCS Manually].
+* You can use FTP or your hosting control panel's file management system to manage the necessary files. For more information, see [https://go.whmcs.com/1709/Updating-WHMCS-Manually Updating WHMCS Manually].
 * If you are comfortable running commands on the server that hosts your WHMCS installation, you can make the necessary changes on the command line. For more information, see [[Install On The Command Line]].

@@ Line 43: / Line 43: @@
 ===Distributions===
-We distribute WHMCS in two ways: '''Full Release''' distributions and '''Patch Set''' distributions.
+We distribute WHMCS in '''Full Release''' and '''Patch Set''' distributions. You can identify the distribution type by examining the distribution's <tt>.zip</tt> file and the contents of the included <tt>README.txt</tt> file:
-A '''Full Release''' distribution contains all the files of a WHMCS product installation. You can use it to perform a new installation or update an existing installation (regardless of previous version).
+<table class="table table-striped table-condensed">
-'''Patch Set''' distributions contain only the files that have changed between the immediate previous version and the latest version (for example, a patch set for version 1.1.2 is valid for a 1.1.1 installation and nothing else). We provide these to make updating both quicker and easier for those of our customers who stay current and up-to-date with the latest WHMCS releases. By including only the changed files, patch sets have less files to upload, which makes the update process quicker and simpler for you to perform.
+For example, we would recommend using a '''Full Release''' distribution to move from an End-of-Life version to the newest release. You could '''only''' use a '''Patch Set''' distribution if you were moving from the immediately previous release to the newest release.
 For more information on our release and distribution types, see [[Releases]].

@@ Line 38: / Line 38: @@
 You can also update your WHMCS installation manually using one of two methods:
-* You can use your hosting control panel's file management system to manage the necessary files. For more information, see [[Updating WHMCS Manually]].
+* You can use your hosting control panel's file management system to manage the necessary files. For more information, see [https://go.whmcs.com/1709/Updating-WHMCS-Manually Updating WHMCS Manually].
 * If you are comfortable running commands on the server that hosts your WHMCS installation, you can make the necessary changes on the command line. For more information, see [[Install On The Command Line]].

@@ Line 7: / Line 7: @@
 ==Preparing for Updates==
-Preparation helps to ensure a seamless updating experience. For more information, see our recommendations for [https://blog.whmcs.com/133532/our-top-tips-for-a-seamless-update preparation, testing, and execution of WHMCS updates].
+Preparation helps to ensure a seamless updating experience. For more information, see [[Get WHMCS Download Information]] and our recommendations for [https://blog.whmcs.com/133532/our-top-tips-for-a-seamless-update preparation, testing, and execution of WHMCS updates].
 ===Database Privileges===

@@ Line 42: / Line 42: @@
 #Unzip the contents of the downloaded WHMCS <tt>.zip</tt> file to a folder on your computer.<div class="docs-alert-danger"><span class="title">Custom Admin Directory?</span><br />If you have renamed your "admin" directory, rename the <tt>/whmcs/admin</tt> directory in the new files to match. </div><div class="docs-alert-warning"><span class="title">Custom Cron Directory?</span><br />If you have customised the location of the <tt>/crons/</tt> directory, be sure to upload that to the custom location.</div><div class="docs-alert-success"><span class="title">Custom File Permissions?</span><br />If you have customised the permissions on any of the files (for example, <tt>/crons/pipe.php</tt>). You must reapply these changes after the update is complete.</div>
 #Upload the new files to your existing installation folder, replacing any existing folders and files.
-#Visit the update page at <tt>yourdomain.com/whmcs/install/install.php</tt>. If you see a message that states that you have not installed WHMCS, you may have overwritten the <tt>configuration.php</tt> file for your installation. Stop and restore that file from your backup before continuing.
+#Visit the update page at <tt>example.com/whmcs/install/install.php</tt>. If you see a message that states that you have not installed WHMCS, you may have overwritten the <tt>configuration.php</tt> file for your installation. Stop and restore that file from your backup before continuing.
 #Agree to the WHMCS End User License Agreement and follow the prompts to update your database.
 #When the system prompts you, delete the installation folder from your server.