On Fri, 01 Jun 2012, Stefano Zacchiroli wrote:
> 2) whether the machine sysadm has a way to install local extensions
> (which is badly needed, especially if (1) does not work) in some
> FHS-compatible way. Doing so directly under /usr/share/wordpress/ is
> a vary bad idea. Shipping symlinks there pointing to other locations
> (as README.Debian suggests) is only a bit better, but still a bad
> idea
>
> I could live without (1), but I'm very surprised to discover that (2) is
> not supported. The new bug I'm creating is meant to track (2) alone.
>
> I guess supporting (2) might be non entirely trivial, especially if
> wordpress expect all plugins to be located in a single directory, rather
> than being able to look them up following some kind of $PATH. So if you
> want to both ship a plugin with the package (like akismet) and allow
> users to install other extensions, you've a dilemma. But it's really
> badly needed, in order to allow people to manage wordpress sites in a
> more Debian-ic way.
It's relatively easy to do it. In my Wordpress config file I have put
this:
define( 'WP_CONTENT_DIR', '/srv/web/wp-content' );
And now I'm free to put whatever plugins/themes I want in
/srv/web/wp-content/{plugins,themes}/. For the default plugins/themes
that I want, I add symlinks pointing back to
/usr/share/wordpress/wp-content/{plugins,themes}/*.
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]
