Many problems with custom domain publishing are transient, and can be fixed by republishing to the domain URL. When encountered by a possibly transient problem, my advice is very basic.
One case, when this advice is not easy to execute, is with blogs that were previously hosted externally, and never published to a BlogSpot URL. A blog that was never published to BlogSpot can't be published back to BlogSpot. The FTP Migration effort, completed just recently, retained that option for many blogs. Blogs migrated from an externally hosted non BlogSpot URL, to a Google hosted non BlogSpot URL, won't necessarily have a BlogSpot URL.
When this happens, pick any available BlogSpot URL, and change the blog temporarily from custom domain publishing to BlogSpot publishing. You won't necessarily use a BlogSpot name even remotely similar to the domain, nor should you expect to do so. The way the republishing process works, you'll just use your BlogSpot name for a few seconds.
>> Top
Publish the blog back to BlogSpot, then re publish it to the domain URL. And recheck the redirect option.This is good advice, and generally easy enough to execute.
One case, when this advice is not easy to execute, is with blogs that were previously hosted externally, and never published to a BlogSpot URL. A blog that was never published to BlogSpot can't be published back to BlogSpot. The FTP Migration effort, completed just recently, retained that option for many blogs. Blogs migrated from an externally hosted non BlogSpot URL, to a Google hosted non BlogSpot URL, won't necessarily have a BlogSpot URL.
When this happens, pick any available BlogSpot URL, and change the blog temporarily from custom domain publishing to BlogSpot publishing. You won't necessarily use a BlogSpot name even remotely similar to the domain, nor should you expect to do so. The way the republishing process works, you'll just use your BlogSpot name for a few seconds.
- Publish to BlogSpot.
- Re publish to the domain.
- Done.
>> Top
Comments