Let me explain this rather frustrating and strange workflow that leads to an issue I have not figured out how to work around yet.
- Create a collection (FakeCollection), create a taxonomy (FakeThings), create a blueprint for FakeCollection (FakeBlueprint).
- Configure FakeThings to be linked to the FakeCollection. This adds FakeThings to the blueprint for FakeCollection.
- I want this taxonomy item max items to be 1, so I set the max items to 1. Now, I also don't want the linked taxonomy item to be called FakeThings, since there is only one. I rename FakeThings and it's handle to "FakeThing".
- Save, and refresh the page. There are now two fields in the blueprint: FakeThing and FakeThings.
Is this the expected behaviour? I don't see a way to delete the FakeThings linked item.