It seems just yesterday when I needed the Happiness Engineers of WordPress to get my pingbacks working … and then to get my reblog functions repaired. Well … It’s déjà vu all over again, as Yogi Berra said.
I have changed the look of Serendipity. Again. I am pretty sure I’ve gone through at least a dozen templates since I started blogging more than four years ago.
Why? Because I’ve had a series of issues for the last three or four months. Some minor ones, others not so minor. All of them required intervention which, to WordPress’s credit, they have worked through and fixed.
I am convinced at least some of them are glitches connected to the Wilson theme I have been using. This isn’t the first time I’ve had a template “go sour.” I have a theory about this. I cannot prove it, but I believe it’s true.
WordPress is forever messing around with their software. These changes affect not only what they intend, but have many unintended “side effects.” Like the way the new software affects individual template functions. They don’t do much (any?) beta testing. Like so many other big software companies, they make changes, throw the new version out to customers and let us find the problems for them.
I hate this casual attitude toward properly testing software. I resent it as do most serious technology users. But apparently testing new versions of software is not included in the development budget. Plenty of money to develop and not one cent for testing. Aggravating.
So, after I’ve been using a theme for a few months, glitches start appearing. It’s like playing Whack-a-Mole. You smack one problem down, another pops up. You whack that one over the head and out of the game, and three more spring from holes in the ground.
After a while, you figure “Okay, time to change games.” Or, in this case, templates.
This theme is “Untitled” and it displays pictures well and large. I’m not sure I like the way it handles text, but I will give it a chance. There are a lot of templates. I haven’t tried all of them. Yet.
From the WordPress.com monkeys to you! Yes, folks, this is my very own personalized summary of this past year in blogging.
I have never been to the Louvre, but it’s good to know that my followers are filling its halls.
The Louvre Museum has 8.5 million visitors per year. This blog was viewed more than 115,000 times (not 110,000) in 2015, but you probably already knew that.
If it were an exhibit at the Louvre Museum, it would take about 5 days for that many people to see it.
Wow. Or they could just visit the Rodin exhibit. Or the Mona Lisa. I’m sure my blog would not be the main attraction at the Louvre on any day of any week of any year.
Actually, there were 1,206 new posts, growing the total archive of this blog to 4,206. No one knows how many pictures I posted because I don’t know.
365 days, from 1 January to 31 December. They could have merely said “every day.” And more than once most days. Which is why I really need a break.
Friday (Really? Wow!) 185 posts total. I have no idea why I posted more on Friday, but I think it may be because that’s the day the WordPress Photo Challenge comes out.
You can click here to see the complete report, but I figure you’ve already seen more than you have any interest in. Since WordPress kindly supplied this lovely, official document, I might as well make use of it, right?
Yesterday, WordPress decided even though I had previously and continuously elected the “old” stats page, now, I am going to use the new, confusing stats page.
I created a bookmark to get me back to the original stats page, but this is better!
Today, Dennis published the directions for using a script — a workaround to bring you back to the original page — where you can get the information you want in a way that makes sense.
The script was written by tPenguinLTG. The instructions are from Dennis and this is a reblog. I did not write this post, but I will guarantee that it works perfectly with Chrome. As do the earlier scripts which take you back to the old editor. Thank Dennis, not me. And tPenguinLTG who keeps coming up with fixes for the “updates” from WordPress!
The Solution To Use The Classic Stats Page
If you are blogger at WordPress.com, you might have noticed it, there are not much ways anymore to access the beautiful classic stats screen, instead we are now forced to use the new one, but there is help! Do you remember when they forced us to use the incredible hard to use new post editor? I wrote a post where you can learn how to get back to the classic editor, and there is a very similar solution to get back to the classis stats screen. We will talk about this now, in this post you will learn how to get back to the classic stats page.
How To Force A Redirect To The Classic WordPress.com Stats Screen
Before we start, I want to mention that the solution comes from tPenguinLTG, be thankful there and not here, I do just…
View original post 432 more words
This is from the script’s originator and contains everything for all the browsers that will work with the fix, for PC and Mac.
The Penguin has done a bang-up job. He explains everything clearly and anyone can follow the directions, even those of us who are somewhat technically challenged.
tPenguin has included workarounds for Safari (native to Mac) and Internet Explorer (native to PC), as well as all versions of Chrome, Firefox, and Opera.
If you are still battling to keep blogging despite the incomprehensible determination of WordPress to make it impossible, you need to use whichever of these scripts will fix your problem so you never need face “BEEP BEEP BOOP” again.
And ever would be far too soon for me.
May the Force be with you. And thank you again, Penguin. You have saved us from the WordPress soul and blog destroyer. We will be forever in your debt.
If you are struggling with the horrible new interface WordPress is forcing on you, here’s a workaround. This is a reblog. Actually, it’s a reblog of my original reblog published in March, but apparently many people missed it.
Share it with your beleaguered WordPress friends!
Update: I heard from the script author and this is what he says:
Hi Marilyn, I’m the author of that script that you use. I’m glad you’re finding the script useful, and thanks also goes to Dennis for spreading the word.
I noticed you said in a forum post that “This redirect does NOT work on Mac, sorry”. Could you please elaborate on that? It might be more difficult to get working on Safari, but it works just fine if you use Firefox or Chrome, both of which are available for Mac.
The Solution To Use The Classic Editor
If you are blogger at wordpress.com, this post here will help you to solve a big problem. As you have noticed, the decision makers at WordPress want to force you to use the recent new editor interface that is purely designed for mobile devices and for users who only create short-form content. This is of course a pain if you are desktop user and if you like to create long-form content as well. In this post you will learn how to get back to the classic editor permanently.
In the new editor form, we had a link back to the classic editor but that link is now gone too. WordPress does not have the intention to give us the link back as you can read here in the forums. If you go through this huge forum thread, you will find out…
View original post 717 more words
While I wasn’t looking, WordPress turned off about half the blogs I follow. I had reduced the frequency of notifications from instant to daily, but I guess WordPress was feeling helpful, so they further reduced it to nothing at all.
I thought maybe everyone was on vacation or had given up blogging. At the same time.
So I’m back and so are you. Just so you know.