Rick Alday

Hi @wealthy,

This is a conflict between GiveWP and the WP Activity Log plugin: https://www.ads-software.com/plugins/wp-security-audit-log/

Our team is going to look into it but it seems like an issue with that plugin so in the meantime, I recommend that you disable WP Security Log.

Hi @ronaduwe

Happy to clarify.
WPML creates a different form for each language. That means that each form will have separate statistics and donations. That is expected.

I see that you were able to get around this by placing a form goal shortcode on the English page. Is that correct?

Hi folks,
Just wanted to chime in here. This issue has been reported here: https://feedback.givewp.com/bug-reports/p/the-new-akismet-support-in-version-3150-might-block-donations-in-some-cases

It’s not an issue with Stripe but with the new Akismet SPAM support for visual builder forms.
There’s a simple workaround.
Navigate to Donations -> Settings -> Advanced -> Akismet SPAM Protection, and simply save the changes.
If you’re not using the Akismet plugin (although you should ??), it’s best to disable the Akismet SPAM Protection feature.

There’s a mistake in my last response.
The linse should read:
define( 'WP_DEBUG_DISPLAY', false );

Hi folks,

?I was finally able to reproduce the issue, and I found a workaround that is explained in this video:
?https://www.loom.com/share/1e391d6ecc2f41a28c9b26c00bda51e8?sid=fbf9834f-0eff-4a09-94c6-023636714cd8

TL;DR Set WP_DEBUG_DISPLAY to false in your wp-config.php file
define( 'WP_DEBUG_DISPLAY', true );
?
?Hope it helps!

No problem. We’ll leave this ticket open.

Hi folks,

If you can, please reach out via https://givewp.com/contact-us/ and in subject of inquiry, select I am responding to a request to contact you.

Then, add a link to this ticket in the message field. And we will work from there.

Hi @estedog,

Happy to clarify.
Elementor widgets do not work with Visual Builder forms just yet. Our team is working on that in the next coming weeks. You will see an update for the GiveWP Donation Widgets for Elementor plugin when it’s ready.

By default, the Payment Element uses dynamic ordering to optimize which payment methods appear for each user.

Hi @pid1984,

Glad you reached out.
I tested your form and I got the same error message.

In the broser console I get this error:
“The requested action could not be performed, semantically incorrect, or failed business validation.”

It’s one of those generic error messages PayPal throws that provide no clues as to what the problem really is.

It could be something as simple as a missing Donation Success page.
Go to Donations -> Settings -> General, and make sure you have selected “Success Page.”

Another reason for this to happen is that there’s some sort of restriction on your PayPal account and you need to reach out to them for clarification.

Hi @ridhosay,

Just following up here.
Do you still need assistance?

Glad to hear that. I’ll close this ticket now but don’t hesitate to open a new thread if you run into any other issue.

Hi Alison,

I works for me on Safari Version 15.5 (17613.2.7.1.8)
What version are you using?

Hi folks,

I just wanted to post an update here.
It looks like both of you are running PHP 8.1.27 and a WordPress Multisite installation.
I have tested this on a multisite using PHP 8.1.23 and PHP 8.2.8 but I have not been able to reproduce the issue. I’m coordinating with other team members to try to pin point the cause of the problem.

Thanks for your patience.

Hi folks,

Just wanted to post an update here. Our team is coordinating with PayPal on this issue to get this resolved as soon as possible. It seems something changed recently on the PayPal side that affects our integration.

We’ll post another update as soon as we have more information.
In the meantime, consider using Stripe instead ??

Hi there,

The token error is always related to cache. I checked your form and didn’t get a token error but I did get the infinite spinner.

The admin-ajax.php request throws a 403 error:
https://www.loom.com/i/84230c0dae6d4e6a8647546c27a87b1a

The HTTP?403 Forbidden?response status code indicates that the server understands the request but refuses to authorize it. You need to contact your host about it.