Repository navigation
Stop Setting the URL Constants #35
Description
I've found an issue with setting the WP_HOMEURL and WP_SITEURL constants in the wp-config.php file. When site_url(); or home_url(); are called within the theme they fail to output the actual url (either nothing at all or just /wp). It seems we've been through this before with Genesis but I'm not sure if that was changed for a different reason.
Activity
ericclemmons commentedon Dec 11, 2014
I think this is intentional (because of my research with Bedrock & multi-env WP installs), because these constants are used in tons of places (particularly data and URLs saved to the DB) that'd otherwise have to be corrected.
The hope is that these URLs return
/or/wpso we have path-only URLs.What's the best way of handling this?
jimmynotjim commentedon Dec 11, 2014
Looks like roots doesn't set those (outside of changing the env here https://github.com/roots/bedrock/blob/53a5013e0b13754a94f8a9271d4ce809bbe3dc3c/config/environments/production.php#L8-L9) but rather sets a content dir constant https://github.com/roots/bedrock/blob/master/config/application.php#L26-L31.
ericrasch commentedon Dec 11, 2014
Timely... this article was just published on the
wp-config.php. Looking at the 1. WordPress URLs section, there's a link that goes to this article: http://pressing-matters.io/using-wp_siteurl-and-wp_home-to-migrate-a-wordpress-site/It's worth a quick read.
ericclemmons commentedon Dec 11, 2014
I'll have to check again. I remember lots of experimentation leading to introducing these constants back in (in addition to the content directory change), particularly around uploads.
I have to say, I didn't have intermittent issues like @jimmynotjim described with how the generator works: