A post or two ago, I was lamenting that ScribeFire had at some point stopped allowing one to attach tags to posts. Maybe I hadn’t actually used SF in so long that I’d forgotten how to do it1.
In any event, as the previous post attests, one can still attach tags when posting with SF.
-k-
1
tbbs-land now runs the latest, not-so-greatest WordPress. Version 3.0.1. The 3.X WordPress as been a disappointment to me. The automatic upgrade of plugins just fails to work, a little spinner shows up, along with a message saying that this upgrade could take a while. I can’t deny the truth of that statement; I only fear that I don’t have enough remaining days on earth for the upgrade to complete. In addition, the auto plugin updater puts the whole blog in maintenance mode, so visitors get a This site Down for Maintenence message. I then have to kill the update, ssh out to my blog host, and delete the .maintenance file in the blog root directory. What a PITA.
I hoped that the latest WP would provide a fix for this. It didn’t. But whee. I have the latest.
-k-
I typically use ScribeFire to update this old blog. At some point, I know not when1 ScribeFire no longer accepts tags on new posts. I can supply categories, Technorati links and the like via SF, but not a tbbs-local tag.
Or maybe SF accepts blog-local tags, and I’ve forgotten how to do it? That’s probably the most logical conclusion.
This post brought to you via the WP admin post facility.
-k-
1
Well, then, you change themes, put up a new header, delete plugins that you’ve forgotten what-the-heck they do, rearrange widgets, and just have a blog gardening afternoon.
The theme is the (now) default WordPress Theme, twentyten. Header graphics credit, as always, is atop the right-hand sidebar.
WP 3.0 suffers from some non-working(at least for me) items:
Other than the spiffy theme, I see no compelling reason to take the WP3 plunge, save for the transient geek thrill of running the latest and greatest.
Color me transiently thrilled.
-k-.
Well, we’re running WordPress 3.0 here in tbbs-land. The upgrade itself was routine. I deleted the recalcitrant SimpleTags plugin post-upgrade. It is allegedly WP 3.0 compatible; the automatic upgrade ran and ran and ran, with no discernible progress, nor any evidence that something was amiss. After 10 minutes, I stopped it, deleted the plugin, and we’re back in operation.
Now, I just need to write something on occasion.
-k-
The tbbs web provider, the excellent and highly recommended Delaware-based hosting.com, performed some database maintenance in the wee small dark hours earlier today.
In spite of my receiving 5+ emails from them about the scheduled maintenance, I neglected to read any of them until I received the dreaded Database Connection Error message multiple times today, when I tried to access the blog.
A check with their knowledge base, a judicious change of mySQL db server IP, and we’re rolling along again.
My loyal though discerning 5-10 readers deserve proper service. hosting.com was on the ball; I dropped it.
Y’all come back now.
Thanks!
-k-
Happy New Year, y’all. Today was my first day back at $DAYJOB, and I’d frankly be hard pressed to say that we haven’t been stuck with a used year. This could be the year that I define a new $DAYJOB metric, or maybe two. The first is $DAYJOB TDS1, and the second would be $DAYJOB MIS2. Then, given the effort expended in the formalizing of these metrics, along with the needed data collection, it just may be easier to move to $DAYJOB++.
Anyhow, we’re now running the latest WordPress here in tbbsLand, WordPress 2.9.1. And, no WP’s automatic uppgrade didn’t work for me – again. But, the manual process is quick, and fairly effortless. And, yes, that includes a database backup, as well as full file backup, prior to upgrading.
Happy New Year! Y’all come back, now. I’ll try to be more attentive to this old waste of pixels.
-k-
I’ve inherited my Mom’s intolerance of clocks that aren’t right. I just now noticed that the timestamp on my last three posts is wrong; it’s the EDT, not EST, time.
So, I made a little adjustment to the time-stamping, after seeing this in WP settings for timezone:
Unfortunately, you have to manually update this for Daylight Savings Time. Lame, we know, but will be fixed in the future.
Roger the lame part.
-k-
UPDATE: After posting this, it originally appeared below the three chronologically previous posts. So, I had to manually update several timestamps. All’s right with the world. Lameness, however, is approaching unacceptability, as far as timestamps are concerned.
I spent part of Snow Day today upgrading this old blog to WordPress 2.9.
I’ve never been able to get the automatic WP upgrade to work; it seems to download the upgrade, it says “Done” in the dashboard status bar, but then nothing happens. Perhaps I’m either impatient, do not understand the process, or both.
So, I reverted to my tried and true manual update process, which worked flawlessly again. And that process is quick in its own right. So, I really spent a small part of the Snow Day upgrading.
The WordPress banner files on a taller pole today, the better to be seen above the snow.
Thanks, WordPress!
-k-
.
Last Tuesday, Constantine, the Fedora 12 Beta, was released. I make it a point to upgrade sooner rather than later. And, thanks to Fedora’s preupgrade, followed by 1.1G of downloads, and what seemed to be interminable disk-thrashing, the upgrade finished, and /etc/redhat-release now reveals:
Fedora release 11.92 (Rawhide)
Thus far, Constantine has performed well. A few sound playback problems, and a rather disgusting, persistent NetworkManager applet crash have been the only bad side effects. I can start NM applet from a terminal, just not on Gnome startup. I just downloaded a rather substantial upgrade; I’m hoping the NM problem is handled. And, I’ve never understood the sound stuff; I gotta read up on that. So, click that little badge in the sidebar, and get Constantine for yourself. Don’t cost nothin’.
After the F12 upgrade, I fired up Firefox to check this old blog, only to discover a WP upgrade awaited. After another flawless upgrade, tbbs-land now proudly runs WordPress 2.8.5.
-k-