Updating plugin best practices
Updating your plugins is a good thing to do as
- It gives you more features
- Fixes bug code
- Fixes security issues
- Makes sure there are no problems with WordPress and Theme updates
The issue is that sometimes these updates can cause issues with your site, so what do you do?
Firstly, why are there sometimes issues?
We have a lot of customers who want new features or develop their websites in different ways. We try and cater for all this and keep adding features and requests you have. Sometimes one feature might conflict or maybe you have developed the site in a way we have not thought of and tested on. This can cause an issue
What can you do to make sure you do not have issues?
The first thing you can do is to create a staging or dev site to do the updates on. This is a great way to check the update without impacting the live website. You may have the question that this is labour intensive or a pain to keep doing this for every update? Yes we agree and you should not have to do this for all the updates. So how do you know when to make a staging site for an update?
- Check the version number. If it is a big jump or new main number - a rule of thumb is that we have changed a lot so please make a staging site. (example if the update is from 4.5.2 -> 5.0)
- Check the changelog. In the changelog you can see all the new features, mods and bug fixes - do any of these impacts what you have on the site? Create a staging site
- If it is a minor update, it most likely will be ok but we still recommend checking the changelog to see what has been done.
What are we doing to reduce bugs?
- We do out own checks (as much as we can) but as you know web design is a massive field and done so many ways. It is impossible to check all the different situations.
- For any major update, we release beta versions for you to help find these bugs before the live update