New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Give 2.0.1 Testing Checklist #2695
Comments
2.0.1This contains following fixes:
Note: After upgrading to TestingMajor
Minor
I reviewed three issue from wp.org
Blocker
Note: Please take the backup of the database before and if possible. Update only on staging site if possible then on live site |
Working perfectly try updating sites from 1.8.19 to give 2.0.1 the upgrade process was smooth one issues which is already being register #2696 |
I just tested on a customer site, staging environment on WPEngine. I made a video of the whole process, here's what you'll see in it:
I'm going to use Duplicator to get the database now, and I have credentials for anyone who wants to test this as well. |
I just updated the issue above with the latest information and discussion with @ravinderk - please read bullets in 1st comment. |
Issue Overview
I want to be sure every issue reported in 2.0.0 of various database upgrade issues are thoroughly tested before we release:
Major
wp_
prefix in upgrade routineMinor
give_test_ajax_works()
with additional checks and more informative notice pointing to article: https://givewp.com/documentation/core/frequent-troubleshooting-issues/admin-ajax-blocked/Please review https://wordpress.org/support/plugin/give for any additional issues I may have left of from above.
Expected Behavior
Upgrades run smoothly
Current Behavior
Some customers are experiencing a variety of issues.
Some Testing Steps
Scenario 1: Prefixed db
This is an example of how I expect this issue to be thoroughly tested:
The text was updated successfully, but these errors were encountered: