WP fails to deduce WP_CONTENT_URL from WP_CONTENT_DIR

[Denis-de-Bernardy]

When you define WP_CONTENT_DIR, e.g. to __DIR__ . '/content', but not WP_CONTENT_URL, WP will mindlessly define the latter to get_option('siteurl') . '/wp-content instead of trying to identify the correct url by comparing ABSPATH and WP_CONTENT_DIR.

One issue that this introduces is that it's the wrong URL. Is this something that we want to fix? (If not, close the ticket.)

The other is that it might end up using the wrong protocol. (Related: #13941 and #15928.)

[jeremyfelt]

I don't think a direct relationship between WP_CONTENT_DIR and WP_CONTENT_URL is one we can assume.

My config could be setup to use a root path of /var/www/site/content/ for a URL such as http://site/wp-content/*.

It can be a little confusing if one is set without the other, but that's a decision best left to the specific configuration.

[nacin]

Replying to jeremyfelt:

It can be a little confusing if one is set without the other, but that's a decision best left to the specific configuration.

Agreed.