WordPress 5.6 was recently released, and as always, we’ve updated our WordPress one-click installer to automatically install the latest version for new WordPress sites. WordPress 5.6 works fine on our servers (make sure you’re using a recent version of PHP for your site).
If you’ve previously installed an older version of WordPress, you should update it from within your WordPress Dashboard.
WordPress 5.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. WordPress 5.5 works fine on our servers (make sure you’re using a recent version of PHP for your site).
If you’ve previously installed an older version of WordPress, you should update it from within your WordPress Dashboard.
One great new feature of WordPress 5.5 is that it adds automatic updates of plugins and themes. We strongly recommend enabling this feature to improve the security of your site. To do that, just click “Enable auto-updates” for all your plugins and themes:
That’s all it takes to prevent most “hacker” attacks on your site.
WordPress 5.4 was recently released, and as always, we’ve updated our WordPress one-click installer to automatically install the latest version for new WordPress sites. WordPress 5.4 works fine on our servers (make sure you’re using a recent version of PHP for your site).
If you’ve previously installed an older version of WordPress, you should update it from within your WordPress Dashboard.
WordPress 5.3 was recently released, and as always, we’ve updated our WordPress one-click installer to automatically install the latest version for new WordPress sites. WordPress 5.3 works fine on our servers (make sure you’re using a recent version of PHP for your site).
If you’ve previously installed an older version of WordPress, you should update it from within your WordPress Dashboard.
If you have a WordPress site, and you use both the WP Super Cache plugin and the Cloudflare content delivery network, the latest version 1.6.8 of WP Super Cache may not properly cache your pages by default.
This is because of a quirk of the update: A new setting makes it think all Cloudflare visitors are “known users” because they have a “cookie” set. If you had the old “disable caching for known users” option turned on before the update, it won’t cache pages for Cloudflare visitors after the update.
The same thing can happen if you have a WordPress plugin that sets a “cookie” for each visitor for some other reason.
This problem is easily fixed by changing the new WP Super Cache “Cache Restrictions” setting from “Disable caching for visitors who have a cookie set in their browser” to “Disable caching for logged in visitors. (Recommended)”. We’ve updated our WP Super Cache page to reflect this change, and if we notice that a site hosted on our servers suddenly has higher CPU resource usage because of this, we’ll update the setting for you to make it work as it did before.
WordPress 5.2 was recently released, and as always, we’ve updated our WordPress one-click installer to automatically install the latest version for new WordPress sites. WordPress 5.2 works fine on our servers (make sure you’re using a recent version of PHP for your site).
If you’ve previously installed an older version of WordPress, you should update it from within your WordPress Dashboard.
WordPress 5.0 was recently released, and as always, we’ve updated our WordPress one-click installer to automatically install the latest version for new WordPress sites. WordPress 5.0 works fine on our servers (make sure you’re using a recent version of PHP for your site).
If you’ve previously installed an older version of WordPress, you should update it from within your WordPress Dashboard.
One thing to note is that WordPress 5.0 comes with a new default editor called Gutenberg. Some people like Gutenberg and some people don’t; if you don’t, you can install the Classic Editor Plugin to continue to use the old editor.
One of the nice things about WordPress is that it automatically updates itself for important security and bug fixes. For example, if you installed WordPress 4.9.1, it would have automatically updated itself to version 4.9.2 on January 16, and to version 4.9.3 on February 5.
Unfortunately, WordPress 4.9.3 has a bug that prevents it from automatically updating itself to later versions. It needs to be manually updated to version 4.9.4 or later.
The WordPress 4.9.3 to 4.9.4 update is trivial (it fixes only this bug, after which automatic updates will work again), so we’ve updated every customer copy of WordPress 4.9.3 on our servers to version 4.9.4, just as if it had happened automatically.
Customers should not notice any change as a result of this — but as always, don’t hesitate to contact us if you have any trouble.
We’ve received a couple of reports that audio and video file uploads don’t work anymore in old WordPress versions (4.3.9 and lower). You instead see the message “HTTP error”. (This doesn’t affect uploads of images, PDF files, etc.; it affects things like MP3 files and movies.)
This is because of a bug in the WordPress software itself, which will presumably soon be fixed, and not related to our servers.
However, if this is happening to you, you’re using a very outdated version of WordPress. You should update to the current version 4.7.3, which is easy to do by clicking “Updates” in your WordPress dashboard. We recommend that you always update WordPress whenever it tells you to do so, because it avoids all sorts of problems.
Many scripts that send e-mail include a file called PHPMailer. The file is distributed as part of WordPress, Joomla, Drupal, and lots more software.
Recently, a security researcher discovered a security bug in PHPMailer. The bug could allow “hackers” to take over a website.
However, sites hosted on our servers are not vulnerable to this problem. (Despite that, you should always update your copy of WordPress, Joomla, or any other software when there’s a new version available.)
