Hello,
I'm working on upgrading our build to use Magnolia 4.3.1 and ETK 1.3 (we're currently on Magnolia 4.2.3 and ETK 1.2.3), since we want to make use of the new enterprise multi-site support. After modifying our site definitions by adding the new domains and mappings nodes and changing the i18n node to the new structure, I've run into a problem. Right now we have a single URL (subdomain) where all our editors for all sites can reach AdminCentral. This subdomain is of course not in any site's domains mapping, and this causes problems when opening a site on the author instance, because Magnolia falls back to the default site definition (and thus the theme of the default site definition) when it cannot find the current domain in any site definition domains mapping. Does this really mean we need to create separate AdminCentral subdomains for every site definition and that our editors need to use the right AdminCentral subdomain or they can't properly view the site they want to edit? Or am I missing something? Nils Breunese. De informatie vervat in deze e-mail en meegezonden bijlagen is uitsluitend bedoeld voor gebruik door de geadresseerde en kan vertrouwelijke informatie bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van deze informatie aan derden is voorbehouden aan geadresseerde. De VPRO staat niet in voor de juiste en volledige overbrenging van de inhoud van een verzonden e-mail, noch voor tijdige ontvangst daarvan. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
