Difference between revisions of "Directory Refresh Guide"
(Redirected page to Contents) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | # | + | ==Refreshing a Directory== |
| + | Refreshing directories can help to troubleshoot and resolve some errors. The example below refreshes the <tt>/modules/servers/</tt> directory. | ||
| + | |||
| + | To do this: | ||
| + | # Download and unzip the WHMCS file set that matches the current version of your WHMCS. You can download current versions of WHMCS including Long Term support versions from [https://download.whmcs.com/ WHMCS Downloads Page]. | ||
| + | # Navigate to the directory to refresh <tt>/whmcs/modules/</tt>. | ||
| + | # Rename the unaltered ‘’’servers’’’ directory to contain the original name and the date. For example, <tt>servers_new_MM_DD_YYYY</tt>. | ||
| + | # Upload the unaltered directory to the parent directory within your WHMCS installation (in this example, the <tt>/modules/</tt> directory). | ||
| + | # Rename the previous directory and include the date. For example,<tt>servers_old_MM_DD_YYYY</tt>. | ||
| + | # Revert the new directory name to the original name. For example, <tt>servers</tt>. | ||
| + | <div class="docs-alert-success"> | ||
| + | After you finish, check within WHMCS to ensure that refreshing the directory resolved your issue. | ||
| + | </div> | ||
| + | |||
| + | == Restoring Customisations == | ||
| + | |||
| + | After confirming that refreshing the directory has resolved your issue, you may need to restore any customisations. | ||
| + | |||
| + | To achieve this, you would need to copy the customisation from the ‘<tt>servers_old_MM_DD_YYYY</tt> directory to the now refreshed <tt>servers </tt> directory. | ||
| + | |||
| + | We recommend moving each customisation seperately and checking for errors within WHMCS in between each addition. This allows you to identify any problems by the specific module and allow you to choose whether to remove the customization or contact the third-party developer for help." | ||
| + | === Cron Directory === | ||
| + | |||
| + | Refreshing the cron directory may require additional steps, including updating your configuration in the <tt>config.php</tt> file. | ||
| + | |||
| + | To do this, use the instructions within the <tt>config.php</tt> file in the crons directory to uncomment the WHMCS path line and provide the full path to your WHMCS installation. | ||
| + | <div class="source-cli">$whmcspath = /home/username/public_html/whmcs/;</div> | ||
| + | In this example, the server runs cPanel & WHM, the account username is <tt>username</tt>, and <tt>whmcs</tt> is the WHMCS installation directory. | ||
Latest revision as of 22:47, 6 December 2022
Refreshing a Directory
Refreshing directories can help to troubleshoot and resolve some errors. The example below refreshes the /modules/servers/ directory.
To do this:
- Download and unzip the WHMCS file set that matches the current version of your WHMCS. You can download current versions of WHMCS including Long Term support versions from WHMCS Downloads Page.
- Navigate to the directory to refresh /whmcs/modules/.
- Rename the unaltered ‘’’servers’’’ directory to contain the original name and the date. For example, servers_new_MM_DD_YYYY.
- Upload the unaltered directory to the parent directory within your WHMCS installation (in this example, the /modules/ directory).
- Rename the previous directory and include the date. For example,servers_old_MM_DD_YYYY.
- Revert the new directory name to the original name. For example, servers.
After you finish, check within WHMCS to ensure that refreshing the directory resolved your issue.
Restoring Customisations
After confirming that refreshing the directory has resolved your issue, you may need to restore any customisations.
To achieve this, you would need to copy the customisation from the ‘servers_old_MM_DD_YYYY directory to the now refreshed servers directory.
We recommend moving each customisation seperately and checking for errors within WHMCS in between each addition. This allows you to identify any problems by the specific module and allow you to choose whether to remove the customization or contact the third-party developer for help."
Cron Directory
Refreshing the cron directory may require additional steps, including updating your configuration in the config.php file.
To do this, use the instructions within the config.php file in the crons directory to uncomment the WHMCS path line and provide the full path to your WHMCS installation.
In this example, the server runs cPanel & WHM, the account username is username, and whmcs is the WHMCS installation directory.