Open modxbot opened 12 years ago
markh submitted:
A blocker priority means that it's impossible to use the product in general usage.. this is not a blocker.
markh submitted:
I'm wondering if running the manager on a subdomain should be considered as a new feature that may not be supported right now. Or maybe you need to define your assets url with a full domain to point to it to ensure the links don't 404 from their default configuration. Where are your connectors at?
danya_postfactum submitted:
The problem occurs due to cross domain origin policy of XHR. When scripts in site.com/assets/components/ folder, they try to access manager.site.com. They, of course, should be placed in manager.site.com/components/assets/
danya_postfactum created Redmine issue ID 8531
Ext-js files of components should be in the manager/components directory.
At this moment component panels don't work when manager uses another domain ( manager.example.com ).
It seems modx installation should have manager/components directory for this purpose and components with backend scripts should move its assets to this directory.