By -Anti- on

If drupal is in a subdomain (ie. it is reached using http://www.sub.domain.net),
does the base_url in settings.php need to be set to reflect that?

The reason I ask is because:

· emails sent from drupal, informing of updates, have a link like:

See the available updates page for more information:
http:///en/admin/reports/updates

· There is a cron error logged everyday:

Location:
http://?/home/[name]/public_html/[sub]/cron.php

Message:
parse_url(http:///sites/default/files/) [function.parse-url]:
Unable to parse URL in /home/[name]/public_html/[sub]/includes/common.inc on line 436.

Could not setting base_url cause that type of problem?

Cheers.

⋅ Categories: Drupal 6.x

Comments

-Anti-’s picture

-Anti- commented

OK, specifying the base_url stopped the cron error.

But the email notifications sent still have a link: http:///en/admin/reports/updates
Anyone else seeing that? Any solution?

cheers.

EDIT: OK, I just got an update message today from my sites, and the url in the email is fixed (ie. correct). So even though it doesn't cause any other problems, it appears that setting base_url is necessary for some core functions if your site is not in root. I set base_url to: http://sub.domain.net

I have no idea why the email was still broken straight after I set base_url and then ran cron manually to test it. But one month on, letting it all happen automatically, it works