I'm experiencing a realy strange problem.
I'm not a developer but I really know drupal.
I've a field collection that own a date iso field. Collect end date not mandatory.
This field collection is attached to two different Entity Registration Type.
In one of those two when I save the first time the entity the date dispalyed is current date while the real value stored in the database is something else. Example I save 02-02-2017 11:44 but I see the current date(now and it refresh every time i go to the entity page). This happen also in Views.
If I go to edit field collection i see the right value, and If I save withouth editing the date then I can see the right value also in entity page and views. Checking the Db entry with phpmyadmin I see (field_start_value) 2017-02-02 11:44 and (field_endt_value) NULL, after updating I see (field_start_value) 2017-02-02T11:44:00 (field_endt_value) 2017-02-02T11:44:00
On the other Entity Registration Type everything goes well.
What can I do?


arzuga created an issue.

Irbis’s picture

Same issue. Can anybody help?

Drupal 7.53
Date 7.x-2.9
Views 7.x-3.14

It work as expected only after I edit/save node.

God Of Atheism’s picture

I can confirm this issue. For me it appears in a date (ISO format) field.

When setting the display to date the date is displayed as the current date. When setting the display to plain, it does not. However, after applying the patch in comment #26 in issue Manage Display Format Settings won't save when using the "plain" formatter, the issue also pops up when setting the display to plain. When reverting to the pre-patch code, plain again displays the correct date.

vitalie’s picture

I had a similar issue, some dates being correct, some wrongly displayed the current date. I noticed that in the database the wrong cases lacked the time part of the date string, so no T00:00:00.

When I added that, it fixed the issue.

jlbrewster’s picture

(Drupal 8) If you use the field formatter widgets instead of Twig date filters, you will have better luck. (You will find these both in your content type and your view configuration). You can choose "custom" and have Drupal output the correct date format for you (much the same way you would have done it in Twig).