I am running Modx 2.6.5-pl on a Windows 2016 server.
I am trying to get a 2nd context running but when I call its url it loads up the start page defined in the default Web Context. I have Gateway Manager installed with http_host, site_start and site_url settings configured for both the web and my new context. In addition, I added a default_template in my context settings.
I have defined a new template to use on my new context along with new chunks and assigned them to the new pages in the new context. When I create new pages in the new context the new template is being assigned.
When I select view from the home page in the new context the content from the "Web" context displays with the URL assigned to the new context. When I select view on another page that I created in the new context I get a 404 error.
I also tried using ContextRouter and XRouting. ContextRouter gives me some errors when it tries to install. Neither made any difference. Currently they are uninstalled.
In chrome developer tools I am seeing this error:
Access to Font at '
http://myoriginaldomain.com/domain1/assets/fonts/my-font.ttf?cwmxip' from origin '
http://my2nddomain.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '
http://my2nddomain.com' is therefore not allowed access.
My modx install is set up with a shared html folder for all contexts but I have added a media set for each context to store that sites files. html/assets will be used for shared files.
Anyone have any ideas on how to fix this?