Recently I wanted to display the current date in a Views block, so that a visitor looking at the block at the 5th of July would read something like "July 5, 2018".
The use case is an academic online article with a block indicating "how to cite" that article. Here's a real world example (see the "view date" at the end):
How to cite Mani, Inderjeet: "Computational Narratology". In: Hühn, Peter et al. (eds.): the living handbook of narratology. Hamburg: Hamburg University. URL = http://www.lhn.uni-hamburg.de/article/computational-narratology [view date: 5 Jul 2018].
I was surprised to not find a 'current date' field in Views but hoped then to get the current date with a token like [current-date:medium] in the "Global: custom text" field, but that's not the case: the custom text field doesn't support tokens.
So, I suggest to support general (e.g. 'Current date' and 'Site information') tokens in the Views "Global: custom text" field. I'm sure they would be helpful in various use cases, not only the one described above.
I think it's important to provide such values via the Views UI. Particularly because (afaik) there is no Views PHP module (and probably won't be) for Backdrop. Other implementations (like a custom Views field template) have several disadvantages, for instance the need to localize dates in PHP on non English sites even if dates have already been localized in Backdrop.
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