Skip to:

Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#1936 closed defect (bug) (fixed)

Update 'siteurl' variable 'home'

Reported by: bebradsm1's profile bebradsm1 Owned by:
Milestone: 1.5 Priority: minor
Severity: Version:
Component: Core Keywords: siteurl home domain core, reporter-feedback


Originally posted at:

I noticed Buddypress confuses the use of the WP "siteurl" and "home" variables.

The following scenario applies to WPMU and BP 1.2 RC2.

I have moved all my core WPMU files to their own directory instead of the root. This requires me to update the "siteurl" variable to point to those files. The "home" variable still points to the domain. (As recommended in

Meanwhile, in bp-core.php, the bp_core_get_root_domain() description says: "@return $domain The domain URL for the blog." However, the actual functions return the value of "siteurl" instead of "home." In this case, "siteurl" is *not* the value of the domain. If I manual edit this core file to make the change the problem goes away.

Otherwise, the result is that some links generated by BP, i.e. adminbar, look like http://domain/wpdir/members instead of http://domain/members (the addition of the <wpdir> folder).

Change History (7)

#1 @andrea_r
14 years ago

Can you confirm that setup works in WPMU without BP active? Because it's my understanding that unlike single WP, WPMU can't be moved. Specifically, check the blogs.

#2 @DJPaul
14 years ago

  • Keywords reporter-feedback added

#3 @ousep
14 years ago

Confirming that this is an issue in WP 2.9.2 (single).

#4 @johnjamesjacoby
14 years ago

  • Component set to Core
  • Resolution set to fixed
  • Status changed from new to closed

This was also reported and patched by sambauers a few weeks ago.

#5 @ptroxler
14 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

as per my post on the forum, using 'home' does corrupt the login link in the adminbar on a WP 3.0 single install with

#6 @r-a-y
14 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

Fixed in trunk. Any reason why [3343] did not apply to 1.2 branch as well?

#7 @DJPaul
14 years ago

1.2.7 is imminent for branch and is only meant to be a maintenance release with critical bug fixes in. There will probably be a 1.2.8 around the time of the WordPress 3.1 release which will only fix a couple of known compatibility bugs. Everything else is going into 1.3, which we're shooting for a mid/early January.

Note: See TracTickets for help on using tickets.