-
☆ A M B ☆
- 3,141 Posts
If you're running it through the Minifier I'm not sure if it can be on a different host like that, the 400 bad request could stem from that.
Why would you want to minify your assets during development anyway? Sounds like you're only complicating it for yourself there.
-
MODX Staff
- 10,725 Posts
Minify will ONLY work with paths that are within a) the defined $_SERVER['DOCUMENT_ROOT'] of your install, b) the defined MODX_BASE_PATH of your site, or c) the defined MODX_MANAGER_PATH of your site. Otherwise, you'll have to do without the minification.
-
☆ A M B ☆
- 160 Posts
I am following the Doodles guide and thats the way it show how to load the assets. Is there another way to load assets without using the addJavascript function?
-
MODX Staff
- 10,725 Posts
Just make sure it's within those paths and it should work. You cannot minify things outside those paths, and you should never need to have such assets outside of those paths.
Maybe I'm misunderstanding, but the extra has to be within those paths I described.
-
☆ A M B ☆
- 160 Posts
I am currently developing a extra outside of the MODx BASE Path and also outside of Manager Path. I am using virtual hosts to store my extras under a different url while serving MODx on another url. Is it not possible to develop Addons like this?
How can I load my assets by bypassing the Minify controller?
-
☆ A M B ☆
- 3,141 Posts
$modx->registerClientScript() and the related functions.
http://rtfm.modx.com/display/revolution20/modX.regClientScript
Or disable compressions, set compress_js and compress_css to false in the system settings.
-
MODX Staff
- 10,725 Posts
You'll have to disable compress_js in order to use the addJavascript function for now.
-
☆ A M B ☆
- 160 Posts
Great, thank you both. I have opted for disabling the compression and it works great.
