Minify problem in manager on staging server xxx.xxx.xxx.xxx/~xxx address

[FickleLife]

ficklelife created Redmine issue ID 6247

Forum post: http://forums.modx.com/thread/72361/modx-2-2-rc1-install-problems-on-site5-with-temporary-url#dis-post-402631
Initial bug report (thought it was related to another bug): http://bugs.modx.com/issues/6165

Summary:
I'm installing a fresh 2.2 (6th Dec nightly) to a fresh site5 reseller account with a xxx.xxx.xxx.xxx/~xxxx/ address (staging before it goes to www.xxxxxx.com address). I can install successfully, however on first login to the manager I get an unstyled page, no JS or CSS loaded. Opening up firebug I get the following errors on several files:

GET http://46.20.118.12/~rubadub/manager/min/?f=/~rubadub/manager/templates/default/css/xtheme-modx.css,/~rubadub/manager/templates/default/css/index.css 400 (Bad Request)

The error is regarding minify on several JS and CSS files, effectively halting all javascript loading. I did test this on a different site, and as soon as I went from the temporary xxx.xxx.xxx.xxx/~xxxx/ address to a legit www.xxxxx.com, minify worked.

Environment info: http://dl.dropbox.com/u/419424/phpinfo/phpinfo.html

Can easily provide a temporary acct on site5 to replicate the issue if needed, email me at alexleeblack@gmail.com

[splittingred]

splittingred submitted:

I can't replicate this; tried an install with a ~, and that worked fine, so that's not the issue.

The first worrisome things I see in your php.ini are:

• magic_quotes_gpc needs to be set to Off
• max_execution_time should be at least 60
• Try upping your memory_limit to 128M

[opengeek]

opengeek submitted:

I can confirm this does not work with Apache user directory configurations and seems to be an issue with min whenever any virtual directory paths are involved.

[FickleLife]

ficklelife submitted:

Thanks Jason, I tried a fresh 2.2 nightly 15th Dec install and it worked. Weirdly, I just tried upgrading a 2.1.3 site on a staging address to 2.2 nightly 15th Dec and I had the same minify problem. They're on exactly the same environments as detailed above. The site I attempted to upgrade was installed at http://xxx.xxx.xxx.xxx/~xxxx/xxxx - It's in a subfolder just incase that is important. Later on tonight I'll try to upgrade a fresh 2.1.3 to 2.2 nightly 15th dec and see if I get the same minify issue.

[FickleLife]

ficklelife submitted:

Tried on the fresh install, all went ok. Must be something wrong with my install. Cheers.

[FickleLife]

ficklelife submitted:

Hi Jason, there seems to be a related minify issue with Articles. I incorrectly filed a bug report in the articles section: http://bugs.modx.com/issues/6411

It's probably also related to this: http://bugs.modx.com/issues/6383 even though I have tried goldskys corrected file and it doesn't fix it.

Any ideas? Environment is same as before: http://dl.dropbox.com/u/419424/phpinfo/phpinfo.html

[opengeek]

opengeek submitted:

Unfortunately, this was a known limitation of the fix I made here; basically have to figure out how these component specific paths can be registered with our min integration when there are virtual directory mappings that need to be added. I'll have this resolved before pl.

[modxbot]

whistlemaker submitted:

I am now seeing this problem after updating from rc2 to rc3
I have tried installing it several times.
php memory is 128M and max_execution_time = 60
PHP 5.2.17
I don't have time right now to go back to rc2 so that I can look at the system report.

[modxbot]

whistlemaker submitted:

I tried setting the modx_system_settings compress_css and compress_js to '0' and now my manager is working fine

[opengeek]

opengeek submitted:

Bill, if you were fine before rc3 this is not the same bug you are experiencing, but may be a result of changes made in it. I'll need more information to help you diagnose, especially your $_SERVER['DOCUMENT_ROOT'] as well as the MODX_MANAGER_PATH, MODX_MANAGER_URL, MODX_ASSETS_PATH, and MODX_ASSETS_URL defined in your config file.