[
http://jira.magnolia.info/browse/MAGNOLIA-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394#action_17394
]
Jan Haderka commented on MAGNOLIA-1095:
---------------------------------------
Not reproducible with 3.6.1 ... the content of NodeData value is actually
base64 encoded for export when containing characters that could break xml.
> ASCII Backspace Character Breaks XML Export
> -------------------------------------------
>
> Key: MAGNOLIA-1095
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1095
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 3.0 RC2
> Environment: Redhat Enterprise, BDB PM
> Reporter: Sean McMains
> Assignee: Philipp Bracher
> Priority: Critical
> Attachments: exampleBadSource.txt
>
>
> One of our content editors pasted text into an FCK Editor field from another
> source. Among the content was a backspace character (ASCII 8, or CTRL-H).
> While Magnolia could save and edit this page without difficulty, Jackrabbit
> was unable to render that into XML, which broke publishing, backups, export,
> etc. for that page. We were eventually able to fix the problem by using the
> JCR browser to copy the data into a text editor, have it zap the
> non-displayable characters, and then paste the result back into the
> repository.
> To solve this issue, I'd suggest that stripping non-printable characters from
> String values (or at least for the FCK Editor controls) before persisting
> them to the repository might be a good approach.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
