PHP7 Compatibility – Blacklist feature to save scan time
-
It would be handy to have a blacklist feature, and blacklist management.
It could work along the following concepts;
1) If a plugin is found either by scan or experience, to not be compatible with a PHP version, then it is added to the blacklist.
2) When a plugin is blacklisted, the plugin author/team is sent a message, and invited to bring the plugin up to compatibility.
3) The user that is doing the scan, can choose to override the use of blacklist reference for any/selected plugins, if they want to force a re-scan on their site.
4) When a scan is done, and the blacklist is not being bypassed, then a simple name (and version and error) check of the plugin is done, and if there is a match, then the plugin is flagged as “known incompatibility exists” (possibly with an indication of the severity of incompatibility).
5) When notified by the plugin author that the plugin is compatible, and this is verified, then the plugin can be removed from the black list, and added to the whitelist.
6) When a user decides to manually over-ride the blacklist, to scan a plugin anyway, and finds that the latest version has been made compatible (but the plugin author has not been part of the information loop), then the user can inform the blacklist. When verified as being compatible, the plugin can be added to the whitelist.
- The topic ‘PHP7 Compatibility – Blacklist feature to save scan time’ is closed to new replies.