Category Archives: Blogger

The CTRL-Z Blogger Hole

Blogger.com

I’ve run across this ctrl-z bug a few times in the Blogger interface and it’s about to drive me nuts. The first time I noticed it I was working on an article that I had published previously, an article that still had some cludgy wording in it I wanted fixed, and I wanted to add a bit of HTML zing! to the post. I had it open in the blogger edit interface, the same old Blogger interface that has been the Blogger interface since the beginning of the world wide web if not the beginning of time as we know it. A white and grey interface with orange buttons? The one that has a toggle in the upper left corner that says “Compose” on one button and “HTML” on the other? Two different shades of grey? You know the one I’m talking about. I had messed up some code I had entered under the “HTML” setting, and after checking the results in “Compose” I hit ctrl-z to undo the change, and the entire post I was editing simply disappeared!

Luckily I could just back out and start over re-editing. It was a pain but at least I could access the original post. This error has happened a few times since then. Every time it has happened, I have had a version of the post that I could go back to, luckily. A frustrating but recoverable error. Until this time.

Today I was working in a test post that I keep hanging around to save snippets of code in, handily named test post. I had just done some tweaking on some code in the HTML interface. I didn’t like the way it looked in the Compose interface, and I stupidly did the same thing again. I can clearly remember thinking “where was that error?” right before discovering the error again. However, this time I had no version to go back to because test post had never been published for more than a few minutes, and since it was currently a draft post the blogger interface helpfully over-wrote my test post, with all those years of HTML coding snippets saved just for this reason, so that I wouldn’t lose them, and it over-wrote that long, ugly mess with a fresh, new, blank post it had created when I hit ctrl-z.

Funny? It did once. Does again

If I had been thinking at the time I might have stopped everything and gone looking. I mean, I know there is an excellent article (from 2009) on recovering deleted posts over on The Original Blogger Tips and Tricks. I first ran across his five points for recovering deleted blog posts last year when the mobile Blogger app helpfully overwrote a published post I just happened to have created in the mobile interface before completing it later on the desktop. When I reopened the mobile version to do what I saw as some quick editing, it opened the stored version of the earlier post, and then wrote that clearly unfinished, earlier work over the published, significantly longer, one. Suggestion four from his list look for a cached version worked like a charm on that occasion, and I was able to just pretend the entire screaming-rage-fit had never happened.

It has views to prove it.

Suggestion number three, go back to a previous version in the same window might have been helpful had I not rage-quit the window in frustration just moments before going to the blogger forums to complain about the fact that ctrl-z still deletes everything on screen in the edit interface and being helpfully reminded of the Tips and Tricks post by the first thread that mentioned ctrl-z.

This is an old, old interface error. I know it’s an old and common complaint, because there is a near-endless string of threads on the blogger forum that documents just how old and frustrating this error is. Just enter ctrl-z into the forum search window, and look at all the people who have the same problem, with no good resolution to be offered to them other than to be lectured to about backing up your data.

Yes, we understand. We are all but children in the eyes of the internet gods who never commit an error. We are so sorry to have to point this out but sometimes shit just happens. Sometimes you do something that you know is wrong at exactly the instant you do it, but you somehow still do it anyway. We children would really like known bugs to be fixed when they are brought to the attention of the for-profit programmers who work in the giant corporations that can’t help but run our flawed, childlike world. If you aren’t going to fix your errors, why the hell should the rest of us be any different? Why the hell are we relying on you when we could write code at least as well as you do, and do it in our own time? How many years does it take to fix an obvious flaw like ctrl-z blanks the edit window? I’m certain I could duplicate blogger’s interface in less than a decade, and I really don’t have to since I could install WordPress on my own website and learn about all the bugs that are in that interface, just for a nice change of pace.

At least if I’m paying WordPress I’m no longer the product being sold, but the customer being served. Food for thought.

Stuck in Mobile Interface Hell

Mobile apps are so kludgy. Why is it apparently impossible to make a mobile app that can produce content that can dance and sing like  desktop applications do? The Tumblr app will not let blog posts tap the power of the social web by drawing content from other websites and displaying it as it does on the desktop/browser interface.

At least I can access the code with the Tumblr app. The Blogger app cannot give me access to HTML code at all as far as I can tell. Don’t get me started on how the Facebook app can’t let go of content, even when you tell it twice to let go.

Yes, view in browser. No, I mean a real browser. No, I mean Chrome!

Why do I have to argue with Facebook programming on my own phone? The Blogger app can’t find my photos. Tumblr can’t multi-media code unless you can do it all from memory (I can’t) and the Facebook app? Zuckerberg isn’t getting the blogging part of my soul. He already has too much of the rest of it.

This is hell. I want my desktop back. Now please.

Jean-Luc Picard programming binary code from memory
into Data’s severed head in Time’s Arrow (Part 2).
I cannot program on this level, but I do know people who can.

Hey Google! Blogger Interface Needs a Patch!

For the last few weeks I’ve been getting spam comments from Blogger. Yes, that’s right. Blogger is spamming me with comments, if sources for the spam are to be believed. The problem is a little more involved than that.

Not only is the self-identified user Blogger spamming me, but the landing page for marking comments from blogger as spam still references the old blogger developers blog that hasn’t been updated since 2013!

Now, I understand. I rejected Google’s G+ comments interface. I post to G+ for blog promotional purposes (as limited as that is, I’ve seen the metrics) and I got tired of seeing my own posts listed as comments on the blog articles. It makes you feel lonely and pathetic when you are the only one posting comments to your blog. Yes, maybe that is because I am lonely and pathetic, but I don’t need reminders from my blog interface to realize this potential fact. So I moved back to the native blogger comments.

If they want me to use G+ as the only commenting form, perhaps they should fix the G+ interface to import old blogger comments properly; as in, not showing the obvious HTML code inline with the comment text. Give me the option of not showing my own posts to G+ as comments on articles. Something. Anything.

But please Google. Please. I’m begging here. Clean up the old Blogger interface? Make links go places that are still in use? Keep clearly proprietary user names reserved for Blogger and Google not to mention Alphabet, the new parent company and all the other companies that Google now Alphabet owns. At the very least, can you kill the spammers account? The fake Blogger? Please?