With the release of WooCommerce 2.6, we imagine that you all explore the latest latest for the operation that can be used to operate online stores. The function is excited. Maybe a little worried about going through the update process again.
The beauty of the open source world developed by WordPress is that it allows almost anyone to create almost anything for us to call us home. The unfavorable side is that it is almost impossible to predict what will happen when you put any given combination of tens of thousands of creators in different environments and different environments.
We are proud of thoroughly testing Woocommerce and its extension, but unfortunate reality is: conflict still occurs . This is why we recommend preparing for release and main updates in advance, so that you can roll back immediately when there is a problem.
\”But you
How to prepare?\” We are glad you ask. The following is how to effectively set backup and testing for your WOOCOMMERCE store so that you can prepare for anything.
Set up and automatically backup for your store Prepare for future release, the first thing you have to do is to set up backup to set up backups so that your store data is safe and easy to recover when necessary
.
Backup provides you with a clean, functional store version for you to use it when major problems. If you cannot simply disable the expansion of conflict or roll back to the previous version, the backup will allow you to restore the store to the working state so that you can start again.
We recommend using Jetpack in this process. As part of the individual, senior or professional plan, Jetpack will provide you with automatic backup of the Woocommerce store every day.
Jetpack allows you to \”once and for all\” — that is, only
sets a full automatic backup, unless you need to restore backup, you will never touch them again
. If you really need to restore backup, just click to return to the previous version.
Create a separate test environment We proposed some about some aboutCreate a test space in this document to correctly update your suggestion of your Woocommerce website, but all these terms and suggestions may be confused by the new shop owner. They just want to know what, why, and how to do it. In order to make you more clear: We recommend that you copy your store so that you have a second almost the same version to test the new version without producing potential negatives on real things. Impact
. This duplicate version is usually called \”development site\” or \”test environment\” (although you can call it at will; I personally call me \”I try to break the place where things are used for fun\”).
Many store owners create their test environment on the sub -domain where their stores are located. For example, if the URL of your store is Realawesomebooks.com, you may have a test site on testing.reallyawesomebooks.com. For safety purposes, some people choose to put their test environment in different places or local storage, but this depends entirely on you!
It has many benefits to have a separate test environment; in this situation Below, it allows you to try the main version without causing any risks to your store or customer experience. Copying the content of your store to this new location, no matter where it is, it is usually the most difficult problem. If you have FTP and database access rights, you can copy everything -but remember, Every time you need to do this when you want to test something.
Simplify this process and make full use of a good way you may have used the backup created by Jetpack to restore them to your test site
. If you have frequent backups (for example, every hour or daily), this allows you to keep your test environment in the latest state without clicking a few times without manual replication.
After setting the option, Jetpack allows you to restore the backup to the spare domain, so that you can flexibly use a separate site for testing and get closer to the real -time data as much as possible.
You can learn how to set jetpack to restore your data to the spare domain according to the guide here, so that allows you to use the backup as the source of fresh and accurate data of the test environment [ 123]. No longer manually copy for you!
Formulate a test plan for each version or the main update
Once you pass the first two stages, you should be able to run automatic backup and prepare a temporary deposit environment for you to test for testing for testing for testing for testing for testing for testing for testing for testing for testing for testing for testing for testing. Essence Now you are almost ready. The only last step taken between the preparation update and actual test update is to formulate a plan for it . Forming a test plan is a good idea, so that even in your test environment, real -time data or customers will not be affected by your initial activity. You know exactly how and when
to deal with each change of each change. Essence
What is your plan depends on you and should be based on your own bandwidth, needs, and the update frequency you have observed in the past (if you install many extensions instead of only installed many extensions, you you, you May need to be tested more). But
We recommend formulating the plan in advance, clearly stated
:
When you are ready for your test site and try each version Will Zhou restore backup to your on -stage site and test the main version once a month? Or would you give priority to preparing for major updates as soon as possible?
Where will you test
, whether it is your test site or some kind of auxiliary site
How long will the test period last
[ 123]
Who will participate in it -Will will you try to find defects, or will you let other team members and even your family try to find problems?
Specifically, what needs to be tested
Once you have experienced this process, it may feel less embarrassing and more natural, including Discover potential errors, find out which plug -in or extensions cannot work well, and work with your development process.
compatibility between those who never tested plug -ins, extensions and themes before before For a person, a \”professional\” reminder:
If you encounter strange things and are not sure what causes it, please stop all plug -in/extensions in batches and re -activate one after another until the error appears again.
In addition, our supporting ninja always recommends switching to Storefront to solve the potential conflict between WooCommerce and third -party themes. Therefore Copy. (The store is free, so you don’t need to spend any hard -earned money to get the deputy for your test siteBook! )
Why not upgrade without testing is not always effective When the main version of the WOOCOMMERCE is available, or when your other plug -in or one -expanded upgrade, it may be difficult View the impulse of new features.
This method is usually good on a personal blog or WordPress -driven website.
But as far as your online store is concerned, the best way is to act with caution, and
always test it before activating the main update
. Your store is facing more risks and more possibilities to conflict. These two factors make preparations more important.
If you do not pay attention Our warnings and suggestions, there may never be nothing bad. To be honest, most of the owners are carefree, even if there are no tests. As mentioned earlier, we have invested a lot of time and resources to test the continuous compatibility of our products. But similar, because of the open source of WordPress plug -in and themes and third -party Woocommerce extensions, It is best to create some backups and test these updates to prevent it in case you find that you are not compatible with compatibility Cause errors
even (oops) to break your store.
Of course, you can fly it …
[ [ 123] Our store collapsed, we forgot to back up! *Scream*
… But seeing the workload required for automatic update and preparing to enter the stage is very small. We think it is worth spending time (and a little money) to do the right thing one.
Of course, regardless of your situation, if you encounter problems in any version or upgrade, you can contact us to support the ninja reliable at any time. Experience the smooth sailing through backup and testing your WOOCOMMERCE store As we mentioned, we are proud of testing Woocommerce and its expansion before any main version or update. But the beauty of open source also brings some unpredictable, so even if we conduct extensive testing, it means that we cannot capture all possible errors or conflicts.
By setting up the test version of automatic backup and preparing temporary server or store, you will prepare for the main version or extension
, when they arrived or launched when they arrived or launched.
What questions do you have to prepare for the next version?Let us know that we will definitely help you in the comments below.
Simplify this process
