Uploaded image for project: 'Magnolia Standard Templating Kit (closed)'
  1. Magnolia Standard Templating Kit (closed)
  2. MGNLSTK-1382

For specific mappings the incorrent site definition is returned from ExtendedAggregationState

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 2.0.19
    • None
    • None
    • unchanged Magnolia Enterprise 4.5.18 bundle

    Description

      When setting the mapping of a site definition to specific values, the wrong site definition is saved and returned from ExtendedAggregationState

      F.e. consider the following setup:

      Site1 (mapping -> URIPrefix: /en handlePrefix: /site1 repository: website)
      Site2 (mapping -> URIPrefix: /en handlePrefix: /site2 repository: website)

      When opening:
      http://localhost:8080/magnoliaAuthor/en/site2.html
      the correct page is opened
      but the ExtendedAggregationState (f.e. state.getSite(), stkfn.site(), ...) returns Site1, and thus all site definition settings are loaded from the wrong site definition (theme, prototype, template availability, ...)

      This is a big problem when using the multiple tree strategy for multilanguage sites (http://documentation.magnolia-cms.com/display/DOCS45/Multilanguage+structure), which have the same domain, but different URIPrefixes.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              bvass Bence Vass
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: