Recently I found a problem in Magnolia which makes me very
frastrating. I am not sure if it's a bug in Magnolia, because you
never know when it will happen.
You know when editing content in FCKeditor, you can add link, by
clicking "Browse Server". This function is very good and very easy to
use for end user. But now I have problem with it.
On our web site, we have lots of users. They copy the same content
from one place, then modify it to meet their own requirement. Because
Magnolia always uses absolute link, so after copying, user has to
change the link to point their own one, not the original one, which is
not very good, but acceptable.
But, sometimes(not always), after you change the link, and save your
change, on the html page, the link still points to old place, not the
one you want!
I know Magnolia stores the link using uuid, so I had a look into
source code, especially had a look info.magnolia.cms.util.LinkUtil,
there are two functions: makeUUIDFromAbsolutePath and
makeAbsolutePathFromUUID, and I write a simple test code to use these
2 function.
String path1 = "/blah/blah/page1"; // new link
String path2 = "/haha/haha/haha/page2"; // old link
String uuid1 = LinkUtil.makeUUIDFromAbsolutePath(path1);
String uuid2 = LinkUtil.makeUUIDFromAbsolutePath(path2);
String path11 = LinkUtil.makeAbsolutePathFromUUID(uuid1);
String path22 = LinkUtil.makeAbsolutePathFromUUID(uuid2);
I expect path11 should be as same as path1, but what I get is: path11
is as same as path2, which explains why the link always points to old
one, not the new one.
BTW, I'm using Magnolia 2.1.5 with bdb as repositories.
Anyone here has the same problem? any clue?
Cheers,
Richard ([EMAIL PROTECTED])
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
