Best Practices For Plugin Updates
Updating your Divi Engine plugins on a regular basis is a good idea if you would like to access new features, greater security and other solutions. However, sometimes updating can cause other issues. What then should you do?
Why do Divi Engine plugins sometimes cause issues when updated?
We have many customers who ask for new features. In order to help, we keep adding to our plugins and these additions sometimes cause conflicts with your Divi website.
What can you do to make sure that you do not have issues when updating?
A real practical solution is to create a staging or development website to do the updates on. This is a great way to see what the update does to your website without it affecting the live version. Creating a staging website might seem like a time-consuming activity. However, most modern cloud servers offer the ability to create a staging website in a matter of seconds. Try Cloudways since it offers the ability for you to easily create a staging website for updates. It is also true that creating a staging website is not always necessary. How then do you know when to make a staging site for an update?
- Check the version number. If it is a big jump or a new main number then use a staging website for updating. For example, if the update is from 4.5.2 to 5.0.
- Read the changelog. In the changelog you will be able to see all the new features, mods and bug fixes - do any of these impacts what you have on the site? If so then create a staging website for updating.
- If it is a minor update, then it should be safe to update on your live website. however, we still recommend reading the changelog to see the work that we have done.
What are we doing to reduce bugs?
- We do our own routine work to reduce the bugs, but as you know web design is a massive field and so it is impossible to get it right 100% of the time.
- For any major update, we release beta versions for you to help find these bugs before the live update.