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 like to validate their Stats displays, using third party visitor logs like StatCounter.
Since Stats displays aggregated page view counts - not individual visitors - a blog owner will find many discrepancies between Stats and StatCounter. One observation might involve Stats indicating periods of no activity, where StatCounter shows an interesting visit.
A visit, registered by StatCounter - but not by Stats - indicates an apparent problem with Stats. Or, so the blog owner might think.
StatCounter displays page views, by counting clicks on the readers computer.
(Note): Please observe that "page views" come from both dynamic pages ("posts") and static pages ("pages") being accessed. When I refer to "page views", don't get confused about dynamic pages ("posts") vs static pages ("pages") - "page views" apply to both.
Stats displays page views, from the Blogger servers. If a page being accessed, by a reader, is already in cache on the readers computer, there will be no access to the Blogger server, and no Stats activity.
This discrepancy can contribute to confusion about visitor count. If two readers, sequentially sharing a public computer, access the same blog page, StatCounter may indicate two visitors.
If the first reader does not cautiously clear the computer before vacating, the second reader will access the page from cache - and will not register Blogger server activity. Stats will show no page views, indicating a second reader.
If a computer is being used with other people waiting for a turn, a reader may not have a chance to clear the computer before giving control to a second reader. The busier the computer, the greater the chance that Stats and StatCounter may show an apparent discrepancy.
There will always be differences between Stats and any other visitor log - just as there will always be differences between any two visitor logs, in general. A discrepancy is not always an inaccuracy.
Occasionally, someone may publish a blog as private, invite / accept readers, then later decide that results are not as positive as desired.
It's easy enough to change a blog, from Private to Public. Just go to the Permissions wizard, in the dashboard menu Settings - Basic, and change Blog Readers from "Private" to "Public".
Unfortunately, this may not leave everybody able to access the blog.I made my blog public, last week. Some of my friends are now seeingYour current account does not have access to view this page.
Why is this still an issue?
The blog owner, in this case, is seeing the effect of cache, and authentication.
In many cases, simple instructions to "clear cache, cookies, and sessions" may resolve this problem. This does not always work, however - and the mystery why it does not always work may frustrate us, almost as much as the original symptom.
Sometimes, clearing private data - even though it may be a bit drastic - does nothing to resolve the problem at hand.I just did that - and there's no improvement!
Now, we suspect that there is a cache, outside the browser, that can't be cleared.
There is no permanent solution, for upstream cache. But, there may be a diagnostic step, that helps us understand what is going on.
This is the URL of this blog.http://blogging.nitecruzr.net/
If I need to access the main page, without refreshing the browser, or clearing cache, I can retrieve the updated content, on a temporary basis.http://blogging.nitecruzr.net?
A URL containing a "?" is normally used for retrieving a web page, dynamically, with extra settings embedded in the URL.http://blogging.nitecruzr.net?something
A dynamic retrieval is evaluated immediately, using the Blogger server (in this case) - and without any interference from any caches.
Even without a real need to have the URL evaluated by the server, we can still make the URL dynamic, just by adding the "?" at the end. And this bypasses any cache - including cache upstream from the browser.http://blogging.nitecruzr.net?
Just remember - this is a temporary solution.
If you forget to use the "?" later - and you retrieve the old web page, still in cache, don't be surprised to keep seeingYour current account does not have access to view this page.
Until the cached page expires normally, from the cache that you can't control, that's going to still be a possibility.
>> Top
