Part of my new troubles with WordPress came from having installed Noscript at the same time. But not the most important parts: The Add Media button seems to simply not do anything anymore. I can upload pictures, and I can manually tag text, but adding pictures to a post – which I like to do a lot – manually requires tedious coding with uncertain results as in below. At least I got the preview page back.
Why did they do this? Could they at least have the decency to provide a simple way for a non-computer geek to undo it if I install an update and it turns out to be a turd sandwich? I was perfectly happy with the earlier version. Damn my impulsive trust in WordPress not to torpedo their own product.
Now I’ve got to go do a great deal of work. The picture above was taken on top of the ridge above the Secret Lair’s hollow. D doubted his ability to get a gigantic pickup and large flatbed down to the cabin without wrapping the whole thing around a juniper, and in fact refused to try. So we unloaded the trailer at my favorite turn-around spot on the ridgetop, and now I’ve got to make two or three trips with the Jeep trailer. Then there are a few other things I want to wrap up to clear the deck for the big cabin siding job, to commence next week sometime. Technically I can do the sawing with my house power, but possibly not all at once or at the time I want to. One cloudy day could sabotage the whole thing. So we’re going to need D’s semi-portable generator for saws. While we’re at it a second good ladder would be nice, and I still have to deal with the balcony and upper door, et cetera. Much to do.

















































Just realized something. I have an aggressive pop-up blocker. I am obliged to disengage that feature in order to use many of the formatting buttons in my wordpress blog, specifically the feature that allows me to add images. You may need to disable adblock and pop-up blockers temporarily to use them. Worth a try, maybe. 🙂
“Damn my impulsive trust in WordPress not to torpedo their own product.”
The problem with software writers is that they have little connection with or care for their users, otherwise they would just leave things alone, other than fixing bugs. I hate, hate, hate the constant gratuitous fiddling with user interfaces, just to add some gee whiz factor, breaking the familiar flow of work that we are used to.
the hardest, and assuredly the most tedious, thing that a software writer ever has to do is debug code that somebody else wrote (which is about 99% of the code they need to debug). They would MUCH rather write new shiny whizzy things. This virtually ensures an unwieldy, buggy product that looks great, but functions poorly.
As Paul says, they have little connection to their own products, and see no issue with forcing the users to conform to their ideas of what an interface should work like. THEY don’t have to climb up a learning curve, THEY wrote it. And in many cases they don’t really know how to run the stuff they are writing. Their job is so granular that they don’t see the big picture.
I saw this all the time back when I worked for a company that wrote software. Time after time, I would write a bug, and the reply would come back…’that’s not a bug, you need to file a feature request to change it’. The software was crashing during *training* sessions with important clients. I eventually gave up and stopped writing bugs altogether.
Maybe that’s why they laid me off.
Two questions:
With NoScript installed, did you manually allow wordpress.com? (You should.)
Are you using the old style editor ot the new “beep beep boop” “improved posting experience?” (Use the old; the new one is buggy as h/e/l/l/ DC.)