Hi, by using Entity Tokens module I managed to make my forum paths like this
/forum/international-forum/electric-bikes/batteries/what-battery-is-good-for-a-bike
The tokens used to create this path are automatically populated from the corresponding title of every forum/taxonomy. What if I want to change what is shown by every token but keep a different title of the corresponding forum/taxonomy for human presentation? For example I may want in the International Forum the title to be "International Forum" but in the url alias to be just forum/international/ instead of forum/international-forum
If I mofify the taxonomy to be "International" instead of "International Forum" the path will be as wanted but then the presented title at the corresponding page will be "International" instead of "International Forum" so it will not be so nice.
Any suggestions? Could this unported module be of interest https://www.drupal.org/project/taxonomy_machine_name ?
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
Hi @yorkshirepudding! Nothing in admin/reports/fields or admin/config/development/configuration/single/export There is a field in the database though. Should I just copy the item...
Importing the staged config throws an error: another field with the same name already exists
That is not a core field so my guess is it must exist, though perhaps it is a field defined but without any instances. A few places to check: admin/reports/fields - is it...
Importing the staged config throws an error: another field with the same name already exists