Our proceed with WordPress has regularly been to have it run on usual server configurations. We wish users to have coherence when selecting a horde for their changed content. Because of this strategy, WordPress runs flattering most anywhere. Web hosting platforms, however, shift over time, as well as we spasmodic have been means to reevaluate a little of a mandate for regulating WordPress. Now is a single of those times. You substantially guessed it from a pretension — we’re eventually ready to make known a finish of await for PHP 4 as well as MySQL 4!
First up, a proclamation that developers unequivocally caring about. WordPress 3.1, due in late 2010, will be a final chronicle of WordPress to await PHP 4.
For WordPress 3.2, due in a initial half of 2011, we will be raising a smallest compulsory PHP chronicle to 5.2. Why 5.2? Because that’s what a immeasurable infancy of WordPress users have been using, as well as it offers estimable improvements over progressing PHP 5 releases. It is additionally a smallest PHP chronicle that a Drupal as well as Joomla projects will be ancillary in their subsequent versions, both due out this year.
The numbers have been now, finally, strongly in preference of this move. Only around eleven percent of WordPress installs have been regulating on a PHP chronicle next 5.2. Many of them have been on hosts who await PHP 5.2 — users merely need to shift a sourroundings in their hosting carry out row to turn on it. We hold that commission will usually go down over a rest of a year as hosting providers comprehend that to await a newest versions of WordPress (or Drupal, or Joomla), they’re starting to have to lift a trigger.
In reduction sparkling news, we have been additionally starting to be dropping await for MySQL 4 after WordPress 3.1. Fewer than 6 percent of WordPress users have been regulating MySQL 4. The brand new compulsory MySQL chronicle for WordPress 3.2 will be 5.0.15.
WordPress users will not be means to ascent to WordPress 3.2 if their hosting sourroundings does not encounter these mandate (the built-in updater will forestall it). In sequence to establish that versions your horde provides, we’ve combined a Health Check plugin. You can download it manually, or make use of this handy plugin installation apparatus we churned up. Right now, Health Check will usually discuss it we if you’re ready for WordPress 3.2. In a destiny recover it will yield all sorts of utilitarian report about your server as well as your WordPress install, so cling to on to it!
In summary: WordPress 3.1, due in late 2010, will be a final chronicle of WordPress to await PHP 4 as well as MySQL 4. WordPress 3.2, due in a initial half of 2011, will need PHP 5.2 or higher, as well as MySQL 5.0.15 or higher. Install a Health Check plugin to see if you’re ready!
See a strange post:
PHP 4 as well as MySQL 4 End of Life Announcement
.gif "Learn A Z of WordPress Plugins – Beginner’s Guide")