Donor Dashboard does NOT display and throws Error
complete
Scott Kingsley Clark
FYI I have a workaround that I used for my specific use case where GiveWP doesn't set the cookie on login since the GiveWP plugin is not active on the main site I force people to log in through.
I think this snippet could also be useful for others encountering problems with the cookie not getting set properly right now too -- here it is just in case:
https://gist.github.com/sc0ttkclark/604958619e4842a4c61c5a24c5215fdb
Alim
This issue just brings up another issue. The dashboard is just not loading. It just shows the green spinner. I've cleared GiveWP cache, recounted all stats, re-run the databse updater, purged all cloudflare caches, just doesnt work.
Here's the link to the dashboard: https://globalsadaqah.com/dashboard/
Scott Kingsley Clark
I tested with GiveWP 2.10.3 and I still was met with the same kind of REST forbidden errors. I cleared WPEngine cache, cleared object caches, re-saved permalinks to flush the rewrites, and did everything I could think of here.
What works: Logging in (as an existing user) from the Donor Dashboard, I see the right info/screens.
What doesn't work: Logging in from wp-login.php or already being logged in. I see the REST forbidden problem as previously outlined.
Tested and confirmed the above with incognito / no cookie browser runs just to be sure.
Jason Adams
complete
Hi! 👋 This has been resolved in GiveWP 2.10.3.
This issue is somewhat complex, dealing with page and local caching. So please make sure you purge your page and CDN caches after updating. Please reach out to support if you see further issues!
Scott Kingsley Clark
Jason Adams: Should I open a new bug report or can this be reopened?
Jason Adams
Scott Kingsley Clark: Hmm, that's interesting. What's odd is that I specifically tested what you're describing on WP Engine.
Please make another post specific to getting REST forbidden errors on the Donor Dashboard when logged in as a WP user. We'll try to gather more feedback on the problem there.
Thank you!
Scott Kingsley Clark
Jason Adams: I switched to Nexcess this past weekend and the issue is there too. I've tried logging out and logging back in (from normal WP login page) and it continues to have the problem. But if I log in from the donor dashboard page itself, it's fine.
It's possible that there's an issue in my circumstance since our GiveWP site is on a subsite on the network and the logins go to the network login page to establish login cookies for .mydomain.com so it applies across sub-domains.
Jason Adams
Scott Kingsley Clark: Oh! Thanks for the multisite detail! Yeah, there's a very good chance that's the issue. Cookies are used on the Donor Dashboard for authentication. Is the primary site domain the same root domain as the subsite using Donor Dashboard? That is, is the primary site example.com and the subsite on subsite.example.com — or something like that?
Scott Kingsley Clark
Jason Adams: site: friends.pods.io and primary site is pods.io -- I have customized the cookie hash / cookie domain (.pods.io) accordingly so they are shared across all sites.
Jason Adams
Scott Kingsley Clark: Got it. Makes complete sense. I made another post for this. Please upvote over there and we'll track this in that post: https://givewp.canny.io/bug-reports/p/donor-dashboard-should-work-on-a-subdomain-multisite
Scott Kingsley Clark
Ben Meredith Thanks for the update here. That makes a bunch of sense, I'll try that as the workaround here.
FYI this is still happening even with the latest GiveWP 2.10.2 update
Ben Meredith
under review
What's going on here is that a new PHP session is not correctly being initiated when a donor logs into their WP account. GiveWP uses that PHP session to give them access to their donation history.
For now, you can ignore those errors.
Until a fix is in place, you can let donors know about there is an email verification workaround: if a donor requests a verification email, the link in the email will load their Donor Dashboard correctly, because it initiates a session when they click that link in their email.
I
ITSME
same probleme