Hi,
Op 17-06-12 22:17, Raphael Hertzog schreef:
Hi,
On Sun, 17 Jun 2012, Adwin Timmer wrote:
The following change in 3.4: "[a6d0b9f] Default configuration now sets
WP_CONTENT_DIR to /var/lib/wordpress/wp-content" works OK for plugins, except
for the fact that in case the web browser tries to retrieve content from a
plugin directory, /usr/lib/wordpress/wp-content/plugins/ is used, instead of
/var/lib/wordpress/wp-content/plugins/. Linking all plugin directories from
/var/lib/wordpress/wp-content/plugins/ in
/usr/lib/wordpress/wp-content/plugins/ resolves the problem, but this is of
course an unwanted solution.
This is one of the reasons why the default Apache configuration now
recommends to setup:
Alias /wp-content /var/lib/wordpress/wp-content
And this is documented in NEWS.Debian.
What else should be done?
OK, sorry, I missed that documentation in NEWS.Debian. To be honest,
when I am upgrading, I only look at the apt messages and what is emailed
to me via apt-listchanges. Of course I should look at everything, but I
do not think that most people look at all the available documentation.
If something goes wrong with an upgrade, I look at bugzilla and at the
changelog.
Regards,
--
Adwin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
