#5433 closed defect (bug) (fixed)
Buddypress breaks with symlinked plugins dir
Reported by: | elrata_ | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Core | Keywords: | needs-docs |
Cc: | rodrigo-wp@… |
Description
If the plugins directory in WP uses symlink, buddypress breaks (1.9.2 and 1.8.1 at least) and doesn't show js, etc.
The default debian stable WP package, using the script provided in the package, creates the symlink for the plugins.
The only way to make buddypress work, that I found, was setting define('WP_PLUGIN_DIR', ...) to the appropriate dir.
Can this be documented somewhere ?
Thanks a lot,
Rodrigo
Change History (6)
#2
@
11 years ago
Thanks you for the quick reply!
Nope, is the entire plugins dir:
$ ls -l /srv/www/wp-content/myblog/ total 12 drwxrwxr-- 2 nobody nobody 4096 Jan 28 15:46 blogs.dir lrwxrwxrwx 1 nobody nobody 39 Jan 28 15:46 languages -> /var/lib/wordpress/wp-content/languages lrwxrwxrwx 1 nobody nobody 37 Jan 28 15:46 plugins -> /var/lib/wordpress/wp-content/plugins lrwxrwxrwx 1 nobody nobody 36 Jan 28 15:46 themes -> /var/lib/wordpress/wp-content/themes drwxr-xr-x 2 nobody nobody 4096 Feb 26 15:33 upgrade drwxrwxr-- 4 nobody nobody 4096 Feb 24 17:35 uploads
The wp-content directory is not symlinked
#5
@
11 years ago
- Milestone Awaiting Review deleted
- Resolution set to fixed
- Status changed from new to closed
Thanks. I've created a new Codex page: http://codex.buddypress.org/getting-started/setting-up-a-new-installation/installing-buddypress-in-a-symlinked-environment/
The Codex is editable by anyone with a wordpress.org or buddypress.org account, so if there are additional details that you'd like to edit or add, please feel free! Thanks.
Thanks for the report. Can you give more details about how the the Debian WP package is configuring the symlinks? Is each plugin individually symlinked, or is it the entire plugins or wp-content directory?
If it's on an individual-plugin basis, then the problem should go away with WordPress 3.9. See https://core.trac.wordpress.org/ticket/16953