Details
-
Bug
-
Resolution: Unresolved
-
High
-
None
-
1.8.1
-
None
Description
Stumbled across some issues while doing an import via kaliop migration bundle.
The import completed without errors and beside other things a content type and 2 content objects based on the new Type have been created.
So far so good.
First issue popped up when I tried to manually add another field to the content type. Got some form validation error in the backend.
The problem was, that we created fields where the identifier contained dashes instead of underscores, however the fields where saved with their values when creating the content objects (with migration bundle).
So I excpect that a) the api rejects to create those field identifier if there are invalid entries or b) the form validation does not throw errors on valid fieldidentifier
Next Problem was that the content objects where not editable in backend, throwing yui errors on opening.
Here was the problem that we created categories within the fieldtype.
One of those contained white-spaces "Social Media", which caused those yui errors.
So I excpect that a) the api rejects to create those categories if there are invalid entries or b) yui does not throw errors on valid categories
<code>
-
type: eztext
name: Facebook
identifier: facebook
description: Facebookseite
required: false
searchable: false
translatable: false
category: Socal Media
</code>