Issues when manager is used with a subdomain

[christianseel]

I'm using MODX 2.1.3-pl advanced and my manager has a folder above the web-context (website/frontend) folder.
The manager has the subdomain manager.mydomain.tld

1. Asides manager page is blank
   ressources are not found:
   GET http://manager.mydomain.tld/assets/components/asides/js/mgr/asides.js?v=213pl 404 (Not Found) GET http://manager.mydomain.tld/assets/components/tinymce/jscripts/tiny_mce/tiny_mce.js?v=213pl 404 (Not Found) GET http://manager.mydomain.tld/assets/components/tinymce/xconfig.js?v=213pl 404 (Not Found) GET http://manager.mydomain.tld/assets/components/tinymce/tiny.min.js?v=213pl 404 (Not Found) GET http://manager.mydomain.tld/assets/components/asides/js/mgr/Ext.ux.TinyMCE.min.js?v=213pl 404 (Not Found) GET http://manager.mydomain.tld/assets/components/asides/js/mgr/widgets/asides.grid.js?v=213pl 404 (Not Found) GET http://manager.mydomain.tld/assets/components/asides/js/mgr/widgets/home.panel.js?v=213pl 404 (Not Found) GET http://manager.mydomain.tld/assets/components/asides/js/mgr/sections/home.js?v=213pl 404 (Not Found) /?a=69:29 Uncaught ReferenceError: Asides is not defined

...it sould be http://mydomain.tld/assets/components/asides/...
This might be the site_url of the web-context?

2. I tried to fix this by making a mod_rewrite redirect to mydomain.tld/assets/...
   The manager page isn't blank any more, but I don't see any chunk.

[rtripault]

Hey Christian,

Thanks for reporting.
Are your other components working as expected ? Asides should be using assets_url… I'll dig into this asap

[christianseel]

Hi thanks for your quick reply!

Just figured out that similar issues exists with TinyMCE.

I found the asides.asset_url system setting and added the domain, files are found but
XMLHttpRequest cannot load http://mydomain.tld/assets/components/asides/connector.php. Origin http://manager.mydomain.tld is not allowed by Access-Control-Allow-Origin.

Well, this all seems to be more a MODX issue..., right?

[rtripault]

I can't confirm that… i'd better say that's an issue dealing about cross domain request…
One thing i've been doing while having the manager on its own subdomain or domain is doing symlinks, either in the system file (ln -s under *NIX systems) or Apache (i guess other httpd support that) aliases.

[Mark-H]

I've attempted moving just the manager to a different subdomain, but there's too many complications there with cross-domain requests to make that work properly.

One way is to actually move the entire installation to your subdomain, and using context settings to put the "web" (or a different context) on the main domain. That shouldn't give any issues like this..

[rtripault]

Mark,

That's indeed the best solution i've found so far. But i haven't explored really much possibilities/configs (was planning to get Jason bored with questions on that subject ^^).

Since modx.com should be using different contexts (and a custom manager path/url), there should be a "correct" way to handle that!

Anyway, thanks for passing by & commenting

[christianseel]

Thanks a lot Mark for your comment! I run into quiet a lot issues now, but thats a good solution!
Will try it now.

[hcanning2014]

Does this manager url issue persist in Modx Revo 2.3.2?
Revo manager doesnt work when used on a subdomain?
Thanks

[rtripault]

@hcanning2014 i've not been facing this issue, but i somehow changed the way on how i'm handling having the manager in a dedicated (sub)domain :

• assets_path moved to manager/assets/
• connectors_path moved to manager/connectors/

That's the most "compliant" way i've found so far.

Hope that helps.

[hcanning2014]

If I create a domain in WHM called sub.mydomain.com then the manager URLS are all off and the Articles extra wont display article listings.
mydomain.com works fine
...it's a pain. I hope they fix it so manager works in subdomains. ALWAYS something up.