[
http://jira.magnolia.info/browse/MAGNOLIA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15671#action_15671
]
Claudio Greuter commented on MAGNOLIA-2017:
-------------------------------------------
yes, you're right, the import were coming from 3.0.1.
The reason for the export/importing procedure is simple: The mailing list
stated that an update would be possible from 3.0.5 or so, so i assumed that
older versions are not compatible without exporting. i could not find a clear
migration path or data-backwards-compatibility, so i thought i go for the
"safe" approach (this was also suggested by the mailing list).
I think it would be a great feature for magnolia to provide some sort of
migration-path for each version, so one knows what to do when updating from a
specific version. i guess this would boost the popularity of magnolia even
more, since the migrations using import/export require quiote a lot of work and
time.
as for your request to test the export with 3.5.2: i'll do this today and will
provide the information here.
many thanks for your reply,
Claudio
> additional Line Breaks after XML Import/Export
> ----------------------------------------------
>
> Key: MAGNOLIA-2017
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2017
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 3.5.2
> Environment: Windows Server 2003, Tomcat, Mysql
> Reporter: Claudio Greuter
> Assignee: Boris Kraft
>
> during a Migration from magnolia ce 3.0 to magnolia ce 3.5.2 we exported our
> sites to XML and imported them on the target system.
> after this, the pages containing longer text were completely messed up with
> random, additional line breaks. i worked around this issue by removing all
> line breaks from the XML files manually (using a search and replace), however
> this is a hack and i am worried about side effects.
> It seems as if the export tries to format the XML in a readable way,
> resulting in these line breaks. i tried the "format XML" switch, however the
> results were the same.
> I am aware that a similar bug has been reported quie a while ago, however
> this issue is marked as resolved, so i guess it was reintriduced somehow.
> Let me know if i can help with more details.
--
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/docs/en/editor/stayupdated.html
----------------------------------------------------------------
