On Thursday, August 30, 2012 at 11:18, Raphael Hertzog 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.
Looking at the bundled plugin, akismet, I see in
/usr/share/wordpress/wp-content/plugins/akismet/admin.php at least one
plugin_basename(__FILE__).
Wouldn't this cause a problem because
plugin_basename("/usr/share/wordpress/wp-content/plugins/akismet/admin.php")
with
WP_PLUGIN_DIR = "/var/lib/wordpress/wp-content/plugins"
would return
"/usr/share/wordpress/wp-content/plugins/akismet/admin.php"
And that is not a basename - it's an absolute path...
Oskar
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
