Drupal pages work, no CSS (wrong URL)

Hi all,

First I must say thanks to the many people who have contributed to Drupal, it's a fantastic CMS, and a pleasure to use. Now, to the issue I'm experiencing:

Recently I created a new installation of Drupal on my company's website (hosted with www.digitalpacific.com.au). It is located here:

http://dev.elfx.com.au

It is a fresh install of Drupal 5.7. As you can see, there is no CSS formatting. The CSS files don't appear to be accessible by my browser (Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.11) Gecko/20071204 Ubuntu/7.10 (gutsy) Firefox/2.0.0.11). I don't believe this is a browser issue though.

I'm not sure how to explain this, it's quite bizarre. Anyway, here goes..

When Drupal is installed in the main site (http://www.elfx.com.au, the DocumentRoot of the webserver; NB: no Drupal site there currently, was installed momentarily for testing purposes), it works fine. When moved to a sub-domain (http://dev.elfx.com.au), there comes URL/path issues.

I compared the output of phpinfo() on both the main site (www.) and the sub-domain (dev.), and there existed differences in the _SERVER["SCRIPT_NAME"] variable. On the main site, the contents of SCRIPT_NAME was simply "/phpinfo.php", on the dev site, the contents were /var/subdomain/dev/html/phpinfo.php, but in theory that should have been simply /phpinfo.php also.

/var/subdomain/dev/html is a symlink pointing to /var/www/dev/ (where the subdomain exists).

All of the CSS import lines in the page source of http://dev.elfx.com.au include the /var/subdomain/dev/html/ path, where that should be just "/". This extra URL (/var/subdomain/dev/html/) creeps into other Drupal-generated URLs also, which prevents them from working (such as clicking on the site title to get back to the main page).

I'm not sure if this is an issue with Drupal or not. Is Drupal using the $_SERVER variable to get an appropriate path?

Apparently Joomla! works with this hosting company's setup, so perhaps there's an issue in Drupal's code.

Thoughts would be appreciated (even if it's to clarify whether this may or may not be an issue with Drupal, but with the hosting company's site setup).

Cheers,

Lem