Description of the need
This is a formal request to have Token Filter added to core as a text format filter.
Both Drupal and Wordpress work on a token system in the backend, however Drupal nor Backdrop make it easy to expose the tokens to the front-end out of the box. Wordpress (from my understanding) does expose their tokens to the frontend without any additional plugins to accomplish it.
Proposed solution
Token Filter is one of my go-to modules that needs installed, just to be able to use the date token for a website copyright. It is rare that I use tokens in other places on sites (depending on the site), however the fact that none of the tokens are exposed to the frontend without a contrib to accomplish it, makes it difficult for new users to know that tokens exist.
Alternatives that have been considered
The only current alternative is to use contrib.
Another alternative is to expose a small, pre-defined set of tokens instead of all tokens. Contrib could be used to expose any additional tokens that aren't exposed by core.
Is there a Drupal or Backdrop contributed module that accomplishes this?
https://github.com/backdrop-contrib/token_filter
Additional information
I'm not big on bloating core, however this is one aspect of Drupal (and now Backdrop) that I have always pondered: "Why do tokens exist in core if core doesn't do anything to easily expose them?" I'm all for tokens being a part of core, but I'm also all for the ability to use the tokens through core.
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