Personal tools
Namespaces

Variants
Actions

How To Update WHMCS Module

From ModulesGarden Wiki
(Difference between revisions)
Jump to: navigation, search
(How To Update Provisioning Modules For WHMCS V5.2.2)
Line 54: Line 54:
 
{|
 
{|
 
|style="padding: 0px 0px 30px 15px;"|'''In case of failure, return to the previous version of the module and [https://www.modulesgarden.com/customers/support  report a problem].'''
 
|style="padding: 0px 0px 30px 15px;"|'''In case of failure, return to the previous version of the module and [https://www.modulesgarden.com/customers/support  report a problem].'''
|}
 
 
=How To Update Provisioning Modules For WHMCS V5.2.2=
 
{|
 
|style="padding: 10px 0px 10px 0px;"|<span style="color: #ff0000">'''If you downloaded our provisioning module/modules before 19.03.2013 and updated your WHMCS to V5.2.2, you need to also update module/modules.''' </span><br />
 
<span style="color: #ff0000">'''If you downloaded our provisioning module/modules for the first time on 19.03.2013 or later, you don't need to update anything.''' </span><br />
 
'''Please note that since WHMCS V5.2.1, server types nor modules names can not contain the underscore ( <span style="color: #ff0000">_</span> ). '''<br /><br />
 
'''Here is the list of modules which require your special attention:'''
 
|}
 
{|
 
|style="padding: 0px 0px 0px 30px;"|✔ cPanel Extended For WHMCS
 
|}
 
{|
 
|style="padding: 0px 0px 0px 30px;"|✔ DirectAdmin Extended For WHMCS
 
|}
 
{|
 
|style="padding: 0px 0px 0px 30px;"|✔ Plesk Extended For WHMCS
 
|}
 
{|
 
|style="padding: 0px 0px 0px 30px;"|✔ Rackspace Email For WHMCS
 
|}
 
{|
 
|style="padding: 0px 0px 0px 30px;"|✔ Rackspace Email Extended For WHMCS
 
|}
 
{|
 
|style="padding: 0px 0px 0px 30px;"|✔ Zimbra Email For WHMCS
 
|}
 
{|
 
|style="padding: 0px 0px 0px 30px;"|✔ cPanel Manage2 For WHMCS
 
|}
 
{|
 
|style="padding: 0px 0px 0px 30px;"|✔ Google Apps For WHMCS
 
|}
 
{|
 
|style="padding: 0px 0px 0px 30px;"|✔ WWD GoDaddy Domaind For WHMCS '''(more details in the following sections)'''
 
|}
 
{|
 
|style="padding: 20px 0px 10px 0px;"|'''Follow these instructions:'''
 
|}
 
{|
 
|style="padding: 10px 0px 10px 15px;"|1. Create backup of your WHMCS system.
 
|}
 
{|
 
|style="padding: 0px 0px 10px 15px;"|2. Remove old module files from your system.
 
|}
 
{|
 
|style="padding: 0px 0px 10px 15px;"|3. Download the latest module version from your clientarea.
 
|}
 
{|
 
|style="padding: 0px 0px 10px 15px;"|4. Upload all the module files into your main WHMCS directory.
 
|}
 
{|
 
|style="padding: 0px 0px 20px 15px;"|5. Update server/servers type through choosing new module name e.g. '' 'CpanelExtended' '' from a dropdown menu.
 
|}
 
{|
 
|style="padding: 0px 0px 20px 25px;"|[[File:MU1.png]]
 
|}
 
{|
 
|style="padding: 0px 0px 20px 15px;"|6. Update product/products module settings through choosing new module name e.g. '' 'CpanelExtended' '' from a dropdown menu.
 
|}
 
{|
 
|style="padding: 0px 0px 30px 25px;"|[[File:MU2.png]]
 
|}
 
 
==WWD GoDaddy Domains For WHMCS Update==
 
{|
 
|style="padding: 10px 0px 10px 0px;"|'''Follow these instructions:'''
 
|}
 
{|
 
|style="padding: 10px 0px 10px 15px;"|1. Create backup of your WHMCS system.
 
|}
 
{|
 
|style="padding: 0px 0px 10px 15px;"|2. Remove old module files from your system.
 
|}
 
{|
 
|style="padding: 0px 0px 10px 15px;"|3. Download the latest module version from your clientarea.
 
|}
 
{|
 
|style="padding: 0px 0px 10px 15px;"|4. Upload all the module files into your main WHMCS directory.
 
|}
 
{|
 
|style="padding: 0px 0px 20px 15px;"|5. Update registrar settings through choosing registrar module '' 'WwdGoDaddy' '' from a dropdown menu. Then enter your Go Daddy API User login and password.
 
|}
 
{|
 
|style="padding: 0px 0px 20px 25px;"|[[File:MU3.png]]
 
|}
 
{|
 
|style="padding: 0px 0px 20px 15px;"|6. Update domain pricing through choosing '' 'WwdGoDaddy' '' from an 'Auto Registration' '' dropdown menu.
 
|}
 
{|
 
|style="padding: 0px 0px 30px 25px;"|[[File:MU4.png]]
 
|}
 
==DNS Manager For WHMCS Update==
 
{|
 
|style="padding: 10px 0px 10px 0px;"|'''While updating DNS Manager to 1.9.10 version - compatible with the latest WHMCS V6.0.x remember to follow the below steps:'''
 
|}
 
{|
 
|style="padding: 10px 0px 10px 15px;"|1. Follow basic update instructions.
 
|}
 
{|
 
|style="padding: 0px 0px 10px 15px;"|'''IMPORTANT!'''<br/>
 
2. Replace your old integration codes from ''clientareahome.tpl'' with the one adequate to your WHMCS version.
 
|}
 
{|
 
|style="padding: 0px 0px 30px 15px;"|3. Find a very detailed information on the integration codes for each WHMCS and template version [http://www.docs.modulesgarden.com/DNS_Manager_For_WHMCS#Installation HERE,] look at point 5.
 
 
|}
 
|}

Revision as of 11:38, 23 November 2017

How To Update WHMCS Module

This article will help you go through the process of updating a WHMCS module.

Proceed with steps shown below to complete a basic update.
We will also list additional steps which may be needed.

Basic Update

1. In the beginning, please make a backup of your server.
2. Addon Modules Only: Log in to your WHMCS system admin area.

Go to 'Settings' 'Addon Modules' and deactivate the module you wish to update.
Note: This step is recommended but skip it if you want to keep your module's settings.

3. Download the latest version of the module from our website.
4. Remove all files of the old module version (except license.php file).
5. Upload and extract the new files to your WHMCS root directory. They will overwrite the old files.
6. Proceed to the module location and remove the 'license.php' file.

Now, rename 'license_RENAME.php' to 'license.php' file and edit it by providing your module license.
Note: This step is mandatory only in some part of cases, due to changes in the packaging system.

7. Remove all files from '\your_whmcs\template_c\' directory.
8. (Addon Modules Only) Log in to your WHMCS system admin area.

Go to 'Settings' 'Addon Modules' and activate the recently updated module.

Optional Actions Needed

It may happen, that after the update of a module, it still causes a lot of errors.

If so, we advice to check the module's wiki article and check whether additional actions are needed.
Especially look for:
1. Folders which need specific chmods.
2. Earlier settings of chmods which got overwritten.
3. New cron job added or old cron job removed.
4. Use of migration tool needed to import settings from earlier version.
5. Settings removed during the update.
6. Integration codes that need to be changed after the upgrade.
7. Additional steps listed in the installation instruction.

In case of failure, return to the previous version of the module and report a problem.
Navigation
WHMCS Modules
WHMCS Widgets
Translations
cPanel Modules
General
FAQ
Community