Enonic version: latest
When I do an export + import I expect the content to be exactly the same on the import side. This is not so in my experience.
Content created with lib content.create() does not export content with toolbox export, when display name contains diacritic characters. If content is successfully created it seems strange it can’t be successfully exported with toolbox export. If it can’t be exported it shouldn’t be legal content and not created. It will create inconsistencies, and if there is one thing we developers don’t like that much is inconsistencies. Content created must be allowed to be exported allways, you will create all sorts of problem if export don’t allow created content to be exported.
The export function provided is not at all reliable as of now and your user base should be adviced with a large warning box that the export function must not be used for backup if you have content created from libs and not from user interface.
In my use case I have 700 items created by content.create() but about 400 available in the export. Which is not so good when I need the backup to be restored from an export.