Just opening this issue for any agenda items for the dev meeting this week.
---------
Olaf asked that we put this item on the agenda for the dev meeting today.
https://github.com/backdrop/backdrop-issues/issues/5138
"Hey everybody, I'd like to suggest a topic for today's meeting, an issue introduced in the last release: https://github.com/backdrop/backdrop-issues/issues/5138. I've lined out two approaches to fix the issue and I'm looking forward to more feedback. Thanks in advance!"
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