Field timestamp default can not be set to none.

Created on 25 August 2023, about 2 years ago

Problem/Motivation

If I create a field timestamp that mistakenly had a value set for default, it is not possible to change it to have no default because the seconds value which is locked causes the field setting to pick up a new timestamp that is the time of save of the settings

Steps to reproduce

Add a timestamp field to a content type, include a default
Save the configuration
Edit the field
Delete the date and time fields from the default
Notice the seconds is disabled which prevents deletion of the seconds
Save the config
Edit again and notice that you have new default that matches the time when you pressed save.

Proposed resolution

If date is blank, blank the times as well. Can't have a timestamp with no date.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

🐛 Bug report

Status

Active

Version

11.0 🔥

Component

Datetime →

Last updated 4 days ago

Maintained by
🇺🇸United States @jhedstrom
🇺🇸United States @mpdonadio

Created by

🇺🇸United States swirt Florida

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @swirt
Comment 4 days ago →
🇸🇪Sweden peter törnstrand
I could not reproduce this error with latest core 11.x and using the following browser:

Firefox 141.0.3 (Linux)

Web (The GNOME project) 48.4

Chromium 139.0.7258.138 (Linux)

To remove the default value of the timestamp field I could just uncheck the Set default value checkbox.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024