Matheus Martins

Hi, @ignacioc.

Glad you reached out.

we’ve seen this issue in the past when people either disabled the API or had a plugin that was messing up with the API.

Also, the theme can cause errors like this when they change how you treat logged-out users.

In this case, can you triple-check if there is a plugin breaking/disabling the API, or if your theme is breaking it? You can switch your theme to test it.

Looking forward to helping you get to the bottom of this!

Hi, @rybtechsupport.

Glad you reached out.

We need GiveWP to load the scripts in a certain order so we can process the information and send it to the payment gateway. When you minify or merge scripts, it breaks the load sequence and, consequently, breaks GiveWP.

In this case, you need to whitelist any GiveWP related to GiveWP from Cloudflare so it does not break GiveWP.

​Please let us know if you have further questions or need additional assistance!

Hi, @fabriziosorbara.

Glad you reached out.

It looks like you are using a version of GiveWP that is incompatible with the Form Field Manager version. As much as I’d love to help you here, we are not allowed to support premium plugins here.

Instead, I need you to reach out via Priority Support here https://givewp.com/priority-support. There, I’ll be able to help you with the issues you are facing.

Looking forward to helping you get to the bottom of this!

Hi, @peterpollock1.

It’s been a while since we’ve heard back, and I know troubleshooting needs a little extra time. I’m marking this as resolved for now, but if you still have questions, you can send them along right here, and I’ll be happy to hop back in.

Have a great day!

Hi, @kadiwala.

Glad you reached out.

We’ve seen this issue before happening when you had cache and PayPal Donations working alongside. Can you let me know if that’s your case?

If it is, here is what you need to do (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 these recommendations):

If you’re not familiar with caching, it’s a method of saving server resources by storing copies of a page, resource, query, 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. 
Many security solutions include options for caching as well, so be sure to give those settings a look.
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.

Lastly, disconnect and connect your PayPal Donations account.

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, @tombratten.

Glad you reached out.

The connection between GiveWP and PayPal happens on PayPal’s website, and to connect them, an email and password is required.

Putting myself in your shoes, I’d use email and password – and request it to someone if it’s necessary.

​Please let us know if you have further questions or need additional assistance!

Hi, @jeffvirgil.

Glad you reached out.

The GiveWP plugin was designed as a plugin to accept donations and also let the donor control/check what they donated to/for. It means that the donor dashboard is an important part of it and there isn’t a way to remove it totally.

What you can do, instead, is to delete the donor dashboard page from your Pages menu, then navigate to donations > settings > general > general and set the Donor Dashboard Page to a different page that does not contain the donor dashboard – your home page, for example.

Although you can do that, I would say it’s better to keep the donor dashboard. But that’s personal.

​Please let us know if you have further questions or need additional assistance!