-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't let the lineage.childsites vocabulary fail, if there are multip…
…le childsites with the same id.
- Loading branch information
Showing
3 changed files
with
22 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c091f96
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
childsites with the same id can only occure in setups where childsites are located in different subfolders of the main portal. eg:
this "fix" basically makes content from both sides be labeled with "Super Subsite", even if it's from folder2/subsite1.
a real fix for this problem would be to change the way the index is computed to use the portal-relative-path instead of the plain id.
this would require an upgrade step to update existing catalog data, too.
i'd prefer to go for the real fix, although i currently have no resources to implement it.
if we do a release containing this workaround, i'd at least log an error message ("lineage.index does not support subsites with the same id - see ticket xxx") when a brain gets skipped while building the vocabulary. the version number would be 0.4.1 rather than 0.5
c091f96
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i agree. currently the vocab is only used for the subsite switcher viewlet.
but however, i won't make a release yet and postpone the real fix until time has come.