WordPress on subdomains/addon domains

prasad0889

Currently the functionality for WordPress installation on subdomains/addon domains through Apps section is live on Enhance. Thanks a lot to the Enhance team for this.

I have faced a few issues, and I would like to list it here,

If installed on a sub-directory like domain.com/folder1 or domain.com/folder2, the URL is set to http://workaround/folder1 or http://workaround/folder2. How can we solve this, and make it point to domain.com/folder1? Even if we go ahead and edit it, it sets itself back to the workaround domain.
On addon domains, some WordPress installations do not pick up the domain name, and show as blank in the Control Panel. There is no way to manually set the domain if it hasn't been picked up by the system. Could you please let us know how to solve this?

Andreas

prasad0889

"http://workaround/folder1 or http://workaround/folder2."
I noticed that today as well, when I was testing this.

Adam

Are these brand new WordPress installations? Are there any overrides in wp-config.php for the WP_SITEURL or WP_HOME variables?

prasad0889 On addon domains, some WordPress installations do not pick up the domain name, and show as blank in the Control Panel. There is no way to manually set the domain if it hasn't been picked up by the system. Could you please let us know how to solve this?

SSH as the customer (or su to the website user) and run the following inside the WordPress directory. What is the result?

wp-cli option get siteurl

PradeepC

Adam Facing same issues as mentioned by @prasad0889

prasad0889

No Adam, these are older installs that already existed on the account before migrating to Enhance.
When I ran wp-cli option get siteurl it shows just https:///folder1 and not https://domain.com/folder1

PradeepC

prasad0889 @Adam Could you please let me know how to solve this?

Adam

It sounds like your WordPress site URL is set to a relative URL. The bit I don't understand is why editing it doesn't fix the problem. It could be a plugin is causing this. Or maybe it's defined somewhere in wp-config.php.

Can you send a support ticket? We'll take a look at the site(s) for you.