WordPress.org

1.0.5

Internet Explorer 7 and up will not display the 'object' element (e.g. embedded flash content) when its dynamically inserted. If that is the browser in use, and if an 'object' element is found in the new content, the page will immediately redirect to the single post display (instead of expanding to show the new content).

The expand/collapse animation with 'object' elements looked pretty bad. Now, they are not shown until AFTER text has expanded. When collapsing, they are hidden BEFORE the text begins to move.

Using the proper 'is_admin' WP function to keep plugin out of the admin area. This was previously done with a PHP 5 only string comparison function against the URL. If the server was still using PHP 4, this function would break things.

1.0.4

Method used to obtain plugin's root directory no longer worked with 2.8.1 update. It has been changed to use the new:

    plugin_dir_url(__FILE__)

This change means that the minimum version of WP now required is 2.8.

1.0.3

Wordpress 2.8 updated its included version of jQuery to 1.3.2. This required a very minor change to the plugin javascript code. The new jQuery version provides a much smoother animation of the content into and out of view.

For those interested (and because I have no idea why this broke), the change in code was essentially creating the new content with this:

    $j("<p>").html(newContent);

instead of this:

    $j("<p> + newContent + </p>");

1.0.2

Almost immediately after releasing 1.0.1, I became aware of the 'wplocalizescript' function (see Best practice for adding JavaScript code to WordPress plugins). It negates many of the javascript changes implemented in the previous release and offers a much better solution.

1.0.1

Plugin would not function correctly with installations in which WP is used as the root of the domain but the actual WP installed files are within a subdirectory of the root (see codex Giving WordPress Its Own Directory). This has been fixed (thanks to Thijs for the heads-up and solution).

Part of the fix means that the full plugin path used to get the animated "loading" image is retrieved as an AJAX call. If the user clicks a "read more" link before that call has completed, there will be no GIF associated with that link (but the content will still be pulled and expanded for the user).

1.0.0

Initial Release