When you connect a domain for a free or starter account, the default is that the domain is available for the website, blog, and landing pages.
It is optional how you configure the domains for Pro and Enterprise, but this might also impact those users depending on the domain/subdomain chosen for the blog vs website.
A user connects their domain and expects to publish their website home page on the root domain.
They get an error that a page already exists with that page path, despite not having created any other content.
This is happening because the blog listing page URL hasn't been set.
Once a blog is created, the user can add a page path to the Blog Slug and the blog listing page is no longer parked on the root domain, allowing the home page to publish.
This has popped up at least 20 times in the last few weeks here in the community and it's causing a lot of confusion.
When a domain is connected, the root domain should be reserved for the website and since a blog listing hasn't been created yet, there should be a temporary path for "blog" until the user configures something.
... Exibir mais