Opened 11 years ago
Closed 11 years ago
#5489 closed defect (bug) (duplicate)
Symlinked 'buddypress' directory not referenced when setting buddypress()->file
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 1.6 |
Component: | Core | Keywords: | has-patch dev-feedback |
Cc: |
Description
If we are manually defining the BP_PLUGIN_DIR
constant for symlinking purposes, buddypress()->file
does not take this into consideration.
This notably breaks the bp_is_network_activated()
function because buddypress()->basename
references __FILE__
instead of the symlinked directory.
To test:
- Set up a new multisite install with the 'buddypress' directory symlinked.
- Network-activate BuddyPress and go to the network admin dashboard
- You won't see the following items: "Settings > BuddyPress", "Tools > BuddyPress"
Attached patch addresses this by setting buddypress()->file
to use the BP_PLUGIN_DIR
constant.
Attachments (1)
Change History (7)
#3
@
11 years ago
- Milestone changed from Awaiting Review to 2.1
Do the plugins directory symlink changes in WP 3.9 affect this at all?
Note: See
TracTickets for help on using
tickets.
I've experienced this exact problem before.
r-a-y, I think that your patch looks like the right solution, but in an abundance of caution (and since this is not a regression in 2.0), I'd prefer to do it for 2.1. Is that OK with you?