[wp-trac] [WordPress Trac] #13941: WP_CONTENT_URL should use site_url() to support HTTPS / SSL
WordPress Trac
noreply at wordpress.org
Tue May 21 15:10:15 UTC 2013
#13941: WP_CONTENT_URL should use site_url() to support HTTPS / SSL
-------------------------+-----------------------------
Reporter: micropat | Owner: ryan
Type: enhancement | Status: new
Priority: normal | Milestone: Future Release
Component: General | Version:
Severity: normal | Resolution:
Keywords: has-patch |
-------------------------+-----------------------------
Comment (by creativeinfusion):
The patch (though sensible) doesn't cater for sites that use the
recommended procedure for moving wp-content out of the wordpress directory
as per http://codex.wordpress.org/Editing_wp-config.php#Moving_wp-
content_folder (for example when using an SVN or git e.g.
http://ottopress.com/2011/creating-a-wordpress-site-using-svn/).
These constants can be a right pain, yet so many plugins use them instead
of the current doing_it_right() functions that setting them up correctly
still matters. Some really great plugins still use them and alas even then
do not not always honour overrides (e.g. by assuming plugins are in
WP_CONTENT_DIR/plugins). I'd ideally like to see the constants properly
deprecated to force use of the functions, but that seems unlikely.
wp-config.php is too early to set WP_CONTENT_URL for a subsite in a
multisite subdirectory install - it's not possible to reliably set it to
!http://domain.com/subsite/custom-content and know subsite exists. We can
use sunrise.php but that would involve a lot of code duplication and in
any case it's not available for single site installations.
Any mileage in having a drop in config file that can be used before these
constants are set but after most of the functions have been loaded?
--
Ticket URL: <http://core.trac.wordpress.org/ticket/13941#comment:21>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list