Formatting frustrations

Gah. I just spent a considerable amount of time doing the layout and formatting for the first plugin post, and I discovered a few frustrating aspects of WordPress’s formatting:

  1. When saving/publishing an entry that is in need of a closing tag, WordPress seeks to close it for you. Appreciated behavior, when it works properly. I’ve found that if a close tag is not present and WP inserts it for you, it is sometimes either (a) in the wrong spot (i.e. closes a mid-list <li> at the end of the <ol>/<ul> -or- (b) worse, it eats up some of the entry text in doing whatever it was doing. There is already a bug tracker item on this.
  2. If I had continued that lowercase sublist and put in a ( c) [without the space before the ‘c’, I would’ve wound up with a ©, which I wouldn’t have wanted. This is a result of wptexturize() (see next item)
  3. I was having a hell of a time figuring out why I was getting curly quotes for all single- and double-quote characters. Checking out the source of the page in my browser, I saw that single-quote characters were replaced with either &#8216; or &#8217;, and double-quote characters were replaced with &#8220; or &#8221;. This was when I discovered that wptexturize(), in /wp-includes/functions-formatting.php, was the culprit. As a result, I wrote a mini-plugin, wpuntexturize (the plugin is being pre-linked since I haven’t created the page for it yet as of this posting). The mini-plugin goes back and reverts some of wptexturize’s changes to what I had used originally. I could just as easily have commented out those four lines in the function and be done with it, as well as spared the processing of the replace and unreplace, but I’m currently of the mindset to limit modifications to the core files as much as possible.
Package/plugin/module WordPress

Plugin: Category Image(s)

This plugin has been updated! Comments to this post are now closed. For the latest download, documentation, and link for posting new comments related to this plugin, visit the plugin’s new homepage at:
Category Image(s)
Scott Reilly
Last updated:
17 May 2005
Displays image for each category associated with a post. The number of images displayed can be limited, and the image file extension type and file location can specified.
Package/plugin/module WordPress

WordPress: Plugin Development

In making the conversion from Movable Type to WordPress, I had need and desire to create an assortment of plugins. Since my priorities were to convert various other of my sites prior to creating this newest techblog of mine, I haven’t been able to make said plugins available to others. Now that the site is more or less ready for prime time, I find myself with a bit of a backlog of plugins to unveil.

The complete list of the plugins I have developed is available at coffee2code WP Plugins page, which will be kept updated. It’ll link to more in-depth plugin-specific pages that will actually be specially formatted weblog entries, which too will be kept updated.

Feel free to peruse, use, and offer me feedback!

Installation/configuration User WordPress

Conversion from Movable Type to WordPress

I’ve converted Movable Type to WordPress four times now (two sites, initially converted for evaluation purposes, then converted for real). Here’s the essense of what I did, the customizations I made, and what I encountered:

Installation/configuration User WordPress

Installation of WordPress

Here’s the fully enumerated steps undertaken to install WordPress.


Switching from Movable Type to WordPress

The recent flap over the release of Movable Type 3.0D and the associated license agreement had caused me to pause and reflect on my usage and satisfaction with MT, and in so doing to consider alternatives. And for me, what I saw different from when I first shopped around for weblog software three years ago was that a wider variety of applications are now available. After a review of many of them, I decided to go with WordPress.

Cons of MT: open code but not open source; PERL-coded; static pages required inordinate amount of time for rebuilds, new post posting, and comment posting; stagnated for years with regards to the number of new features; a pain to customize the code to my liking.

But, it was free enough. Not any longer, not after I’ve seen the alternative.

Pros of WP: open source (GPL); PHP-coded; zippy performance; active and friendly user and development community, with regular participation of the core developers; a vital and growing user and developer base; easy to use, easy to customize; interface is more to my liking.

For some reason WordPress has me fired up in a variety of ways. Maybe I’m picking up on some of the energetic vibe of the WP community. I’ve already begun converting some of my weblogs over to WP and plan to finish converting them all soon. I started this site, a tech link and info weblog, in part because, unlike my time as a user of MT, I am keen on contributing to the development of the weblogging application.