Redirect to confirmation page

Hi @beccanoire,

Happy to clarify. The Classic and Multi-step form templates load via an iframe and the donation receipt is shown on the iframe itself. It’s not supposed to load the Donation Confirmation page in the iframe so that’s definitely not right but that’s usually caused by an aggressive cache on the site.
If you want donors to be redirected to the Donation Confirmation page, use the Legacy form template.

Let me know if you have any other questions.

Hi, @beccanoire.

Do you still need assistance here? I’ll close this ticket for now but if you still need assistance with it, please reopen it and we’ll happily assist you.

If you have other issues, you can open a new ticket and we’ll help you there too.

Thanks for using GiveWP! Have a great day.

I have the same issue. Even when using Classic and Multi-step it still loads the entire site in the iframe which creates a bad user experience. Do you not just have an option where the defined success page is loaded in a new window ? So in other words use the receipt shortcode on a page and have that load upon successful transaction ?

• This reply was modified 2 years, 5 months ago by kobomemphis. Reason: word wording

Sorry for the delay, I must have missed this since I ended up switching to a different platform! The site is on WPengine with their basic caching if that helps for future troubleshooting.

Hi, @beccanoire.

I’ve tested it on my website but I still cannot replicate this issue. So, as Rick said, caching can be the culprit here, so let’s make sure we remove it as a possibility.

If you’re not familiar with caching, it’s a method of saving server resources by storing copies of a page or site, so that the next visitor’s visit doesn’t trigger a call to the server at all, they just get the copy that was saved.

We put together this deep dive into what caching is and how it can cause problems: https://givewp.com/documentation/resources/caching/

Caching works really well for speeding up sites, but when a saved copy of the site has sensitive information in it (like donor info) it’s important that GiveWP not share that with the next visitor.

If GiveWP is not convinced that the browser requesting the data is the correct one, it defaults to not showing the data.

In order to verify that my hypothesis is right here, we need to exclude any asset loaded by GiveWP from the cache.

Caching is handled differently on various sites and web hosts, and most of them allow for excluding specific URLs or parts of URLs from caching. At the very least, you should exclude the following slugs from caching:
/donations/
/donation-confirmation/
/donor-dashboard/

Also, the following query strings:
give-embed=donor-dashboard
giveDonationFormInIframe=1

Your host or the caching plugin/solution you are using can help with that. Some of them may require what’s called a “wildcard” like /donations/* to capture all subdirectories under the /donations/ folder.

You can also temporarily disable caching on the site to confirm that the uncached site isn’t showing the problem.

While fine-tuning cache falls outside the scope of the support we’re able to provide, your success with online donations is our number one priority, and we’re happy to provide any tips.

If after we make sure the cache is not the culprit, then we need to go to the next steps and verify if there is some kind of conflict going on between GiveWP and other plugins/themes.

In this case, I suggest you follow our troubleshooting tutorials using Health Check. It allows you to isolate plugins and change themes for administrator, while the frontend still runs the live version of the website. You can see the documentation here:
https://givewp.com/documentation/resources/troubleshoot-wordpress-websites-health-check/
https://givewp.com/documentation/resources/how-to-troubleshoot-your-website-like-a-wordpress-support-engineer/

Your success with online donations is our number one priority. Looking forward to helping you get to the bottom of this!