View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0019767||phpList 3 application||General||public||14-02-19 08:01||15-02-19 08:55|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0019767: Fatal error: Your phpList version is older than two years|
|Description||Reported by v3.3.1 users: https://discuss.phplist.org/t/fatal-error-your-phplist-version-is-older-than-two-years/4970|
|Tags||No tags attached.|
||I think asking to upgrade once every two years is not too much. The main reason to keep this check in is to avoid abandoned installations polluting the internet.|
So far as I can see release 3.3.1 is the last release that actually defined the RELEASEDATE constant in init.php. Now the age check isn't now being done because the constant isn't defined.
Presumably there was a build step that inserts that line, which now isn't being run.
@duncanc That's right.
The release date could be taken from the download server (automatic updates) or reinserted into the build process.
It would be good if an automated warning about old releases expiring could be generated, so that admins are warned at least one month in advance.
As for how the fatal error: more information and links in the error, as a minimum, would be an improvement.