[MGNLETK-51] AdminCentral generates incorrect link to site when the site root node is no direct child of website repository root Created: 02/Feb/11  Updated: 23/Aug/11  Resolved: 23/Aug/11

Status: Closed
Project: Extended Templating Kit (closed)
Component/s: multisite
Affects Version/s: 1.4.1
Fix Version/s: 1.4.3

Type: Bug Priority: Major
Reporter: Nils Breunese Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: vpro
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File config.modules.extended-templating-kit.config.sites.pip-test1.xml     XML File website.pip.xml    
Issue Links:
causality
relation
is related to MGNLETK-52 Site definition with empty handlePref... Closed
is related to MGNLETK-53 AdminCentral generates incorrect link... Closed
supersession
supersedes MGNLETK-62 multisite detection: implement a rule... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

We no longer want all site root nodes on one level, as we get too many sites. We want to group them, so site root nodes are no longer direct children of the repository root.

But if the site root node is not a child of the website repository root, then you need a link like:
/[site def name]/[urlPrefix or path to site].html,
but admin central creates link:
/[url prefix or path to page].html

so sites don't open correctly from admin central.

Site definition and website tree attached.



 Comments   
Comment by Philipp Bärfuss [ 11/Feb/11 ]

Thanks for the report, this should actually work.

Comment by Raphael Joss [ 09/Aug/11 ]

Any updates on this issue? As I understood this bug is accepted and should be fixed?

Comment by Jan Haderka [ 12/Aug/11 ]

Hi Raphael,

this issue is still scheduled for the next ETK release. It is accepted and will be fixed.

Regards,
Jan

Comment by Philipp Bärfuss [ 23/Aug/11 ]

Will finally be solved by a new algorithm (MGNLETK-62).

Comment by Philipp Bärfuss [ 23/Aug/11 ]

fixed by implementing MGNLETK-62

Comment by Jan Haderka [ 23/Aug/11 ]

Pls next time mention all the tickets that are fixed in the commit message.

Generated at Mon Feb 12 01:48:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.