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? One thing which I might want to do to avoid instant breakage is to add supplementary symlinks for plugins and themes which were manually installed in /usr/lib/wordpress/wp-content/plugins/. And also the "uploads" or "blogs.dir" directories could be moved to the new directory... But in the end, whatever we do, the admin should update its Apache configuration to get a clean and reliable system. There's no way that the content within /usr/lib/wordpress/wp-content/ will automatically stay in sync with what's in /var/lib/wordpress/wp-content/. 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]
