-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
-
Empty show more show less
-
4.5.14
The problem is, that the links don't get expanded if you request Magnolia via a domain which is not mapped to a sitedefinition.
To reproduce, follow these steps:
Case 1
- Visit http://demoauthor45.magnolia-cms.com/.magnolia/pages/adminCentral.html
- Verify that in the site definition of demo-project the domain mapping does not equal "demoauthor45.magnolia-cms.com"
- On the page /demo-project/about/subsection-articles/article edit a TextImage component and create an internal link to a page of the demo-project
- Click OK and save the dialog
- Reopen the dialog and edit the previously created link (notice that the prefixHandle got cut out)
- Click on "Browse Server"
Result: The tree is not expanded
Case 2
- Now verify that in the site definition of demo-project the domain mapping "demoauthor45.magnolia-cms.com" exists!
- Reopen the dialog, edit the link and click on "Browse Server"
Result: The tree is expanded, but only if you link to pages of the current website (crossdomain links don't expand the tree)
Can't we just always save the link as absolute URIs without cutting out the handlePrefix like it is done when you select a document from dms instead of a page from website tree?
Chris
- is cloned by
-
MULTISITE-9 CLONE - fckEditor: repository browser doesn't expand to linked node if working on multiple sites from one base domain
- Closed
- is related to
-
MGNLUI-2450 fckEditor: repository browser doesn't expand to linked node at all
- Closed
- relates to
-
MAGNOLIA-5250 fckEditor: make repository browser site aware
- Closed