Requested behavior
-
Allow the import of an entry if the JSON rich text editor field in Contentstack is empty.
Use case
-
Depending on each client's needs, sometimes there is a value in this field than needs to be localized, but sometimes the field can be empty. If the JSON rich text editor is defined in a template, it cannot be set as non-localizable because of the use case just mentioned.
Current behavior
-
It is currently not possible to import an entry from Contenstack if the JSON rich text editor field is empty and set as localizable.
Available workaround
-
Change the field to non-localizable in Contentstack. In that case, Phrase will skip it and it should be possible to import the entry.
0 comments
Please sign in to leave a comment.