NOTE:: Before reporting an issue, make sure you are running the latest version, currently 3.3.1
|Anonymous | Login | Signup for a new account||26-03-17 06:29 BST|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0015671||phplist application||User Management||public||30-01-12 18:53||23-05-12 02:00|
|Target Version||4.0.x||Fixed in Version||2.11.7|
|Summary||0015671: Function parseDate() does not allow valid dates|
|Description||There are some serious errors in the function parseDate() in file admin/connect.php.|
It refers to a non-existant variable $value that means the only allowed date format is dd-mm-yyyy.
Additionally the processing for the date format yyyy-mm-dd uses incorrect regex matches (it should be matches 2,3,1 not 3,1,1).
This is actually in version 2.10.17, but the drop down list for Product Version does not include that.
See attached file for a corrected version of the function.
|Tags||No tags attached.|
|Attached Files||parseDate.php [^] (866 bytes) 30-01-12 18:53|
marking it for 2.11, unless you think it's breaking something crucial in 2.10, in which case it can go there.
Well, it is stopping the import of date fields in YYYY-MM-DD format, which is probably the most common date format people use. That sounds like a serious break to me. As I have provided a fix I think that it should go into the next release, 2.10.18.
In general, shouldn't fixes be applied to the next release? If not, then that's a discouragement to people reporting problems.
|applied to trunk as well as 2.10 branch|
|Copyright © 2000 - 2017 MantisBT Team|