The Backdrop forum is a website where everyone can come and chat about Backdrop.
You have questions, we have answers! You have answers, we have questions! Don't have questions or answers? It doesn't matter, we all have ideas! Let's share them, and together we'll make the world of Backdrop a better place.
If you respond to a question, please adhere to the following guidelines regarding transparency:
- If you copy guidance from somewhere else such as an AI service, a Drupal resource or another web development resource, please state where you got it from and if applicable link to the original resource.
- If you offer a solution, please indicate whether or not you have tested it and the extent of your testing in relation to the original posters question.
Also, please see our code of conduct.
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