On Fri, Jun 01, 2012 at 09:47:38PM +0200, Raphael Hertzog wrote:
> 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}/*.
It is a nice work around, thanks for the heads up.
But it still doesn't look as a satisfying solution for this bug report:
- it needs to be configured on a per-instance basis (which, arguably,
could be fixed by the site-wide configuration setting WP_CONTENT_DIR
somewhere sensible by default for all instances; but currently it's
not done)
- it just pivots around the default: instead of having to symlink
non-default themes/plugins added by the sysadm, you now have to
symlink the default themes/plugins that come with the Debian package.
Meaning that when/if the wordpress Debian package will ship new
themes/plugins (or plugins wordpress Debian packages appear), the
sysadm will need to discover that and add the needed symlinks. And
that should be done for all instances that have set WP_CONTENT_DIR
A satisfying solutions should allow at the same time to change the set
of available themes/plugins available for all wordpress instances by
means of package manager actions (e.g. upgrading the wordpress package
of installing wordpress extension packages) *and* empower the sysadm to
do the same by dropping themes/plugins in FHS-compatible paths.
Cheers.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences ...... http://upsilon.cc/zack ...... . . o
Debian Project Leader ....... @zack on identi.ca ....... o o o
« the first rule of tautology club is the first rule of tautology club »
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
