Blogger Custom Domains, In Addition To Mapped Services
Saturday, June 6, 2015
Edit
I've been observing custom domain publishing, in addition to how it's affected past times applications mapped through diverse Google services, for a few years.
The good known "Another blog", in addition to it's successor "Key already exists", bring three possible causes.
If y'all map a Google service to a URL inward your domain, fifty-fifty temporarily, thence only disable the service, y'all tin displace halt upwards amongst a domain URL that remains mapped to the service. When y'all seek to issue your weblog to that URL, you're going to run across "Another weblog ..." or "Key already exists ...".
When at that spot is an service mapped to a URL, that y'all postulate to use, reset the service.
Resetting a service is non hard - every bit long every bit y'all bring 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 beingness 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 issue to "project.mydomain.com". This volition gratis upwards the electrical flow URL, "mydomain.com" or "www.mydomain.com", thence y'all tin displace issue the blog.
Publish around content, using the service.
This ensures that the service remapping becomes active.
Delete the published content.
Be tidy, in addition to take repose content, earlier disabling the service.
Disable the service.
You are similar a shot done amongst the service - until y'all want to decease along working on it later.
Re issue the blog, to the domain.
Publish the weblog back to the BlogSpot URL (if necessary), thence i time again publish to the domain URL. And don't forget to redirect the domain root, if y'all precisely published to the primary domain URL (generally, the "www" alias).
You're done.
And finally, complete the migration.
The good known "Another blog", in addition to it's successor "Key already exists", bring three possible causes.
- Actual content, published to the URL.
- Bogus DNS addresses.
- Database corruption.
If y'all map a Google service to a URL inward your domain, fifty-fifty temporarily, thence only disable the service, y'all tin displace halt upwards amongst a domain URL that remains mapped to the service. When y'all seek to issue your weblog to that URL, you're going to run across "Another weblog ..." or "Key already exists ...".
When at that spot is an service mapped to a URL, that y'all postulate to use, reset the service.
Resetting a service is non hard - every bit long every bit y'all bring 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 around content, using the service.
- Delete the published content.
- Disable the service.
- Re issue the blog, to the domain.
- You're done.
Create a novel DNS address inward the domain.
In this example, amongst the service beingness 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 issue to "project.mydomain.com". This volition gratis upwards the electrical flow URL, "mydomain.com" or "www.mydomain.com", thence y'all tin displace issue the blog.
Publish around content, using the service.
This ensures that the service remapping becomes active.
Delete the published content.
Be tidy, in addition to take repose content, earlier disabling the service.
Related:
Disable the service.
You are similar a shot done amongst the service - until y'all want to decease along working on it later.
Re issue the blog, to the domain.
Publish the weblog back to the BlogSpot URL (if necessary), thence i time again publish to the domain URL. And don't forget to redirect the domain root, if y'all precisely published to the primary domain URL (generally, the "www" alias).
You're done.
And finally, complete the migration.
