Face issue in legacy template

Hi @hirenmakasana,

Glad you reached out, I can help explain what you are seeing here.

You’ve uncovered an edge-case issue that we are investigating: https://feedback.givewp.com/bug-reports/p/legacy-form-template-does-not-display-errors. You can use the link to check in for updates or to provide additional details of your own. I’ve also linked your ticket internally, so when the issue is resolved we can reach back out to update you. We’ll either have a resolution for you, or we’ll know more about what our developers need to do to fix the issue.

We don’t have a viable workaround for this at the moment, it’s an issue the developers will need to dig into. If error display is a must-have for your donors, you could switch to the Classic or Multi-Step templates. One note: those two templates have some key differences compared to the Legacy form template, especially regarding styling, so this might not be the best fit.

Give the post above a look, and let me know if there are any details you would like for me to add. I’d like to make sure your issue is as accurately reflected as possible, and I’m happy to include an internal note to our teams with any specific information you would like for them to have.

If you have any questions about this in the meantime, I’m happy to help.

Hi @hirenmakasana,
It’s been a bit since I’ve heard back, and I know troubleshooting can need a little extra time. I’ve gone ahead and added your ticket to the report above, and I’ll be marking this ticket as resolved. If you still have questions you can send them along here and I’ll be happy to give things a look. Have a great day!

Because of iframe load in Multi-Step and Classic templates I can’t customize css and other things so that’s why I am using legacy template, But in legacy template I face this issue.

Hi @hirenmakasana,
You have it right, Classic and Multi-Step form templates are more resistant to styling. You’d need to determine which would help reduce the friction to your donors best: Legacy template with styling but no errors displaying, or Classic/Multi-Step with less custom styling and error displays – until the issue is resolved.

As an alternative, you could include a message on your donation form page letting your donors know that if the form scrolls back to the top that they’ll need to check their registration. This way you still have the benefits of the Legacy form, and donors have a better idea of why the form scrolls.

Error getting in AJAX response but it is not showing in form. kindly review below image.
https://tinyurl.com/2n6xlwp7

Hi @hirenmakasana,

That error is typically caused by two issues, so I’ll send along information for both here.

First, we see this error when someone donates and uses an email address that belongs to a user who has donated before at some point. If you don’t want donors to have to register and/or log in to the site to make a donation, you’ll want to disable Registration and enable Guest Donations on the form settings:

Then, also enable Email Access in Donations -> Settings -> General -> Access Control.

That will allow your donors to give as “guests” and will eliminate that error message for you.

If that doesn’t get you going, you may have an issue with caching that is the culprit. GiveWP has some best tips for managing caching:

The fix here is a bit technical, so I’ll include as much detail as possible, but you may need to reach out to your web developer or web support person to implement the recommendations I’ll be talking about below.

Your issue here is caused by some caching happening somewhere in the process. 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. Basically, instead of the site needing to recreate the page from scratch, it sends up a copy which allows it to load faster.

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.

Caching is handled differently on various sites and web hosts. This could mean a caching plugin, or caching could be in a security solution. Hosting providers also have settings for caching at the server level, and they can help make adjustments for you there. Most caching solutions have a setting or section for excluding specific URLs or parts of URLs (called “slugs”) from caching. At the very least, you should exclude the following slugs from caching:

/donations/
/donation-confirmation/
/donor-dashboard/
*any page with a donation form on it

Also, the following query strings (if your caching solution has a setting for them):
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.

Some folks prefer to customize the URLs to their site pages, so you may find that your URLs don’t have the slugs mentioned above, even though they contain the same content. In cases like those, we recommend whitelisting the page, not just the slug, that way the pages with those essential pieces of information are still excluded from caching. This is especially important for URLs of pages with donation forms on them.

One helpful tip: Check in with your hosting provider. Most hosts have caching at the server level, and they will be able to adjust this for you. 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.

I know this was quite a bit of information to share. If you have any questions about this let me know, I’m happy to help.

Hi @hirenmakasana,
I know you are doing some work here, so I’m going to mark this as resolved, but if you have any questions don’t hesitate to send them along here. I’m happy to help as you navigate things!