id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc
6938,Allow wp-content directory to exist in a custom location (not relative to ABSPATH),sambauers,anonymous,"This enhancement is related to ticket #6933, with similar reasoning.

 1. It's a little more secure if wp-content happens to also be outside the webroot
 2. It allows us to add WordPress as an external repository in other projects with plugins/themes/cache engines/database classes that sit outside that external repository (we do some of this with bbPress)

WordPress requires a few changes as there are a few hard-coded references to wp-content.

If we don't like the constant name I chose ( WP_CONTENT_DIR ), then that can be easily changed in the patch.

This will almost certainly break a few plugins where wp-config is hard-coded, but only when the blog owner chooses to use this feature. Naughty plugins should use API calls anyway :)",enhancement,closed,normal,2.6,General,2.5.1,normal,fixed,has-patch,