Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem
The timestamp field definition (TimestampItem) has the incorrect default widget specified which prevents forms from validating properly that use the field. The default widget specified is "datetime_default" but should be "datetime_timestamp". They both appear visually the same on the form, but the major difference is that "datetime_default" does not convert the date input into a unix timestamp value, so the range constraint that validates the proper timestamp value will always fail (because 2016-10-10T12:30:31 is not a proper number).
It can be resolved by simply re-saving the form display form, because the widget dropdown for the timestamp field has the proper "datetime_timestamp" value there and will save the proper widget value on this form submission.
The real resolution is to fix the field definition.
Steps to reproduce:
1. Add a "timestamp" field to an entity type, like the Article node type
2. Configure it with all defaults
3. Attempt to create an entity of that type, filling in a valid date.
4. Observe a form validation error "This value should be a valid number" (see screenshot)
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | wrong-timestamp-default-widget-2831885.patch | 675 bytes | bkosborne |
| Screen Shot 2016-11-30 at 1.51.55 PM.png | 58.08 KB | bkosborne |
Comments
Comment #2
bkosborneEDIT: Found the root cause and updated the issue summary
Comment #3
bkosborneComment #4
bkosborneHere's a patch w/o tests, don't have time for tests at the moment
Comment #5
bkosborneComment #13
kristen polThanks for the issue and patch. This is a duplicate of #2802663: Exceptions due ChangedItem, CreatedItem, and TimestampItem implicit dependencies on datetime module which was fixed in 8.3.x.