PLUGINDIR should be properly interpreted if absolute path

  • Ralf Bergs

    (@rabe)


    17 years, 1 month ago

    Hi there,

    I’m using Debian’s version 2.1.2-1 of WordPress, and I have several different WordPress sites using Debian’s config mechanism (files config-<domain>.php in /etc/wordpress/).

    I want my users to be able to have a plugins directory for their own, so I naively defined PLUGINDIR in a config-<domain>.php file and set it to an absolute path, like /home/<user>/www/wp/plugins. However, whereever WP uses PLUGINDIR, it prepends ABSPATH to it, regardless whether PLUGINDIR is a relative or absolute path.

    So my request would be whereever PLUGINDIR is used, first check whether it’s absolute, and in that case use the value as specified. Only if it’s a relative path, prepend ABSDIR to it.

    Another request would be to introduce a define for the themes directory, so that I am able to offer each user a separate themes directory as well.

    Thanks!

    Regards,

    Ralf

  • The topic ‘PLUGINDIR should be properly interpreted if absolute path’ is closed to new replies.