I think most non-developer users are pretty perplexed when faced with the Date choices presented to them while adding a date field to a content type.
I am not sure what would be the best way to address this issue, but here are my thoughts so far.
- There is a need for a short description somewhere near where the user has to make this choice and due to the complexity of the Date formats possibly also a link to more detailed documentation.
- There is not enough space on the
Manage Fieldspage at/admin/structure/types/manage/foo/fieldsfor brief explanation or even a link.
One option could be to present the user only with one choice and then allow them to select one of the Date formats on the Field Settings page where there is more space to provide some brief description next to each Date type with a link to more detailed explanation.
Can anyone think of a better (easier or more user friendly) way to present this choice to the user?
Recent comments
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists