Category: WordPress

In a belated celebration of the release of WordPress 1.5 (or is it in early anticipation of 1.5.1?), I will set upon seven days of plugins. Seven days of at least one new plugin a day AND the update of at least one of my existing plugins a day (at the end of the seven days, all of my existing plugins will have been updated). Expect more than just seven new plugins though.

Had a chance to comb through some of the latest WordPress 1.5 code (through 2005-01-05) in CVS, both in the course of a fresh install and in the course of code analysis for development of some new plugins. Spotted a few things that would benefit from improvement (nothing critical).

A list of things I’ve noted, provided, or want to inquire about to help contribute to WordPress v1.3 (or as ideas for future versions), roughly in ascending order from trivial to implement to complex.

Bug 0000113 is titled “Post content ‘lost’ if multiple <!–more–> (more…) tags used“. Which basically says that if more than 1 <!–more–> tag is located in the content of a post, you’d only ever see the text up to the second <!–more–>. All subsequent text, though still part of the post content in the database, will never be displayed. The fix is extremely simple:

In wp-includes/template-functions-post.php, in the function get_the_content(), change this line:

$content = explode('&lt&;!--more-->', $content);

to this:

$content = explode('&lt&;!--more-->', $content, 2);

The third argument to explode(), the limit arg, was introduced in PHP 4.0.1, and since WP supports PHP 4.1, the fix should be valid. This way text before the first <!–more–> will be put into $content[0] (as expected), and all other post content, regardless of subsequent <!–more–> tags, will be put into $content[1] and therefore not “lost”.

Here is the patch (modified from, and then compared against, the latest WP 1.3 from CVS).