I’m replying to comments on my UtopiaMechanicus.com website, and I’m thinking – “why don’t I see those fancy nested comments like elsewhere?” You know, the ones that allow you to reply directly under any comment, and then reply to that, and so on, instead of adding a reply to the very end, and hoping somebody figures out you were answering them?

First step is to use a newer theme – this feature was added around WP 2.7, so themes before that time simply won’t show nested comments. The good news …

WordPress has a nice new theme, TwentyEleven, that I liked so much I’ve added it to some of my sites.

However, one issue is that little gray bar that appears at the top. Normally it’s not a problem, but when I use the dark display (as I did on UtopiaMechanicus.com) it becomes quite visible.

If you have the same problem, here’s how to turn it off – just edit your style.css file for the theme, and look for this text:

#branding {

border-top: 2px solid #bbb;

padding-bottom: 10px;

position: …

Shortcodes are little codes that plugin developers can use to add features, generally in the article text. For example, my post on syntax highlighting required custom shortcodes for language display (like [c]).

Here’s the problem: since shortcodes are meant to DO something, how do you go about documenting them?

Well, one option is to use a double entry, like this:

[[c]]

WordPress understands that you are not using a shortcode, simply displaying it, and it will correct the issue, giving you the display of [c], and no activating.

However, what if …

Unable to save a WordPress post with an image in it? This happened to me, along with the 406 error “An appropriate representation of the requested resource could not be found”. Here’s how I fixed it, via MOD_SECURITY.

It’s WP update time, and I’m upgrading to 2.9.2 – not a huge hardship, since it’s all one-click now (unless there’s a plugin conflict, of course). However, a problem arose: one of my blog disappeared completely. Nada. Nothing. Just a nice white page, without anything whatsoever.

In the end, it was because of old wp-cache-config.php and advanced-cache.php files in my /wp-content/ directory. Briefly, these files caused a cache issue that was not needed on this blog. Remove them, and the blog was AOK.

The reason for mentioning this? I …