If you don’t want to, you can use the WordPress beta tester plug-in. This gives you access to the development version of WordPress (including release candidates), so you can check before a new WordPress release appears. Install and activate the plug-in. When you are finished, you can the latest beta in the usual way by navigating to dashboard > update. 5. test everything! After that, you can finally test the new release! What should I test? Yes, simply put – everything! In this process, you will see the functionality of the theme. Whether all plug-ins are compatible, shortcut codes, meta boxes, current menu display methods, sidebars, components, etc. Also, make sure which items are displayed in Tools > site status. If you find a bug, you can use the alpha\/ beta support forum to report the bug. In addition to testing, you need to be familiar with the new release and understand the functionality. So, to see how it works, you can play for a while. The point here is to better understand the impact of implementing the new version on the site. If you are satisfied with the test and make the necessary changes, it is your turn to move to the live site. 6. apply updates to live sites. Even if you are satisfied with all the content, you must apply the same changes to the actual web presence. There are many ways. Perform the same steps as those performed during testing in a real environment. The previous backup must be retained when executing. Because if the actual environment is different from the test settings, sometimes different results will be obtained. Replicate the local site to the real-time server – you can also back up the site from the primary user to the test environment, just like backing up the site to the test environment. Some backup plug-ins are helpful, and you can find examples of mobile methods here. Dump to production site push – well known hosting providers of dump sites can also push changes to the real-time environment by clicking. This is actually for dumping. Please confirm with the host. No matter which path is selected, after completion, the real-time site must be provided with the same appearance as that previously applied to the test site. If you are satisfied, you can finally complete and take full advantage of the new word press distribution. Finally, word press is updated regularly to help improve all aspects of the site. This will make working with word press interesting and interesting, but it will also cause problems. To avoid this, it is best to test the new word press distribution in a secure environment before using it on the live web. Above, you learned how to do this in five simple steps. Create a site backup test environment use the site replication and test environment to test whether the migration site has the problem of updating to the latest version, and test all aspects of the site. This knowledge of applying changes to the live site has left you unprepared for the new word press release. How to avoid damage to the site due to the new release? Do you have anything to add to the above? Please inform the comments section below.
