Feature Requests
Share ideas, discuss and vote on requests from other users in community
 

Add to the System Health Status an alert for modules that are not longer part of WHMCS

ramf shared this idea 1 year ago
Completed

Hi,

Can you please add to the System Health Status an alert for modules that are not longer part of WHMCS and users should consider removing them?

Recently I upgraded to PHP 7.

After the upgrade I had several problems that where solved by removing some old modules that once where part of WHMCS (not manually added modules - I'm talking about modules that came with the WHMCS core system installation) but where removed along the way by WHMCS.

There is a note in the release notes when WHMCS decide to remove such a module - But nothing is actually removed from your local system - so there is a chance that you missed such a notice in the release notes and you still have old unsupported and maybe with security vulnerability module installed on your own WHMCS installation.

I think that such an old module can be dangerous and thus should be added to the System Health Status as a Warnings or even as Needing Attention alert.

Thanks!

Ram

Comments (6)

photo
1

Hi,

Another issue related to this feature request - Please add a note for such a modules that are not longer part of WHMCS - with the relevant information on how to remove the old module (what files should be deleted etc.).

Thanks!

Ram

photo
1

Hi,

Thanks for this suggestion. In version 7.5 we are introducing the ability for the updater to check for discontinued official modules which are no longer in use, and to remove them during the update to 7.5.

We feel 7.5 is the right time to introduce this, due to the increased Ioncube requirements and added support for new PHP versions means the presence of historic code could cause errors in new environments.

If a discontinued module is activated it will not be considered for removal.

Any removals will be logged to the Activity Log. Any errors in the deletion will also be logged and emailed to full administrators.

photo
1

Hi,

Thanks!

The problem is that we don't use the automatic updater utility.

We tried it several times but every time we had problems - during the last time even part of the DB got lost.

We are using the old FTP upload way - and it's working great.

The question is - how can we have this tool (check for discontinued official modules which are no longer in use, and to remove them ) not during an automatic update process but rather as a stand alone module?

Or maybe something that being done via the daily cron job or something like that?

Please take under consideration that some of your users are not using the automatic update option - but still need a way to check for discontinued official modules which are no longer in use, and to remove them.

Thanks!

Ram

photo
1

The code introduced in 7.5.x series will do this check during the update process done via the automatic updater or when running through the install/ folder update process after a manual FTP of files.

photo
1

Grate - thanks!

photo
photo
1

Also

  1. If a discontinued module is activated it will not be considered for removal

Please add to the relevant log this information also - so even if such a module will not get removed, we need a way to know there is a problem with it.

By the way,

I'm not sure the Activity Log is the right place to store such information - we usually don't look there (unless there is a problem) - adding this information to the System Health Status is much more logical and visible to admins - not only after an update.

Please do consider adding the relevant alerts of old modules that where not removed from WHMC during the update to the System Health Status.

Thanks again,

Ram