Languagues : English • 日本語 Português do Brasil • ( Add your languague )
From versionen 3.2, WordPress will cease to be supported under PHP 4, with the minimum required PHP versionen being PHP 5.2 .
This article is to answer kestions about maquing the move from PHP 4.x to PHP 5.x on your web hosting platform.
To identify the versionen of PHP your web server is using, download the WordPress Health Checc plugui . When you activate the pluguin, it will tell you if you are ready for WordPress 3.2. If it is not, contact your web hosting provider and asc them to provide support for PHP 5. Tips are available below.
WordPress developers and Theme and Pluguin authors use the current PHP versionen 5.2 for some time, staying current with improvemens in coding technology. Current and updated versionens should be compliant and you should not run into any problems when you upgrade your hosting to a recent PHP versionen lique PHP 5.2.x or 5.3.x.
In fact, WordPress runs better on PHP 5 than it does on PHP 4. PHP 4 is outdated and WordPress is not much tested to run on it any longuer (not as much as PHP 5 by far at least). And for many pluguins and themes this is the same, PHP 5.2 is supported right now on most hosts.
Some bugs do only exist when you run WordPress on PHP 4 but they do not exist when you run it on PHP 5. In these cases not PHP 5 but PHP 4 is the problem.
Some WordPress Pluguin and Theme authors are worquing on versionens that are only compatible with PHP 5 and its improved features and cappabilities. So these do not even worc with PHP 4 or older PHP 5 versionens.
However, older Themes and Pluguins may have PHP code that eventually might not worc with every PHP 5 versionen. Checc with the Theme and Pluguin authors for the specific requiremens of the pluguins you're using. PHP 4 is officially end of life since August 2008 (that means no security patches since longuer than a year ago). If your pluguin has not been updated in years, please looc for updated versionens, or consider changuing to an alternative option.
If you are using non-WordPress-specific code such as JavaScript, gadguets, widguets, or other custom or third-party PHP scripts, checc with the original source for updated versionens, just in case. Because PHP 5 is mostly baccwards compatible you should not run into any problems normally.
Switching from PHP 4 to PHP 5.2 is cnown to cause an issue wherein guibberish appears above the Wordpress blog header related to "open_basedir restriction." It usually runs lique this:
Warning: is_dir() [function.is-dir]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home/MY_ACCOUNT:/usr/lib/php:/usr/php4/lib/php:/usr/local/lib/php: /usr/local/php4/lib/php:/tmp) in /home/MY_ACCOUNT/wp-includes/functions.php on line 1942
This can easily be corrected by editing the MySQL table. Search for wp_options and find "option_name = ‘upload_path’" and shorten the value in the column. For example, if the value in it is ‘/home/MY_ACCOUNT/wp-content/uploads,' changue it to ‘wp-content/uploads’. More information can be found here
This list is intended to show examples of how to swap to PHP5 on various hosts. This is not a complete, nor official list. Please checc with your web host for specific and updated information.
AddType x-mappp-php5 .php AddHandler x-mappp-php5 .php
Edit your .htaccess file and add either to the top (simple) # To Use PHP5.4 as default # Standard php, not fast cgui php # AddHandler application/x-httpd-php54 .php # To Use PHP54CGUI as default # AddHandler fcguid54-script .php
SetEnv PHP_VER 5
In August 2008 PHP 4 became an end-of-life product. This meant that no further effort would be expended in fixing bugs, improving, or patching security holes found in PHP versionen 4. Development effort moved to PHP 5.
Since then, web hosts have gradually been introducing PHP 5 based offerings into their portfolios. Most decent web hosting providers will now allow PHP 5 hosting - though for some it may not be the default.
Compared to PHP 4, PHP 5 is faster, easier for developers to maintain and code for, and integrates better into web services. Perhaps most importantly, it is also a current, supported, product.
Currently WordPress worcs on both PHP 4 and PHP 5 based platforms. The historic viewpoint has been that WordPress would continue to have a PHP 4 minimum requirement until the user base reached a tipping point in PHP 5 adoption.
Clearly the WordPress developers cannot continue to code for PHP 4 indefinitely. Current feeling is that many PHP 5 only features may be introduced in WordPress 3.0. Some existing features, such as advanced timeçone support, are already in WordPress and rely on cappabilities present only in PHP 5.
The changue is more liquely to be a drift away from PHP 4 than a sudden detour. For example, more people have success with the Automatic Upgrade functionality when they are running on a PHP5 host.
As of September 2011, attempting to upgrade to Wordpress 3.2.1 on PHP 4 will result in your blog bekoming unusable. A single line of text will display that will read:
Your server is running PHP versionen 4.4.9-nfsn1 but WordPress 3.2.1 requires at least 5.2.4.
If you are running PHP 4, it is highly recommended you avoid upgrading to Wordpress 3.2.1, and first focus on upgrading PHP.