Allow editing term machine names (a.k.a. Taxonomy Machine Name module in core)

There is currently no way in core to allow editing a term machine name via the admin UI. In Drupal, Taxonomy Machine Name module solves this problem:

Is this something that 80% could use, or does this belong in contrib?

That module claims integration with Views/Token/Pathauto, all of which are in Backdrop core. So does it make sense to have such a feature in core?

GitHub Link:

https://github.com/backdrop/backdrop-issues/issues/3093

GitHub Issue #:

3093

Log in or register to post comments

Recent topics

Importing the staged config throws an error: another field with the same name already exists

Posted 4 days 9 hours ago by Francis Greaves (themetman) in How-To and Troubleshooting

Comments Enhanced

Posted 1 week 6 days ago by (izmeez) in How-To and Troubleshooting

Why not add a Github star?

Posted 2 weeks 7 hours ago by (izmeez) in How-To and Troubleshooting

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...

Posted 4 days 3 hours ago by Francis Greaves (themetman) on:

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

Posted 4 days 9 hours ago by Francis Greaves (themetman) on:

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....

Posted 4 days 9 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:

Importing the staged config throws an error: another field with the same name already exists