On Thu, 30 Aug 2012, Oskar Liljeblad wrote:
> Now most plugins use plugin_basename(__FILE__) to determine their basename.
> It is assumed that this function returns a relative directory, but it doesn't
> if the plugin is not "physically located" in WP_PLUGIN_DIR (or
> WPMU_PLUGIN_DIR).
> (With physically located I mean located according to realpath (without
> symlinks) - the plugin may still be reachable through WP_PLUGIN_DIR.)
The default value of WP_PLUGIN_DIR is (see wp-includes/default-constants.php):
define( 'WP_PLUGIN_DIR', WP_CONTENT_DIR . '/plugins' ); // full path, no
trailing slash
And the default value of WP_CONTENT_DIR with the official Debian package
is /var/lib/wordpress/wp-content so WP_PLUGIN_DIR points to
"/var/lib/wordpress/wp-content/plugins".
Given the above, I believe that there should be no problems. Please check
that you have a correct version of /usr/share/wordpress/wp-config.php.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
