Details
-
Bug
-
Resolution: Fixed
-
High
-
5.0.0-dev
-
None
Description
When using the public API, the position property of FieldDefinition shouldn't be required.
Currently, omitting it results in random position in admin interface, because all field types will have a 0 set in "ezcontentclass_attribute.placement".
The different use cases are:
- Adding field definition in the order in which they should appear in content type.
- Redefine the position of existing field definition.
- Insert a new field type at a specific position
Previous description:
Hi
I make a field type with ezstring (name) and ezkeyword fieldtype.
I then remove the class and make it again ( with the very same code). After the second time, the ezkeyword fieldtype is listed before ezstring in /class/view/17If you then use admin2 to edit the class, then they appear in the correct order
I am attaching the database
Attachments
There are no Sub-Tasks for this issue.