You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered this issue on two sites now. Sites launched seem to be pretty resolute about keeping their *.herokuapp.com names as the primary one for the WP instance.
In General Settings, WordPress Address (URL) is greyed out and Site Address (URL) is editable. In this state, editing Site Address to reflect a vanity domain takes the site down because it'll create a number of location problems: the server can't be reached, referenced assets are 404s, etc.
No amount of editing 'home' and 'siteurl' in the database's wp_options table seems to help.
I've managed to solve this once but couldn't reproduce my steps and I'm completely stuck.
Has anyone else had this issue?
Using CloudFlare for DNS.
Edit for clarity: Domains are properly set on Heroku dash.
The text was updated successfully, but these errors were encountered:
By tweaking whatever's there (eg hardcoding WP_SITEURL or WP_HOME to my domain string), I start to time out on any https page, so I'm locked out of wp-admin. Even with Cloudflare SSL on, is this normal?
I've encountered this issue on two sites now. Sites launched seem to be pretty resolute about keeping their *.herokuapp.com names as the primary one for the WP instance.
In General Settings, WordPress Address (URL) is greyed out and Site Address (URL) is editable. In this state, editing Site Address to reflect a vanity domain takes the site down because it'll create a number of location problems: the server can't be reached, referenced assets are 404s, etc.
No amount of editing 'home' and 'siteurl' in the database's wp_options table seems to help.
I've managed to solve this once but couldn't reproduce my steps and I'm completely stuck.
Has anyone else had this issue?
Using CloudFlare for DNS.
Edit for clarity: Domains are properly set on Heroku dash.
The text was updated successfully, but these errors were encountered: