Many people with a WordPress website wonder what to do when they see the notice in the WordPress admin prompting them to upgrade to the latest version. Upgrading WordPress yourself can be as simple as clicking a button, but things can go wrong. Many people take it for granted that all WordPress websites should use the latest version. There is some risk involved, so it’s worth considering why it’s worth bothering – and what you can do to minimize the risks.
READ MORE :
- WordPress Installation – How to Install WordPress CMS and Why?
- Everything You Need To Know About the Samsung Galaxy S7
- Using Banner AutoRotators on Your WordPress Site to Make Affiliate Sales
- Income on the Internet – Tips for Success
- What You Need to Know About the Xbox 360, the Kinect, and a Review of All Kinect Games
The latest major release of WordPress was version 3.3, released in December 2011. As well as the new features for WordPress developers, there are loads of improvements to benefit the average blogger or website owner: My favorite new feature is the hover menus in the WordPress admin navigation, which give you single-click access to any screen. It sounds simple, but it’s a big improvement that rather than having to click – for example – pages, than wait for the page to load, THEN clicking ‘Add New,’ NOW you can hover over pages and immediately click ‘Add New’ in the flyout menu. As a WordPress designer, this has already saved me a huge amount of time, and it will help you too.
It’s easier than ever to upload images and other media via the single upload button in the WordPress toolbar. The drag and drop media uploader allows you to drag and drop files directly from your computer into the WordPress admin, rather than browse to the file’s location. Whenever you add a new feature, a pointer tip appears, providing useful information on using the feature. Touch support has been improved for those using iPads or other tablets to manage their WordPress website.
Version control has been improved for larger companies with multiple users editing the same pages and posts – the improved co-editing support locks posts that are being edited by someone else. And more. Website security is constantly evolving. Hackers are constantly working to discover and exploit loopholes, and the WordPress developers are continuously working to close them. The latest version will usually have several important security fixes to protect your website. The responsible thing to do is to update to the latest version and protect your WordPress website. Upgrading WordPress should be as easy as clicking a button, but things aren’t always that simple. Things can sometimes go wrong – for example; the new version might not be compatible with your website theme or some of the plugins. The worst-case scenario is that upgrading WordPress could actually break your website.
Problems are most likely to occur if:
Your website is particularly complex or has a lot of plugins installed. You haven’t updated for a while and are running an ancient version of WordPress, your website theme, or any plugins. If any of this applies to your website, then it might be worth getting a professional WordPress designer to upgrade WordPress for you. This is less likely to be necessary for simpler sites. Upgrading WordPress will affect all files and folders included in the main installation, including all the core files that run WordPress and the plugins that come pre-packaged with it. If you have made any customizations to these files, then your changes will be lost.
It’s not best practice to modify the core WordPress installation anyway, so if you have done this, I suggest finding an alternative way to achieve what you’re trying to do. If you don’t know-how, then any good WordPress designer can help you with this. Follow the instructions in the WordPress Codex to upgrade WordPress with minimal risk. This includes instructions on backing up your WordPress website before upgrading, so you have something to roll back to if anything goes wrong.
I would add a further precaution to make things extra-safe. As well as backing up your site, create a separate test site – this is basically a duplicate of your live site that you can test any changes on (i.e., upgrading WordPress) before applying the same changes to the live site. Although backing up is a good backup option (excuse the pun), restoring your WordPress site to a backed-up version is a hassle, so it’s best not to let things go wrong in the first place. Upgrading WordPress on a test site first is the way to do this – as with any other major changes you make to your site at any point.