Difference between revisions of "Updating"

From WHMCS Documentation

m (Performing a Manual Update)
m
Line 1: Line 1:
We always recommend staying up-to-date with WHMCS in order to benefit from the latest development and improvements, and you can do that either by [https://www.whmcs.com/services/upgrade-service/ having us perform the update for you] or by updating as per the steps below.
+
We always recommend staying up-to-date with WHMCS in order to benefit from the latest development and improvements. You can do this by [https://www.whmcs.com/services/upgrade-service/ having us perform the update for you] or by updating using the steps below.
  
 
==Automatic Updating==
 
==Automatic Updating==
  
If you are running WHMCS 7.0 or later, you can use the built-in Automatic Update utility.
+
If you are running WHMCS 7.0 or later, you can use the built-in Automatic Update utility. To do this:
  
 
* Navigate to '''Utilities > Update WHMCS''' to begin the process.
 
* Navigate to '''Utilities > Update WHMCS''' to begin the process.
* Click ''Update Now''
+
* Click ''Update Now''.
* Follow the on-screen wizard through the update process.
+
* Follow the prompts through the update process.
  
 
[[File:UpdateAvailable.png|center]]
 
[[File:UpdateAvailable.png|center]]
  
<div class="docs-alert-info"><i class="fa fa-info-circle fa-fw"></i>&nbsp; If the update was released recently, you may need to click the Check for Updates button before the update will show as available.</div>
+
<div class="docs-alert-info"><i class="fa fa-info-circle fa-fw"></i>&nbsp; If we released an update recently, you may need to click ''Check for Updates'' before the update will display.</div>
  
For more information about the Automatic Updater and troubleshooting please refer to [[Automatic Updater]]
+
For more information about the Automatic Updater and troubleshooting, see [[Automatic Updater]].
  
 
==Performing a Manual Update==
 
==Performing a Manual Update==
Line 19: Line 19:
 
[[File:Videotutorial.png|center|link=http://www.youtube.com/watch?v=wXZpPjPxvfY&hd=1|Watch Video Tutorial]]
 
[[File:Videotutorial.png|center|link=http://www.youtube.com/watch?v=wXZpPjPxvfY&hd=1|Watch Video Tutorial]]
  
 +
To update WHMCS manually, follow the steps in the section below. Some updates may require steps in addition to the standard update steps below.  We provide this information in the [[Release Notes]].  Always refer to the release notes for a version before attempting any update.
  
To update WHMCS manually, follow the steps below. Some updates may require steps in addition to the standard update steps provided below.  Should these be required you will find them in the [[Release Notes]].  Please always refer to the release notes for a version before attempting any update.
+
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).
  
A '''Full Release''' distribution contains all the files of a WHMCS product installation. It can be used to perform a new install or update an existing installation (regardless of previous version).
+
'''Patch Sets''' 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.
  
'''Patch Sets''' contain only the files that have changed between the immediate, previous version and the latest version, (ie. 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 more information on our release types and distribution types, see our [[Releases]] page. Advanced users can also perform upgrades [[Install_On_The_Command_Line|from the command line]].
 
 
More information on our release types and distribution types can be found on our [[Releases]] page. Advanced users can also perform upgrades [[Install_On_The_Command_Line|from the command line]].
 
  
 
==Update Steps==
 
==Update Steps==
Line 32: Line 31:
 
===For a Full Release Version===
 
===For a Full Release Version===
  
A full release version is denoted by the presence of _full within the zip folder filename and "Distro Type: Full Version" within the included README.txt file.  If the zip file you have instead contains _patch, please refer to the below [[Updating#For_a_Patch_Set|Patch Set update Steps]] instead.
+
A full release version includes <tt>_full</tt> within the <tt>.zip</tt> folder filename and "Distro Type: Full Version" within the included <tt>README.txt</tt> file.  If the <tt>.zip</tt> filename contains <tt>_patch</tt>, see the [[Updating#For_a_Patch_Set|Patch Set update Steps]] section below.
 +
 
 +
'''Make a Full Backup. We cannot stress enough how important it is to always create a full backup before attempting any kind of update, both for WHMCS and for any other software you use.  In your full backup, include both the WHMCS files and the database.'''
  
'''Make a Full Backup - We cannot stress enough how important it is to *always* take a full backup before attempting any kind of update. Both for WHMCS and any other software you use.  A full backup should be taken of both the WHMCS files and the database.'''
+
To update for a full release version:
  
#Begin by making sure your server meets the [[System_Requirements|system requirements]],
+
#Make certain that your system meets our [[System_Requirements|system requirements]].
#Obtain the latest full release download of WHMCS either from http://download.whmcs.com/ or from your license provider (if using a reseller)
+
#Obtain the latest full release download of WHMCS from http://download.whmcs.com/ or, if you use a reseller, from your license provider.
#Unzip the contents of the WHMCS zip file download 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, be sure to rename the /whmcs/admin directory in the new files to match. </div><div class="docs-alert-warning"><span class="title">Custom Cron Directory?</span><br />Similarly, if you have customised the location of the /crons/ 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 eg. /crons/pipe.php. These changes will need to be re-applied once the update is complete.</div>
+
#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 & files
+
#Upload the new files to your existing installation folder, replacing any existing folders and files.
#Visit your WHMCS installation and you should then be automatically redirected to the update process. If you are not automatically redirected, you may visit the installer page directly at yourdomain.com/whmcs/install. If you see a message saying WHMCS is not installed, this indicates you have overwritten the configuration.php file for your installation. Stop and restore that file from your backup before continuing.
+
#Visit your WHMCS installation. The system will automatically direct you to the update process. If the system doesn't auitomatically redirect you, visit the installation page directly at <tt>yourdomain.com/whmcs/install</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 steps on screen to update your database.
+
#Agree to the WHMCS End User License Agreement and follow the prompts to update your database.
#When prompted, delete the install folder from your server.
+
#When the system prompts you, delete the installation folder from your server.
 
#Your update is now complete.
 
#Your update is now complete.
  
We recommend now that you check the release notes for the version you just installed [[Release_Notes|here]]. And if you have custom template files you will also need to review and make any necessary changes to your custom templates using the information provided in the Template Changes section of the [[Release_Notes|Release Notes]].
+
We recommend that you check the release notes for the version you just installed [[Release_Notes|here]]. If you have custom template files, you will also need to review and make any necessary changes to your custom templates. For more information, see the Template Changes section of the [[Release_Notes|Release Notes]].
  
 
===For a Patch Set===
 
===For a Patch Set===
  
A patch set version is denoted by the presence of _patch within the zip folder filename and "Distro Type: Patch Set" within the included README.txt file.
+
A patch set version includes <tt>_patch</tt> within the <tt>.zip</tt> folder name and "Distro Type: Patch Set" within the included <tt>README.txt</tt> file.
 +
 
 +
'''IMPORTANT:''' Before you begin, make sure you are running the version that the patch requires. Patch Sets contain only the files that have changed between the previous release and the Patch Set Version. Only apply them if you are running the immediately-previous version.
  
'''IMPORTANT:''' Before you begin please ensure you are running the version required by the patch. Patch Sets contain only the files that have changed between the previous release and the Patch Set Version. Therefore they should only be applied if you are running the immediately previous version.
+
The previous release version that we designed these patch sets for is part of the first and smaller number in release notices providing the patch set download link.
  
The previous release version that these patch sets are designed for is clearly indicated as the first and smaller number in release notices providing the patch set download link.
+
To update using a patch set:
  
#Download the patch set from http://download.whmcs.com/
+
#Download the patch set from http://download.whmcs.com/.
#Unzip the patch set files<div class="docs-alert-danger"><span class="title">Custom Admin Directory?</span><br />For patches that have updates for the “admin” directory: If you have renamed your "admin" directory, then make sure you rename the /whmcs/admin directory to match</div>
+
#Unzip the patch set files.<div class="docs-alert-danger"><span class="title">Custom Admin Directory?</span><br />If your patch set includes changes to the <tt>admin</tt> directory and you have renamed your "admin" directory, rename the <tt>/whmcs/admin</tt> directory in the new files to match. </div>
#Upload the files from the /whmcs/ directory to the root directory of your WHMCS installation
+
#Upload the files from the <tt>/whmcs/</tt> directory to the root directory of your WHMCS installation.
#Visit the admin area of your WHMCS installation to trigger the version number bump and complete the process  
+
#Visit the admin area of your WHMCS installation to trigger the version number increment and complete the process.
  
No install or update process is required.
+
This method doesn't require an install or update process.
  
 
==Confirming a Successful Update==
 
==Confirming a Successful Update==
  
To confirm an update has been successfully applied, login to your WHMCS admin area and check to make sure that the Version Number displayed either on the admin homepage (in the sidebar of all default templates) or in '''Help > System Health Status''' is the version you attempted to apply. If it has not incremented, then one or more of the files has not uploaded successfully. You should double check file permissions and attempt the steps again from the beginning.
+
To confirm that an update applied successfully, log in to your WHMCS admin area. Then, check to make sure that the version number on either the admin homepage (in the sidebar of all default templates) or in '''Help > System Health Status''' is the version that you attempted to apply. If it has not incremented, then one or more of the files has not uploaded successfully. Check your file permissions and attempt the steps again from the beginning.
  
 
==Helpful Hints==
 
==Helpful Hints==
 +
 
'''Top Tips for A Seamless Update'''
 
'''Top Tips for A Seamless Update'''
  
Preparation is key for ensuring a seamless updating experience. Review our detailed blog post which provides 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 our recommendations for [https://blog.whmcs.com/133532/our-top-tips-for-a-seamless-update preparation, testing and execution of WHMCS updates].
  
 
'''Database Privileges'''
 
'''Database Privileges'''
Line 75: Line 79:
 
Updating requires that the database user have access to the following privileges:
 
Updating requires that the database user have access to the following privileges:
 
   
 
   
*ALTER
+
*<tt>ALTER</tt>
*CREATE
+
*<tt>CREATE</tt>
*DROP
+
*<tt>DROP</tt>
*INDEX
+
*<tt>INDEX</tt>
 
   
 
   
Additionally, you will want to ensure that the database user have access to all privileges listed on the [[Further_Security_Steps#Restrict_Database_Privileges|Further Security Steps]] page.
+
Additionally, you will want to ensure that the database user have access to all of the privileges on the [[Further_Security_Steps#Restrict_Database_Privileges|Further Security Steps]] page.
  
 
'''Customisations'''
 
'''Customisations'''
  
If you have customised templates, please ensure you always follow the recommended method for [[Client_Area_Template_Files#Creating_a_Custom_Template|creating a custom template folder]] to ensure your changes aren't overwritten during updates. Similarly for language file customisations please ensure you use the [https://developers.whmcs.com/languages/overrides/ Language Overrides] feature vs editing the language files directly.
+
If you have customised templates, make sure to follow the recommended method for [[Client_Area_Template_Files#Creating_a_Custom_Template|creating a custom template folder]] to ensure your changes aren't overwritten during updates. Similarly, for language file customisations, make sure that you use the [https://developers.whmcs.com/languages/overrides/ Language Overrides] feature instead of editing the language files directly.
  
 
'''Bad Formatting'''
 
'''Bad Formatting'''
  
If when you first login you see a display where formatting is mixed or unclear, this can indicate your browser cache has not updated. Try clearing your browser cache or performing a hard refresh (typically Ctrl + F5) and delete the contents of the template cache directory (''templates_c'' by default) to ensure you see the new templates and styling.
+
If, when you first log in, you see a mixed or unclear formatting, your browser may not have updated. Try clearing your browser cache or performing a hard refresh (typically <tt>Ctrl + F5</tt>) and delete the contents of the template cache directory (''templates_c'' by default) to ensure that you see the new templates and styling.
  
 
'''What to do if you get a Down for Maintenance or update in Progress message after uploading a patch set'''
 
'''What to do if you get a Down for Maintenance or update in Progress message after uploading a patch set'''
  
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. 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 as described above.
+
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. 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.
  
 
==We're here to help==
 
==We're here to help==
  
We offer a professional update service where our staff will update your WHMCS installation for you. Please refer to https://www.whmcs.com/services/upgrade-service/ for more information and to order.
+
We offer a professional update service where our staff will update your WHMCS installation for you. For more information and to order services, see https://www.whmcs.com/services/upgrade-service/.
  
And of course our support team is always available to answer any questions or concerns you might have when performing the update process yourselfSimply open a ticket @ http://www.whmcs.com/get-support/ and a member of our team will get back to you..
+
Our support team is always available to answer any questions or concerns you might have when performing updatesOpen a ticket at http://www.whmcs.com/get-support/ and a member of our team will assist you.

Revision as of 18:51, 28 April 2020

We always recommend staying up-to-date with WHMCS in order to benefit from the latest development and improvements. You can do this by having us perform the update for you or by updating using the steps below.

Automatic Updating

If you are running WHMCS 7.0 or later, you can use the built-in Automatic Update utility. To do this:

  • Navigate to Utilities > Update WHMCS to begin the process.
  • Click Update Now.
  • Follow the prompts through the update process.
UpdateAvailable.png
  If we released an update recently, you may need to click Check for Updates before the update will display.

For more information about the Automatic Updater and troubleshooting, see Automatic Updater.

Performing a Manual Update

Watch Video Tutorial

To update WHMCS manually, follow the steps in the section below. Some updates may require steps in addition to the standard update steps below. We provide this information in the Release Notes. Always refer to the release notes for a version before attempting any update.

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).

Patch Sets 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 more information on our release types and distribution types, see our Releases page. Advanced users can also perform upgrades from the command line.

Update Steps

For a Full Release Version

A full release version includes _full within the .zip folder filename and "Distro Type: Full Version" within the included README.txt file. If the .zip filename contains _patch, see the Patch Set update Steps section below.

Make a Full Backup. We cannot stress enough how important it is to always create a full backup before attempting any kind of update, both for WHMCS and for any other software you use. In your full backup, include both the WHMCS files and the database.

To update for a full release version:

  1. Make certain that your system meets our system requirements.
  2. Obtain the latest full release download of WHMCS from http://download.whmcs.com/ or, if you use a reseller, from your license provider.
  3. Unzip the contents of the downloaded WHMCS .zip file to a folder on your computer.
    Custom Admin Directory?
    If you have renamed your "admin" directory, rename the /whmcs/admin directory in the new files to match.
    Custom Cron Directory?
    If you have customised the location of the /crons/ directory, be sure to upload that to the custom location.
    Custom File Permissions?
    If you have customised the permissions on any of the files (for example, /crons/pipe.php). You must reapply these changes after the update is complete.
  4. Upload the new files to your existing installation folder, replacing any existing folders and files.
  5. Visit your WHMCS installation. The system will automatically direct you to the update process. If the system doesn't auitomatically redirect you, visit the installation page directly at yourdomain.com/whmcs/install. If you see a message that states that you have not installed WHMCS, you may have overwritten the configuration.php file for your installation. Stop and restore that file from your backup before continuing.
  6. Agree to the WHMCS End User License Agreement and follow the prompts to update your database.
  7. When the system prompts you, delete the installation folder from your server.
  8. Your update is now complete.

We recommend that you check the release notes for the version you just installed here. If you have custom template files, you will also need to review and make any necessary changes to your custom templates. For more information, see the Template Changes section of the Release Notes.

For a Patch Set

A patch set version includes _patch within the .zip folder name and "Distro Type: Patch Set" within the included README.txt file.

IMPORTANT: Before you begin, make sure you are running the version that the patch requires. Patch Sets contain only the files that have changed between the previous release and the Patch Set Version. Only apply them if you are running the immediately-previous version.

The previous release version that we designed these patch sets for is part of the first and smaller number in release notices providing the patch set download link.

To update using a patch set:

  1. Download the patch set from http://download.whmcs.com/.
  2. Unzip the patch set files.
    Custom Admin Directory?
    If your patch set includes changes to the admin directory and you have renamed your "admin" directory, rename the /whmcs/admin directory in the new files to match.
  3. Upload the files from the /whmcs/ directory to the root directory of your WHMCS installation.
  4. Visit the admin area of your WHMCS installation to trigger the version number increment and complete the process.

This method doesn't require an install or update process.

Confirming a Successful Update

To confirm that an update applied successfully, log in to your WHMCS admin area. Then, check to make sure that the version number on either the admin homepage (in the sidebar of all default templates) or in Help > System Health Status is the version that you attempted to apply. If it has not incremented, then one or more of the files has not uploaded successfully. Check your file permissions and attempt the steps again from the beginning.

Helpful Hints

Top Tips for A Seamless Update

Preparation helps to ensure a seamless updating experience. For more information, see our recommendations for preparation, testing and execution of WHMCS updates.

Database Privileges

Updating requires that the database user have access to the following privileges:

  • ALTER
  • CREATE
  • DROP
  • INDEX

Additionally, you will want to ensure that the database user have access to all of the privileges on the Further Security Steps page.

Customisations

If you have customised templates, make sure to follow the recommended method for creating a custom template folder to ensure your changes aren't overwritten during updates. Similarly, for language file customisations, make sure that you use the Language Overrides feature instead of editing the language files directly.

Bad Formatting

If, when you first log in, you see a mixed or unclear formatting, your browser may not have updated. Try clearing your browser cache or performing a hard refresh (typically Ctrl + F5) and delete the contents of the template cache directory (templates_c by default) to ensure that you see the new templates and styling.

What to do if you get a Down for Maintenance or update in Progress message after uploading a patch set

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. To complete the update you will need to download the latest Full Release version and update using the regular update process above.

We're here to help

We offer a professional update service where our staff will update your WHMCS installation for you. For more information and to order services, see https://www.whmcs.com/services/upgrade-service/.

Our support team is always available to answer any questions or concerns you might have when performing updates. Open a ticket at http://www.whmcs.com/get-support/ and a member of our team will assist you.