We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 19302
    • 6 Posts
    Hey all,

    Have just set up a fresh install (2.1.1pl). Made three seperate contexts, set the context permissions to mirror the default web context - and added the correct system settings to each context (http_host, site_start, site_url).

    Hosting is set to accept three urls as aliases (domain1.com, domain2.com, domain3.com) and am using the multiple gateway plugin :

    switch ($modx->getOption('http_host')) {
       case 'www.domain1.com':
          $modx->switchContext('domain1');
          break;
    etc...
    


    Have made all the site_start pages, and this is all working from the front end correctly. I’m using the following code for the .htaccess :

       RewriteCond %{HTTP_HOST} !^www\.* [NC]
       RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
    


    Which keeps the domain intact - and rewrites them to www.

    Prior to 2.1.1 (2.0.8) I could login from any one of these domains and use the manager. However, now whenever I try in 2.1.1, I get an access denied to resources once logged in. If I turn off the gateway plugin, the problem goes away (and can use the manager fine - can assume settings and permissions are fine).

    So, is it still possible to login to the manager when $modx->switchContext(’domain1’) has been fired? Or are we now only able to login to the manager when the default web context is active. It seems
    like a bug, but heck, every time I’ve used contexts since Revo has come out, I’ve had a lot of issues, so just wanted to check if this was an intended change or a bug.