After years of hopping from one dying and broken plugin to the next, it’s time to stop the chase and return to running a monolingual blog.
Although it’s only slated for release sometime in May, the first beta of the new WordPress 3.0 is already doing the rounds. Blog Oh Blog has a nice summary of the changes and additions in the new version: most of the updates are fairly innocuous, perhaps the largest mention should go to the integration of WordPress-mu, for setting up multi-user blogs and networks.
However, the announcement that really put the cat amongst the pigeons has been that the core development team may now be promoting what were formally called canonical plugins, now known as core plugins following the unpublished results of a poll in December. It appears that whilst attempting to address a genuine issue, the very idea of having plugins that stand in the limelight with an official stamp of approval has incensed many community plugin developers.
Some really excellent debate has been held which has, amongst other things, revealed that the initial go ahead for core plugins will be very limited; just three plugins, including an old, out-of-date plugin, a chunk hived off from the core, and a newly developed plugin. Nevertheless, the potential for these core plugins to have wide-reaching effects on the plugin development pool, create stagnation in the community and a greater top-down hierarchy is something that in the eyes of many developers and enthusiasts, has not been addressed.
Fixing blank pages in WordPress caused by embedded theme links in the wp-config.php file.
After initially solving my database character encoding problems by ignoring the specific strings in the wp-config.php file, I was finally forced to alter the characters in the database during a recent reshuffle. Whilst there are two automated solutions available via plugin, namely g30rg3x‘s UTF-8 Database Converter and the Modified UTF8 Sanitize Plugin, sadly neither worked in my particular instance, and indeed the former is no longer supported for current versions of WordPress, though reports on the WordPress support forum suggest there should be no issues.
Fortunately, an excellent guide was available on Alex King’s blog. For more information and follow-up comments, you should definitely read the full post, but here’s a summary of the method that worked for me.
With the latest 2.7 release barely out of the door, the WordPress team are already…