kata Drew

This post is going to be similar to a previous post which I published concerning the phrase “so therefore.” There’s further discussion of “so therefore” over on the WordReference.com forums where I started a thread about it.

Today I would like to talk about talking about blogging. There seems to be some confusion. I hear people, most commonly professors at my school, refer to individual blog posts as a blog. This is not only incorrect but misleading. Consider the following:

“Yesterday I read a new blog by Al Mohler.”

Upon hearing this phrase I immediately begin to wonder whether Al Mohler has started blogging at a new location other than albertmohler.com because “blog” and “a blog” usually refer, in a collective sense, to an entire set of blog posts. For example, you are reading my blog at KataDrew.com. Specifically, you are reading a (blog) post entitled “How to Talk About Blogs” on my blog KataDrew. You are not reading a new blog on my blog. That is imprecise, for I only have one blog and it is at KataDrew.com. My blog is, however, made up of many posts.

Posts are the specific, individual units which make up a blog. If I may belabor the point futher: blogs do not make up blogs but posts make up blogs. Note in the images herein displayed the usage of the word “post” in one blogging platform’s administration section (Wordpress).

One possible exception is an aggregated group blog such as that at Said at Southeastern (sebts.blogspot.com) which aggregates posts from several different blogs to make up it’s own blog in a sense, though it has it’s own posts. Still, you’ll want to refer to a post you read on Said at Southeastern not a blog you read on Said at Southeastern.

So to rephrase the initial above-quoted example to be correct and precise you’ll want to say something to this effect:

“Yesterday I read a new post on Al Mohler’s blog.”

Or

“Yesterday I read a new post by Al Mohler.”

May this help you avoid not only a personal pet peeve of mine, but imprecise language attendant with using “blog” to refer to both a blog and a post on a blog.

I’m at Wordpress 2.7-hemorrhage but my widgets page isn’t working. That is, none of the buttons “click” (add, remove, or show sidebar).

===

Solution: read on the WordPress forums where I posted and, with help, worked out a solution: http://wordpress.org/support/topic/201325

This is only a test for Facebook.

After seeing all the flummery about the new Wordpress 2.5 and the screen shots of the the admin section, I decided to dive in. Actually it wasn’t that straight forward. Upgrading always makes me nervous. So, I upgraded via svn a test blog I keep tucked away online. It worked like a breeze. Praise the Lord for svn. “Svn up” and you’re done. I then decided to svn up this blog, but the oddest thing happened, or didn’t happen: “svn up” doesn’t work on this blog. On my test blog it automatically grabs the latest beta/nightly release and upgrades, but the “svn up” doesn’t work on this one. I’m bewildered. I read something about checking the file and directory permissions for a solution, but that didn’t help though several files and directories needed their permissions changed. Svn didn’t fail me totally with this blog though. Instead of svn up I used “svn sw http://svn.automattic.com/wordpress/trunk/” and bingo. Why “switch” works and not “update” is beyond me; nonetheless, Wordpress 2.5 release candidate 1 is up and going with a beautiful, slick back end. All my plugins are still working as far as I can tell. Well done, Wordpress.

Upgraded to Wordpress 2.3 in about 10 minutes through subversion and command line. Subsequent upgrades should just happen in a snap; I just had to get my installation switched over to subversion. Switching over was a breeze and will save a lot of time and hassle in the future.

Wordpress, Gutenberg would be proud!