It's even worse than I thought then, if it affects every backup- restore cycle. I can tell that my paragraphs (pasted from word in fck) CANNOT be "reconverted" by saving again the paragraph. I don't want to be too critical, because magnolia CE is an open source tool, and a very promising one, but a CMS that cannot be saved and restored, and in the case of magnolia CE, that cannot be updated, is not ready for production.

JPM

Le 26 avr. 07 à 19:32, Sebastian Frick a écrit :

I remember this issue has already been reported in JIRA. Usually you can "re-convert" those richtext-fields by clicking the responsible dialog and save the data again. I don't think this behaviour isn't caused by a different tomcat-version. Nevertheless this issue is a big blocker for me...

Sebastian

Maintaining a site with magnolia proves to be a real nightmare.
The bugs in 3.0.1 forced me to update to 3.0.2.
I also downgraded from Tomcat 5.5.17 to 5.0.28, because of some issues with table paragraphs, and because 5.0.28 is the version magnolia ships with.
I exported everything and imported it back.
Most of the pages have problems now: line breaks appearing randomly, tables created with fck editor which confuse content and html, and so on...

What a mess!
Am I the only one to experience this?
At least we should be warned that one should not export and import to magnolia instances running on a different version of tomcat...
What's the point with exporting to xml if everything gets scrumbled?

JPM

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------



----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------



----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------

Reply via email to