I am having the same issue with it running at 0% progress.
Well – at least mine has better progress than yours I suppose. I am at 2,098,300% progress. That’s great progress, except that I’m sure my database or web service is probably suffering in some way. I’m not sure where all those attempts to update are being stored – database, file. Hopefully there is a way to stop this and continue with the update properly.
Anyone with any ideas on how to stop the updates from attempting at least?
HI folks,
Please reach out to me via our contact form here:
https://givewp.com/contact-us
Choose the option “I’m responding to your request to contact Give”; reference this support URL, and ask for me. I can help you both best over there.
Thanks!
Hi there, I’ve for the same problem. As I mentioned on your blog post (https://givewp.com/prepare-for-give-2-0/) in a commentm, there is no problem with admin-ajax according to my host. Any help on this?
@mdsheeks admin-ajax.php can be blocked for a variety of reasons, not only from the server-level. See our FAQ on that here:
https://givewp.com/documentation/core/frequent-troubleshooting-issues/admin-ajax-blocked/
Try those options, if you still need assistance, then please provide your System Info by going to “Donations > Tools > System Info”.
@tgunkler Did you ever find out how to stop it? I have the same problem. Give says 2.0.1 will fix it, but how to I stop it in the meantime so I can revert to a backup?
I put in a ticket to Priority Support since I’m a customer, but they only work M-F and I would love to get this taken care of today so my client doesn’t see this tomorrow and get all worried!
@brightgirl No, although the updates stopped in the “Update 89495 of 3”, it doesn’t show complete and it shows that it’s still updating in the background. I have a support ticket open and setup a staged version (with the issue) for the dev team to work on. I expected to hear from someone on Friday and haven’t received an update yet. I’m hoping it can be resolved ASAP since I don’t believe the donations will work properly and I also wouldn’t want them to work then have to rollback to a previous backup, losing the recent data in the process. Deactivating the plugin and reactivating at this point just lets the issue continue where it left off. Fortunately, the rest of the website is functioning!
At this point, I’m just waiting and being hopeful.
HI @brightgirl and @tgunkler
Here’s what I’d recommend currently:
1) Backup your site
2) Install WP Rollback and use it to roll Give back to 1.8.19
3) All should be fine then
4) Wait for Give 2.0.1 to be released soon.
If the Rollback doesn’t get everything resolved, then:
1) Create a detailed list of all your new donations since updating to 2.0
2) Restore a back from before the 2.0 update
3) Use our Import tool to import your new donations
4) Wait for Give 2.0.1 to be released soon.
Let me know how that goes.
WP Rollback worked without issue on the staging site I setup (the one your team was working on and installed WP Rollback on). I just installed WP Rollback on the live site. I clicked on Rollback for the Give Donation plugin and no versions show up on the page where it says to select the version to rollback to. Any ideas what may be preventing the versions from appearing?
Thank you.
I had the same issue when upgrading from 1.8.19 to 2.0.1. Rolled back the VPS to pre update and staying on 1.8.19 for now.
According to the WordPress Meta team:
Parts of the ww.wp.xz.cn infrastructure are currently being migrated to new servers. During this period data may appear stale as caches are being served when live data is not available. As this is a rather large undertaking there’s no estimated timeframe, but we’re working to get everything up and running as soon as possible
We’ll keep you posted on what the ww.wp.xz.cn team says in regard to this migration.
My temporary solution to this issue was to use All in One WP Migration to export the site (on a Windows Azure web app), while this update still showed as actively updating, then import it into a new server. Using WP Rollback on the new VPS server (InMotion hosting). No data lost, fortunately, but I’m still running 1.8.19. On the positive side, the new server is much faster for WP.
Unfortunately, I tried to update the Give Donation today to 2.01 (as recommended) and the database upgrade started right back where last showed (Update 89495 of 3) and the circle spinning. I tried pausing the upgrade and restarting it using the new option on the Give database update page, but it keeps starting right off where it left off. The update number no longer increases, so maybe it hit its maximum display limit of 89495.
So… I tried to use WP Rollback, which is a great plugin, but it shows no rollback options and prompts me to continue the database update. So I guess I’m restoring from backup – again. Very frustrating.
There’s nothing we can do about the version issues from ww.wp.xz.cn, but from several reports it seems like it is either resolved or almost resolved for most users.
Regarding the updates; we’ll be shipping Give 2.0.2 which should ideally resolve any remaining issues with the Database updates.
So watch for that update within the next 24 hours; update; then let us know how it goes.
Thanks!
Give 2.0.2 fixed the issue and we actually received a successful donation during the time the DB showed as need updates, so that was great news.
Thank you.
Woot! Thanks for the confirmation @tgunkler and congrats on already getting those donations rolling.