Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-1546

Subscribers with custom contexts are not properly mapped

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Major
    • 3.5 RC1
    • 3.1 M1
    • None
    • None

    Description

      If using single Magnolia Author instance to manage 2 or more websites (with multiple subscribers), setting custom contexts does not create proper mapping
      Scenario:

      single author instance has 2 websites (internet and intranet) each starting from single folder under root:

      /www-mycompany-org
      ---/www-index
      ---/www-page1
      /home-mycompany-org
      ---home-index
      ---home-page1

      Each site then has 2 subscribers (for redundancy) whose website context subscribedURI has been set to filter out top folders.

      Problem #1:
      You cannot activate pages under top folders unless the top folder has been activated itself. Why the filter then?

      Problem #2:
      The desired effect is to have public instance behave as it is managed by single author so that for www subscriber the folder /www-mycompany-org should map to / and so on.
      For the case above if my author host is cms.mycompany.org and public host is www.mycompany.org then the index page will have URLs:

      on author: cms.mycompany.org/www-mycompany-org/www-index.html
      on public: www.mycompany.org/www-index.html

      Otherwise what would be the point of managing multiple sites with the same author?

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                scharles Sameer Charles
                zambak zam6ak
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR