Legacy Module Removal

From WHMCS Documentation

Revision as of 19:31, 1 March 2018 by Nate (talk | contribs) (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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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:

  1. A legacy module is found to be unused and is successfully deleted. A log entry will be created. No email is being sent.
  2. 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 administrator of this condition. Recommended action is to consider replacing the modules referenced in that message.
  3. A legacy module is found to be unused and tried for deletion, but the deletion fails (e.g. for insufficient permissions or a filesystem issue). A log entry will be created. An email message will be sent to notify system administrator of this condition. Since the module state may be inconsistent due to potentially partial deletion, it is recommended to investigate and resolve the issue and finalize module removal.