I've written a few posts about editing post content - and discuss clearing cache after editing, to see updates.
Generally, my posts reference cached posts content. Sometimes, blog owners need to clear cached feed content, in addition to / instead of clearing cached post content.
There is a difference between post content, and newsfeed content - and how both are cached. Newsfeed cache is not as frequent a concern.
When we provide instructions to clear cached blog content, we reference browser cache.
Clear cache - then restart the browser, and check again.
or maybe
Clear cache, cookies, and sessions (yes, all 3) - then restart the browser, and check again.
Posts, updated after published, may create a problem with the posts newsfeed.
In some cases, updated posts may create an "out of sync" condition with the posts newsfeed, as well as the displayed content.
If comparing post content and feed content is important, you need to synchronize the newsfeed with the posts. This will restart the newsfeed - and sync it with the posts.
- Deactivate the blog feeds.
- Publish a post - or delete a recently published post.
- Reactivate the blog feeds.
Activate / Deactivate the blog feeds, using the "Allow Blog Feed" wizard.
The "Allow Blog Feed" wizard, on the dashboard Settings - Other page, in the "Site feed" section, is used to activate and deactivate the newsfeeds.
Look for "Site feed", and "Allow Blog Feed".
"Site feed" is on the Settings - Other dashboard page.
Open the drop down menu, and note the current setting. If you have "Custom" selected, dig deeper.
There are a few selections, in "Allow Blog Feed". For consistent results, note what you have before Step #1 - and re select them after Step #3.
This blog, like many others in Blogger, is "Always Under Construction".
This post, like many earlier ones, was just published. Now, I plan to spend many long hours, reorganising and tweaking the content, phrasing, spelling, syntax - and correcting typos.
If you wish, you can subscribe to any of several posts newsfeeds - and compare the newsfeed content in each, with the displayed posts content. The older any post is, the more changes will be made.
The more revisions I make, the less this post, and the posts feed, will match when compared. Check it, for yourself.
Maybe one day, I will need the feed, in this blog, be accurately updated to compare more closely to the updated posts. Many of my posts double in size, even after post publish edits are "complete".
If you use email, and other feed subscriptions, to read new posts in this blog, you may be missing out on interesting details, added long after posts are published.
Newsfeed content is published once, as each post is published.
Post content may be out of sync with feed content, because post content and feed content is not updated at the same time.
You can update your posts, when you wish. Newsfeed updates are published when the posts are published - and the cached newsfeed is not updated, when you edit a post after it is published.
When you synchronise published posts content with displayed content, you generally clear browser cache. Newsfeed cache is not in the browser - so the latter instructions won't help with newsfeed cache.
That is the basic procedure for syncing the blog content, and feed content. You may have other concerns, though, that might complicate the above procedure.
The procedure is exciting - but painless.
I initially published this post, without any photos - and we see my Reading List, an hour ago.
And my Reading List, after I restarted my blog feed.
It took all of 5 minutes, including making screen prints of my Reading List - before and after, to restart the newsfeeds.
As always, I'll suggest that you Follow this post - and observe the changes. And watch for changes (unlikely) to the newsfeed.
Many #Blogger problems, when being diagnosed, start with advice to clear browser cache (maybe, cache, cookies, and sessions). Not all problems involved the published posts - some involve the posts feed.
You can't clear feed cache, as you can browser cache, because newsfeed content is not cached in the browser. You can, however, force a newsfeed rebuild, by restarting the newsfeed.
Some blog owners have reported in Blogger Help Forum: Get Help with an Issue, about broken email distribution.
There are various ways to distribute Blogger blog content, to email. For those unable or unwilling to use FeedBurner Email Distribution, one popular alternative is Google Groups.
One drawback of FeedBurner based distribution is that FeedBurner uses the blog newsfeed - and is unusable for private blogs.
Google Groups is the best content distribution medium, for private blogs.
The only scalable distribution medium, for private blogs, is Google Groups. Right now, Google Groups, for some owners, is not accepting incoming email.
This problem may not be unique to Blogger blogs. There are other reports of this problem, in the Google Groups Support Forum.
We are asking for details, in a previously posted forum Problem Rollup topic.
We have a previously discussed article, and a Problem Rollup topic, in Blogger Help Forum: Get Help with an Issue - where we are requesting details, as phrased above, about the problems. If you have details to contribute, solution to this problem may result from your contribution.
Please help Blogger Engineering to help you - and make your responses polite, relevant, and responsive. If this problem is to be identified, and you are affected, resolution depends upon you. And also report your problem in Google Groups Support.
Some #Blogger blog owners are reporting that distribution of private blog content, using Google Groups, is not operational. This problem may not be unique to Blogger blogs, as there is some discussion in Google Groups Support.
In BlogLovin, the ownership verification process is termed "claiming your blog".
Claiming your blog involves installing a BlogLovin link, with embedded token, on your blog where it can be seen, by the BlogLovin claim verification process. Getting the claim link, from the BlogLovin dashboard, is not an obvious process.
Not every blog owner is able to get the BlogLovin blog claiming link, for their blog.
- Some folks can't find the "Claim blog" button.
- Others don't provide the right URL, into the "Claim blog" window.
If you have either problem, you end up unable to "claim your blog".
Finding the "Claim" button is not obvious.
You start the Claim process from the "Blog analytics" display. In some instructions, this is referred to as "My blogs". There is no menu selection to "Claim your blog".
From the home page, click "View all in Analytics".
From "Blog Analytics", click on "Edit blog settings".
Find the blue "Claim blog" button.
BlogLovin needs the blog published URL - not the blog feed URL.
Observe the caption in the "Claim blog" window.
When you provide the URL, only provide the published URL - not the blog feed. This works best if the blog publishes a feed, and if the blog has a standard Blogger header. BlogLovin gets the feed URL from the blog header - when the URL is there.
Paste the published URL of the blog - not the blog feed - into the window, and hit "Search".
Select your blog.
And, there is the BlogLovin link, with an embedded token.
Now, you install the token on your blog - and that is another source of confusion.
Not every #Blogger blog owner is able to verify ownership of their blog, to BlogLovin. Some folks can't find the "Claim blog" button - and others don't know what URL to provide, in the "Claim blog" process.
And the term "claim blog" is not obvious, to everybody, either.
Occasionally, a bewildered blog owner will write into Blogger Help Forum: How Do I?, and askHow do I completely remove a post? I deleted a post - but my readers still could read it, in Google Reader!
Some owners are not clear about the nature of post deletion, and the blog feed.
One of the solutions for recovering a deleted post is to retrieve it from Google Reader. Even if you have not subscribed to the blog feed, you can, at any time, subscribe, and retrieve the text content of any previously published post. This solution works because once published, a post will remain in the blog feed for eternity.
Until the post is published, it's in Draft status. As soon as the post is published, the published copy goes into the blog feed. If you immediately revert the post to draft status, the post disappears from the blog main page (subject to clearing browser cache) - but once published, the post remains cached in the feed.
As long as the blog exists, and the blog feed exists (the blog remains public, and the feed is enabled), all previously published posts will remain cached in the blog feed. It may be possible to reset the blog feed - though both of these solutions should be examined carefully - for how your existing readers might be affected.Depending upon local caches of feed content, the blog feed may, or may not, be reset for everybody, with either procedure.
This is both good, and bad - but it is simply something that you can't change, easily.
>> Top
