Fields saving twice #5
Description
What is the issue?
When creating a new field in a field section (on a matrix page, for example), a field can be saved twice, which will cause a 500 error because of the non-unique field name.
What are the steps to reproduce this issue?
- Create a new matrix as a page
- Create a new field of any type
- Save the changes, but do not navigate away
- Save the changes again; the console will display a 500 error.
What were you expecting to happen?
The interface should force all fields belonging to the same collection to be unique. The API should also return a validation error or automatically make the handle/name of the field unique.