Describe the bug
The bug occurs in the datetime widget. When a user does not explicitly click the now button to select the current date and time, the widget fails to automatically populate the field with the correct value. Instead, it inserts the placeholder text "{{now}}" as the literal value. This results in the datetime field displaying "{{now}}" rather than the actual date and time, which is likely unintended behavior.
To Reproduce
Go to the Decap CMS editor and add a content entry that includes a datetime widget.
In the datetime widget, ensure that the now button is available as an option.
Without clicking the now button, leave the datetime field untouched (assuming it should default to the current date and time).
Save the entry.
View the saved content or inspect the field value in the backend.
Expected behavior
The datetime field should automatically populate with the current date and time.
Actual behavior
The field displays the literal text “{{now}}” instead of the actual date and time.
Describe the bug The bug occurs in the datetime widget. When a user does not explicitly click the
now
button to select the current date and time, the widget fails to automatically populate the field with the correct value. Instead, it inserts the placeholder text"{{now}}"
as the literal value. This results in thedatetime
field displaying"{{now}}"
rather than the actual date and time, which is likely unintended behavior.To Reproduce
datetime
widget.datetime
widget, ensure that the now button is available as an option.Expected behavior The datetime field should automatically populate with the current date and time.
Actual behavior The field displays the literal text
“{{now}}”
instead of the actual date and time.Screenshots
Applicable Versions:
CMS configuration