Year: 2008

My good friend Ozh has written an article entitled, What Plugin Coders Must Know About WordPress 2.6. It is a good read if you are a plugin developer for WordPress.

Both of us have came to a conclusion that if you move your /wp-content/ folder to elsewhere, you may need to manually specify the path to wp-config.php in the respective plugins that make use of them as there is no 100% way of guessing the path to wp-config.php.

So my recommendation is DO NOT MOVE the /wp-content/ folder. It is OK to move wp-config.php to a level higher, but try not to touch /wp-content/.

With regards to my plugins, I will release a .01 update bringing the version to 1.31 and 2.31 for the respective plugins. This update will make sure that the plugin will work for BOTH WordPress 2.5 and WordPress 2.6. That is right, I will maintain backward compatibility with WordPress 2.5 for the next update as WordPress 2.6 is just a minor release.

When WordPress 2.7 comes out in November 2008, I will bump all the versions to 1.40 and 2.40 respectively and I will remove the backward compatibility feature to WordPress 2.5.

I have downloaded WordPress 2.6 Beta 1 and installed it. Not much difference from WordPress 2.5 in terms of the layout.

Now on the extreme top menu on the extreme right, there is a link called “Speed up!” which links to Google Gears.

In the Dashboard, right under “Right Now”, there is a comment break down added to it. Here is an example: “You have 1 post, 1 page, contained within 1 category and 0 tags. Current comment break down: 1 total, 1 approved, 0 spam and 0 awaiting moderation.”

When you write a page or post, underneath the “Save” and “Published” button, there is a word count indicator.

The display of themes under “Available Themes” has also changed a little.

Now back to serious business.

I am still deciding whether or not to maintain WordPress 2.5 compatibility for the next wave of updates for my plugins as WordPress 2.6 introduces a lot of constants like “WP_PLUGIN_URL”, “WP_PLUGIN_DIR”
“WP_CONTENT_DIR”, “WP_CONTENT_URL”, etc.

2 potential issues that would break my plugin in WordPress 2.6 and I will be unable to fix it unless I find another way to do the AJAX, “Allow wp-config.php to exist one level up from WordPress root directory”
and “Allow wp-content directory to exist in a custom location (not relative to ABSPATH)“.

Argh! WordPress 2.5 has the shortest development cycle!