[
http://jira.jboss.com/jira/browse/JBPORTAL-1929?page=all ]
Sohil Shah resolved JBPORTAL-1929.
----------------------------------
Resolution: Done
The CMS is now displayed via the "cms content type" via the Content Framework
instead of the old way of "portlet type".
This new/flexible approach does not warrant the need to modify relative URLS into the form
/portal/content before storing them
/portal/content was rigid in the first place since it ended up landing on the default page
of the default portal even though the link would have been clicked from some other portal
page
Relative links in CMS content munged by WYSIWYG editor
------------------------------------------------------
Key: JBPORTAL-1929
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1929
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.4 Final
Reporter: Martin Putz
Assigned To: Sohil Shah
Fix For: 2.6.6 Final
Relative links defined in CMS content are munged by the WYSIWYG editor, which results in
incorrect links if multiple CMS instances are used on different portals.
For instance, the default content has a link from 'default/index.html' to
'default/support.html'. In the original file
jboss-portal.sar/portal-cms.sar/portal/cms/conf/default-content/default/index.html, this
link is defined as
<a href="default/support.html">Explore</a>
This is fine, as it works correctly, even if I have a second CMS instance on another
portal.
As soon as I open the file in the CMS admin portlet, however, this link is changed to
<a href="/portal/content/default/support.html">Explore</a>
which is problematic, as it always opens up this CMS content inside the default portal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira