[MGNLSTK-256] Links should be relative to site-root Created: 17/Jan/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Boris Kraft Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

If I copy a complete site (-tree), some links still link to the original site. For instance the sitemap link will point to the original site after I have created a copy.

I think that links within a site should be relative to the site root. This way, if I copy a site, I do not accidentally end up in the wrong place if I follow a link.



 Comments   
Comment by Magnolia International [ 18/Jan/09 ]

Links being UUIDs, this will be trickier than it sounds.

Comment by Philipp Bracher [ 21/Jan/09 ]

This is a common magnolia issues and indeed very annoying. There is nothing we can do in STK

Comment by Boris Kraft [ 22/Jan/09 ]

As a workaround, it would probably work to export and import a tree (with "create new UUIDs" selected) instead of copying it. If that works and is documented, it would be a good start.

UPDATE: just tested this, this doesn't work. The links will still point to the original pages. I assume that only the UUIDs of the imported objects are recreated but the "data" is not touched.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 07:25:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.