-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
4.1
-
Linux, Tomcat
Problem
If a page contains a paragraph with an FCK editor a user can add links in the content to other pages of the website. If the user links to a non-activiated page in author and previews the content the FCKeditor paragraph is rendered fine. However, when the FCKeditor paragraph is activated to the public instance all internal links in the entire FCKeditor are corrupted.
Steps to Replicate
- In the author instance create three pages (template doesn't matter)
- Page1
- Page2
- Page3
- Activate pages 1 & 2
- Create a new page called sitemap (template doesn't matter)
- Ensure the sitemap page has a FCKEditor paragraph
- Edit the FCKeditor paragraph and add hyperlinks to page 1, 2, 3 (ensure you browse for the pages using the browse button)
- Preview the sitemap page and you will see the links showing up correctly
- Activate the sitemap page and check links in the public instance
Actual Result
- All links in the activated FCKEditor show up incorrectly
- For example:
- Link to Page1 shows up as http://mysite/${link:{uuid:
{a50db24b-862a-43f3-91e1-2fe48261c133}
,repository:
{website},handle:
{/Page1},nodeData:{},extension:
{html}}}
- Link to Page1 shows up as http://mysite/${link:{uuid:
{a50db24b-862a-43f3-91e1-2fe48261c133}
Expected Result
- FCKEditor should at least warn the author that they are linking to a non-activated page; and/or
- The FCKEditor paragraph in the public instance should render all links correctly regardless (better than breaking all links). This would mean vistors to the site are likely to get a 404 for the non-activated page links.
- But this is better than what currently happens
Acceptance criteria
- duplicates
-
MAGNOLIA-2865 Internal Page link in fckEdit: When the target of an internal link is removed, the fckEdit throws an error.
- Closed
- is superseded by
-
MAGNOLIA-2872 Further improve/consolidate Link api
- Closed