|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #77733 IntlDateFormatter parsing incorrectly
Submitted: 2019-03-13 09:00 UTC Modified: 2021-04-06 18:54 UTC
Avg. Score:5.0 ± 0.0
Reproduced:2 of 2 (100.0%)
Same Version:0 (0.0%)
Same OS:1 (50.0%)
From: shariefjamiel at gmail dot com Assigned:
Status: Open Package: I18N and L10N related
PHP Version: 7.2.16 OS: ubuntu 18.04 - php 7.2.15
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: shariefjamiel at gmail dot com
New email:
PHP Version: OS:


 [2019-03-13 09:00 UTC] shariefjamiel at gmail dot com
From manual page:
Passing a totally wrong datetime format returns a valid but strange datetime despite the date formats being so different.

e.g. 2019-12-10 10:10:00 becomes 2016-06-10 09:10:00

If the date format is wrong to start with, should it not return null?

Test script:
use IntlDateFormatter;
$formatter = new IntlDateFormatter('en_GB', 3, 3, 'Europe/London', 0, null);
$date = '2019-12-10 10:10:00';
echo date('Y-m-d H:i:s', $formatter->parse($date));

Expected result:

Actual result:
2016-06-10 09:10:00


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2019-03-13 09:49 UTC]
-Type: Documentation Problem +Type: Bug
 [2019-05-22 10:45 UTC] andorsarig at yahoo dot com
Experienced a similar problem.

For example:
- with 'en_US' locale the function returns false.
- with 'de_DE' returns a timestamp which points with 8 years and a few months later.
 [2021-04-06 18:54 UTC]
-Package: Date/time related +Package: I18N and L10N related
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Thu Dec 08 13:05:53 2022 UTC