Response Time
24 — 48 hours
Version: 3.9.22295
On upgrade to version 3.9.22295, a bug was reintroduced that causes a '?' character to be appended to the end of blog archive URLs. This causes a date parse error when a user attempts to navigate to that URL using some browsers (Safari and Firefox tested).
URL (generated by the archive index mod, all URLs contain the '?'):
http://dbdesignsnc.com/home-design-tips/archive/calendar/2014/01?
Error:
DATETIME::__CONSTRUCT(): FAILED TO PARSE TIME STRING (2014-01?-01) AT POSITION 7 (?): UNEXPECTED CHARACTER
This same issue was documented in an earlier version here:
http://stackideas.com/forums/datetime-__construct-datetime-construct-failed-to-parse-time-string-2014-05-01-at-position-7-unexpected-character
Please provide a patch that I may apply in comments. Other users will likely want to see this patch as well (unlike in previous forum post) so please post openly.
Regards,
chrissy
On upgrade to version 3.9.22295, a bug was reintroduced that causes a '?' character to be appended to the end of blog archive URLs. This causes a date parse error when a user attempts to navigate to that URL using some browsers (Safari and Firefox tested).
URL (generated by the archive index mod, all URLs contain the '?'):
http://dbdesignsnc.com/home-design-tips/archive/calendar/2014/01?
Error:
DATETIME::__CONSTRUCT(): FAILED TO PARSE TIME STRING (2014-01?-01) AT POSITION 7 (?): UNEXPECTED CHARACTER
This same issue was documented in an earlier version here:
http://stackideas.com/forums/datetime-__construct-datetime-construct-failed-to-parse-time-string-2014-05-01-at-position-7-unexpected-character
Please provide a patch that I may apply in comments. Other users will likely want to see this patch as well (unlike in previous forum post) so please post openly.
Regards,
chrissy
7 Replies
The replies under this section are restricted to logged in users or users with an active subscription with us
