WordPress 3.5 was recently released, and as always, we’ve updated our WordPress one-click installer to automatically install the latest version for new WordPress sites.
If you’ve previously installed WordPress, you can upgrade it from within your WordPress Dashboard.
As a reminder, you should always update immediately when WordPress tells you there’s a new version available in the Dashboard. Don’t let yourself get behind, because it gets more difficult to update smoothly if you’re several versions out-of-date.
The PHP developers have announced the release of version 5.3.20 that fixes several bugs.
We’ve upgraded PHP 5.3.19 to PHP 5.3.20 on our servers as a result.
In an earlier post, we described how we’re phasing out PHP 5.2.6 in favor of the newer PHP 5.3 series.
Our original intention was to remove the long-obsolete 5.2 series entirely. However, a small number of customers have told us they’re unable to update their scripts to work with PHP 5.3, usually because the script is more than five years old and no newer version is available.
To help these customers, we’re making an extra version of PHP available: version 5.2.17. That’s still an outdated version, but for technical reasons we’re able to support it for a while longer than PHP 5.2.6, giving customers at least six extra months — perhaps even longer — before PHP 5.3 is the oldest version available on our servers.
We still recommend that all customers use the PHP 5.3 series. However, if you’re unable to do that, you can now use our “My Account” control panel to choose PHP 5.2.17 instead:
- Login to the “My Account” control panel.
- Click PHP Settings.
- Choose the Use PHP 5.2.17 option.
- Click Save Settings.
Our previously announced schedule to remove PHP 5.2.6 still applies, except that PHP 5.2.6 customers will be switched to version 5.2.17 (instead of all the way to the 5.3 series) if they don’t upgrade to 5.3 themselves.
The PHP developers have announced the release of version 5.3.19 that fixes several bugs.
We’ve upgraded PHP 5.3.18 to PHP 5.3.19 on our servers as a result.
We’ve renewed the SSL certificate on our mail servers (because it was due to expire soon).
Almost all customers shouldn’t notice any change, but if you read e-mail using a secure connection with an unusual mail program that doesn’t handle SSL connections properly, you might be asked to “accept” the new certificate.
Read the rest of this entry »
The PHP developers have announced the release of version 5.3.18 that fixes several bugs.
We’ve upgraded PHP 5.3.17 to PHP 5.3.18 on our servers as a result.
This won’t affect most customers, but we’ve changed one of the “php.ini” settings for PHP 5.3. The “register_long_arrays” setting (which defaults to “Off” in PHP 5.3) has been changed to “On”, as it was in PHP 5.2.
Read the rest of this entry »
As described in a previous blog post, we’re removing the obsolete PHP version 5.2 from our servers. Our customers should only be using the newer PHP 5.3 series.
Read the rest of this entry »
The PHP developers have announced the release of version 5.3.17 that fixes several bugs.
We’ve upgraded PHP 5.3.16 to PHP 5.3.17 on our servers as a result.
WordPress 3.4.2 was released yesterday, and it contains important security updates to keep your site safe.
Our WordPress one-click installer automatically installs the latest version for new sites. If you’ve previously installed WordPress, you should upgrade it right away from within your WordPress Dashboard.
In fact, you should always update immediately when WordPress tells you there’s a new version available. Don’t let yourself get behind, because it gets more difficult to update smoothly if you’re several versions out-of-date.
