Blogger Custom Domains, Too Mapped Services
Saturday, October 5, 2019
Edit
I've been observing custom domain publishing, as well as how it's affected yesteryear applications mapped through diverse Google services, for a few years.
The good known "Another blog", as well as it's successor "Key already exists", accept three possible causes.
If yous map a Google service to a URL inward your domain, fifty-fifty temporarily, as well as therefore exactly disable the service, yous tin halt upwards amongst a domain URL that remains mapped to the service. When yous endeavor to position out your spider web log to that URL, you're going to run across "Another spider web log ..." or "Key already exists ...".
When in that place is an service mapped to a URL, that yous require to use, reset the service.
Resetting a service is non hard - equally long equally yous accept access to the dashboard, for the service that's mapped to your domain URL.
Create a novel DNS address inward the domain.
In this example, amongst the service existence a Google Apps Engine project, we'll remap to "project.mydomain.com". Create a novel "CNAME".
Enable the service.
The service has to move enabled, for the settings to move changed.
Change the service mapping, to the novel address.
Change the app to position out to "project.mydomain.com". This volition complimentary upwards the electrical flow URL, "mydomain.com" or "www.mydomain.com", therefore yous tin position out the blog.
Publish exactly about content, using the service.
This ensures that the service remapping becomes active.
Delete the published content.
Be tidy, as well as withdraw residue content, earlier disabling the service.
Disable the service.
You are right away done amongst the service - until yous want to choke on working on it later.
Re position out the blog, to the domain.
Publish the spider web log back to the BlogSpot URL (if necessary), as well as therefore i time again publish to the domain URL. And don't forget to redirect the domain root, if yous exactly published to the primary domain URL (generally, the "www" alias).
You're done.
And finally, complete the migration.
The good known "Another blog", as well as it's successor "Key already exists", accept three possible causes.
- Actual content, published to the URL.
- Bogus DNS addresses.
- Database corruption.
If yous map a Google service to a URL inward your domain, fifty-fifty temporarily, as well as therefore exactly disable the service, yous tin halt upwards amongst a domain URL that remains mapped to the service. When yous endeavor to position out your spider web log to that URL, you're going to run across "Another spider web log ..." or "Key already exists ...".
When in that place is an service mapped to a URL, that yous require to use, reset the service.
Resetting a service is non hard - equally long equally yous accept access to the dashboard, for the service that's mapped to your domain URL.
- Create a novel DNS address inward the domain.
- Enable the service.
- Change the service mapping, to the novel address.
- Publish exactly about content, using the service.
- Delete the published content.
- Disable the service.
- Re position out the blog, to the domain.
- You're done.
Create a novel DNS address inward the domain.
In this example, amongst the service existence a Google Apps Engine project, we'll remap to "project.mydomain.com". Create a novel "CNAME".
project.mydomain.com. 3600 IN CNAME ghs.google.com.
Enable the service.
The service has to move enabled, for the settings to move changed.
Change the service mapping, to the novel address.
Change the app to position out to "project.mydomain.com". This volition complimentary upwards the electrical flow URL, "mydomain.com" or "www.mydomain.com", therefore yous tin position out the blog.
Publish exactly about content, using the service.
This ensures that the service remapping becomes active.
Delete the published content.
Be tidy, as well as withdraw residue content, earlier disabling the service.
Disable the service.
You are right away done amongst the service - until yous want to choke on working on it later.
Re position out the blog, to the domain.
Publish the spider web log back to the BlogSpot URL (if necessary), as well as therefore i time again publish to the domain URL. And don't forget to redirect the domain root, if yous exactly published to the primary domain URL (generally, the "www" alias).
You're done.
And finally, complete the migration.