At this moment both cms:out than cms:setNode resolve those links making them relative to the current page. I am not sure why we decided to create relative links instead of absolute ones,
The original reason was that you can export pages (html) and use the independently.
but I found several problems with this when using virtual uri mappings or error pages served by magnolia. When links are resolved in pages loaded with a URI that doesn't match the path of the node links are broken: for example if I put a link to the home page in a 404 page served by magnolia the link will be resolved from the location of the node of the 404 page, but the url in the browser refers to page originally requested and it will not work.
I see that point.
The question is: is there any reason why we should keep relative links? I found that absolute ones works fine for me in any situation, so I am not sure which is the pro of relative ones (and there are a few cons)...
I thing some already added there pros and cons to the thread.
changing that would be a matter of replacing LinkUtil.convertUUIDsToRelativeLinks with LinkUtil.convertUUIDsToAbsoluteLinks in Out and SetNode. I would be in favour of doing that, any thought?
I would like to make the link rendering configurable (like i18n, filters, ...). This gives the possibility to plug the link resolving you need.
I will work on the fckeditor-dms-link-thing the next days, so I will see what we would have to change to make that flexible.
Philipp Bracher
fabrizio ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
