Hi folks,
We recently moved our installation from Magnolia 3.0.5 to 3.5.4. We thought
we had all of our issues ironed out, but came across a vexing one today:
When there's a Rich Editor paragraph that was created in 3.0.x, images are
stored using a relative path from the current page. In the JCR browser, the
rich editor paragraph will include something like this:
<img src="rich/contentParagraph/0/content_files/file/Picture 2.png" />
Version 3.5 of Magnolia uses the more robust UUID pattern for storing
images, so we end up with something like this instead:
<img
src="${link:{uuid:{74850946-11b2-402b-82c8-012a9be242ea},repository:{website
},handle:{/testing-site-destroyer/paragraph-examples/rich/contentParagraph/0
6/content_files},nodeData:{file},extension:{gif}}}" />
Now, the old content still works fine for display purposes in 3.5.4.
However, when one goes to edit the Rich Editor paragraph, the relative paths
are broken, since the dialog isn't rooted at the same place that the web
page is. As a result, the images show up as broken in the FCK Editor. This
is, understandably, causing our site editors some concern.
So, is there some upgrade step that we missed that will fix these up? It
seems like a bug to me, but I wouldn't have expected us to be the first
people to run across it if so. (I didn't see anything in Jira that seemed to
correspond to this.)
Thanks for any info,
Sean
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
