[ 
http://jira.magnolia.info/browse/MAGNOLIA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690#action_15690
 ] 

Philipp Bracher commented on MAGNOLIA-2017:
-------------------------------------------

> 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.

After 3.5 you will be able to update your system stepwise in a safe way. So you 
would update 3.0.1 to 3.0.5 and then update to the latest 3.5 release. For 
doing bulk export/import we are planing to write a backup restore tool for the 
3.6 release.

If you export ensure that the formating flag is not set. You could try to 
replace the core jar only (with the 3.0.5) and then doing an export




> 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.0.1
>         Environment: Windows Server 2003, Tomcat, Mysql
>            Reporter: Claudio Greuter
>            Assignee: Grégory Joseph
>
> 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
----------------------------------------------------------------

Reply via email to