spingary
Forum Replies Created
-
5.5.3 did fix my issues. Thank you @sstoqnov !
Please disregard – I see you did up the version number!
@sstoqnov would you consider releasing the fix with a new version #? I support tons of sites and they were all updated to 5.5.3. It’d take a lot of time to delete and install vs just updating them!- This reply was modified 4 years, 7 months ago by spingary.
@sstoqnov I will do that now.
That’s right, the latest update breaks lazy loading. All background images on my sites go dark unless I disable lazy loading. Could use a hotfix!
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Unable to process at this time errorThanks, Thomas! There was really nothing on that log that was harmful but I removed it anyway.
I hunted the problem down to this:
- 1. Tribe’s Event Tickets and Event Tickets Pro plugins running. (The site is selling event tickets.)
- 2. Breeze performance plugin running with Auto Purge Varnish checked: https://sg.d.pr/fUhHwC
If these 2 conditions are met, then the purchase process takes 20+ seconds and then sometimes it would come back successful, and sometimes it would fail and multiple 400 errors are seen on Stripe.
If I turned off the Event Tickets plugins OR if I leave off Breeze Auto Purge Varnish, then the process takes 5 seconds and successful every time.
I am going to open a ticket with Tribe folks first to see if they can help.
Hopefully this may help others.
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Unable to process at this time errorJust a bit more info as I wait for someone to hopefully look into this: this happens for both Stripe Test transactions and Live transactions.
Looks like the “give.all.min.js” script tag is placed in the header regardless of the Script Loading Location setting.
I traced the problem to be in includes/scripts.php, on line 30, the condition should be changed from ‘on’ to ‘enabled’:
Gary
I am having the same issue after upgrading to the latest Give core/base. I fixed it before by choosing “footer”, but now it doesn’t work either way. The donation form is down as long as this error persists – please help!
Thanks!