Difference between revisions of "Legacy Module Removal"
From WHMCS Documentation
(Created page with "Old PHP code may introduce breakage on newer versions of PHP runtime. In order to protect your system from unexpected downtime, WHMCS 7.5 will attempt to delete any unused leg...") |
|||
| Line 1: | Line 1: | ||
Old PHP code may introduce breakage on newer versions of PHP runtime. In order to protect your system from unexpected downtime, WHMCS 7.5 will attempt to delete any unused legacy modules from your system. As it performs outdated module deletion, there may be three possible outcomes: | Old PHP code may introduce breakage on newer versions of PHP runtime. In order to protect your system from unexpected downtime, WHMCS 7.5 will attempt to delete any unused legacy modules from your system. As it performs outdated module deletion, there may be three possible outcomes: | ||
| − | # A legacy module is found to be unused and is successfully deleted. A log entry will be created. No email | + | # A legacy module is found to be unused and is successfully deleted. A log entry will be created. No email will be sent. |
| − | # A legacy module is found to be in use and is not attempted for deletion. A log entry will be created. An email message will be sent to notify system | + | # A legacy module is found to be in use and is not attempted for deletion. A log entry will be created. An email message will be sent to notify system administrators of this condition. The recommended action is to contact the module author and determine if there is an update available. |
| − | # A legacy module is found to be unused and | + | # A legacy module is found to be unused and deletion is attempted, but the deletion fails (e.g. due to insufficient permissions or a filesystem issue). A log entry will be created. An email message will be sent to notify system administrators of this condition. Since the module state may be inconsistent due to potentially partial deletion, it is recommended to investigate and finalize module removal manually. |
Revision as of 11:20, 2 March 2018
Old PHP code may introduce breakage on newer versions of PHP runtime. In order to protect your system from unexpected downtime, WHMCS 7.5 will attempt to delete any unused legacy modules from your system. As it performs outdated module deletion, there may be three possible outcomes:
- A legacy module is found to be unused and is successfully deleted. A log entry will be created. No email will be sent.
- A legacy module is found to be in use and is not attempted for deletion. A log entry will be created. An email message will be sent to notify system administrators of this condition. The recommended action is to contact the module author and determine if there is an update available.
- A legacy module is found to be unused and deletion is attempted, but the deletion fails (e.g. due to insufficient permissions or a filesystem issue). A log entry will be created. An email message will be sent to notify system administrators of this condition. Since the module state may be inconsistent due to potentially partial deletion, it is recommended to investigate and finalize module removal manually.