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?
GitHub Issue #:
2508
Recent comments
I use Lando (a wrapper for docker) and find settings changes happen straight away
How often is the settings.php loaded.
You might need to add a Relationship in the View to Flags. Or there might be a setting on the content type. I can't recall for certain but I think it's possible.
No Flag fields in Views
Try using caching in the View settings, set to 24 hours. This should work for anonymous site visitors.
View to show a different node each day