Details
-
Task
-
Resolution: Fixed
-
Major
-
3.1 M1
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
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
Attachments
Issue Links
- is related to
-
MAGNOLIA-38 Subscriber URI mapping
-
- Closed
-
-
DOCU-42 Document new activation configuration
-
- Closed
-
-
MAGNOLIA-1592 Revive Subscriber class for 3.1 (deprecate it)
-
- Closed
-