…so I applied the fix for a bug that I didn’t think is one. I first noticed this bug when I wrote instructions for my plugins. The instructions included the symbols < and >. At first, I thought it was just Exec-PHP clashing with whatever I wrote on my page. So I used HTML character codes. This style worked. However, when editing the page with the HTML character codes, I found the symbols to be just that, symbols, when it’s supposed to be HTML character codes. It parses the code when it’s not supposed to. But I didn’t know that. I thought it was always that way. And that this is the first time I had to do it so it was just recently that I found out about it. A moment of Zen, if I may.

But ever since releasing my plugins and hosting them on WordPress, I made it a habit to check the WordPress Planet feed. There I read about Ryan’s post about WordPress 2.3.1 beta 1 being available for download and that there were a number of bugs fixed, including the bug mentioned above.

And because I update my pages (almost frequently and on a regular basis) that includes those HTML character codes, < and >, I just had to apply the bug fix. And now, the bug is dead. For me at least. Now I realize how important it is to upgrade or update software. Because it addresses issues that one just might run into someday.

After this, I also had a chance to play with a new Thing by Christine from the Internet. The Inline Tag Thing is awesome, as it gives you the ability to manage tagging your posts without ever having to go in to the Admin area of WordPress. Well, as long as you are logged in and allowed to edit the post, you can. She also added a feature that answered a lot of people’s prayers: a dropdown list of available/existing tags that can be reused to tag the post. I just love the simplicity of this plugin.

Now if only my blog can get me coffee. Hmmm.