This was saved as a draft. How did it go public?

Visibity: Draft was set on pupose.  NOT PUBLIC.

I have overwritten the content.

Add categories, groups... Test. Test. Test.  Push out the update... Test. Test.Test.  

20120212abc123test

I had saved this as draft, somehow it went public. So now I have overwritten the post, 15 hours later, to push it out of the cache, there can be so many of those!

This is Google's cache of http://activerain.com/blogsview/2833155/test-01-for-mac. It is a snapshot of the page as it appeared on Feb 12, 2012 01:00:01 GMT. The current page could have changed in the meantime. Learn more

How long will it take to expunge every cache? – Purging the obsolete content from each search engine cache and index may take days or weeks. — Cannot delete the post until the cache contents are overwritten.

http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1663691

To remove the cached version of a page:

1. Go to the Google public URL removal tool.
2. Click New removal request.

URL  Status  Removal  Type   Requested

http://activerain.com/blogsview/2833155/test-01-for-mac

Outdated cache removal

Feb 12, 2012

It's gone from Google cache. Hooray! Updated blog title, made it Members Only.

It took about six hours since the cache removal request.

Timeline:

8pm Saturday, saved blog DRAFT.

12am Sunday, checked in and found the post PUBLIC. Whoa!

1pm Sunday, erased the content, updated the blog, left comments.

5pm Sunday, still in cache, requested removal.

7pm Sunday, still in cache.

9pm Sunday, old content finally removed from Google cache.

However, a Google search on a few keywords in the old post does brings up the new post, but the old cache info is not visible.  The Google Index and the Google Cache are two different beasts!

Bing never even got around to indexing the blog.

Hi Doug, it's as if that Visibility: Draft button has a mind of it's own.  I am sure I set it to DRAFT very intentionally, but it still went PUBLIC somehow.

Update: Removed Members Only... just to see if Bing ever gets this.

I think I've just discovered the cause of our "DRAFT—to—PUBLIC unintentional transition" shared experience!  (Or a scenario that reproduces it.)

This, imho, could be the biggest usability issue I have seen in ActiveRain.

Scenario:

1. The phone rings, you want to save your DRAFT.  No problem. Hit the POST BLOG button.  The Visibility is DRAFT.

2. You forgot (or decided to wait till later) to write the TITLE, which is SO very important to get right.

3. Big red error pops up, "You need to enter a title and an entry for this blog post."  (Of course, you know, I did NOT want to write the title yet...)

4. You put a temporary title on it instantly.

5. You will probably NOT notice, the SYSTEM changed DRAFT to PUBLIC when it posted the error message on your screen.

6. You are in a hurry to get to the phone... You click SAVE  (i.e. Post Blog.)

7. BUMMER!!! You just posted your DRAFT as PUBLIC, and Google has got it, already, in the index, for all to see, and it will be in the Google Cache very soon, also.

IF you have a bunch of GROUPS, the distance from the VISIBILITY box to the POST BLOG button may be several screens full.  You will NOT see it, I guarantee!

This is a design for failure!  I call it a "usability BUG!"

Doug, Does that explain your experience?  It does fit mine.

You intentionally select DRAFT.  

You intentionally leave the title blank.  

Do some editing.  Phone rings.... You click SAVE  (i.e. Post Blog.)

RESULT: ERROR message,
and then the status is set to PUBLIC, automatically!  

If you are in a hurry, you are certain to miss that "automatic" change in status from DRAFT to PUBLIC. 

You click SAVE  (i.e. Post Blog.), bingo! Your "draft" just went PUBLIC.

Shall we now call this a "known bug?"

Workaround: You must scroll up (maybe a page or two) above the Post Blog button.... change PUBLIC to DRAFT before you click "Post Blog."  (Every time you save that draft, to be safe!)

The "Visibility" staus box seems to have a mind of its own?