|
Florian Werner
|
April 5, 2016 at 8:04 am
Hi,
We’re currently using Stripe, and we were taking payments fine up until the beginning of April.
When a patron goes to purchase a ticket, and goes to proceed to checkout, this error appears – http://prntscr.com/aofn65
The 2 plugin updates since April 1st are one for the theme, and one for WPML updates.
We’ve tried the default Twenty15 theme, and still getting the same error – http://prntscr.com/aofpxc
The Stripe account wasn’t validated, and has now been validated by the owner this morning, so that shouldn’t stop us taking payments to Stripe, should it? However we are still getting the error. Site – https://theatrelacbrome.ca
Debug code attached below.
Can someone clarify what this error is referring to, and how to resolve this issue please?
Thanks.
Edit – http://pastebin.com/63yqCT50
-
This topic was modified 8 years ago by
 Tony. Reason: Removed log to pastebin
|
|
Tony
|
April 5, 2016 at 9:56 am
Hi there,
When posting more than say 10 lines of code (or a log) we recommend using a service such as pastebin.com and adding the URL here for us to view (I have done this in your above reply) as its much easier to read.
Can you update to the latest version of Event Espresso (currently 4.8.38.p) and retest this please.
I’ve just ran a test registration and stopped at Stripe as I used an invalid card it rejected the payment, but there has been no errors up until that point. Is it during the payment processing that the error is shown?
|
|
Florian Werner
|
April 5, 2016 at 12:31 pm
Thanks Tony,
We were already using 4.8.37.p, but we’ve just upgraded to 4.8.38.p, and we are still getting the error after clicking ‘proceed to payment’ at the Step 1 – Checkout.
|
|
Lorenzo Orlando Caum
|
April 5, 2016 at 1:19 pm
Hi there Florian,
I see that you mentioned that you tested with a default WP theme. Were any new plugins recently installed on your site?
Also, what is the version number for the Stripe add-on?
—
Lorenzo
|
|
Florian Werner
|
April 5, 2016 at 1:45 pm
Yes, we’ve updated the WPML plugins. I’ve just tried with all of the WPML plugins deactivated, but still the same error.
Stripe was 1.0.11, now upgraded to 1.0.12. Still the same error.
Do I need to reset the License, as these updates are not coming through to the site admin to be updated?
There was also an update within Stripe to update the API version. Do we need to update the API keys too?
|
|
Tony
|
April 6, 2016 at 5:15 am
When a patron goes to purchase a ticket, and goes to proceed to checkout, this error appears – http://prntscr.com/aofn65
The 2 plugin updates since April 1st are one for the theme, and one for WPML updates.
We’ve tried the default Twenty15 theme, and still getting the same error – http://prntscr.com/aofpxc
I didn’t notice previously, but those 2 errors are different.
Does this happen on a specific event?
I’ve run registrations on a couple of your events using Chrome and Firefox, I’m not getting any errors. Which browser are you using?
Do I need to reset the License, as these updates are not coming through to the site admin to be updated?
The license key does not effect EE functionality so it won’t be causing this. Is this a single site or part of a multi site install?
There was also an update within Stripe to update the API version. Do we need to update the API keys too?
You should not need to no.
|
|
Florian Werner
|
April 6, 2016 at 7:35 am
Thanks Tony, Yes, it now only appears to be showing on this event, using Chrome – https://theatrelacbrome.ca/events/knowlton-house-garden-tour/
The only difference with this event is the additional required ‘lunch’ question.
This is a single site install.
|
|
Tony
|
April 6, 2016 at 7:39 am
Have you had reports of this from users or was this just from your testing?
On that event I can register and select Stripe without a problem – http://take.ms/2PqRn
|
|
Florian Werner
|
April 6, 2016 at 9:42 am
Ok, it appears that this error is now only showing for the specific garden tour, only in the Safari browser, for myself and other users following clearing cache.
Can you see it on Safari too?
|
|
Tony
|
April 6, 2016 at 11:36 am
Have you had reports of this from users or was this just from your testing?
I don’t have a MAC so can’t test Safari, however I asked another member of the team to test it out and it worked fine.
|
|
Florian Werner
|
April 6, 2016 at 1:36 pm
Thanks, yes, we did have users not being able to make a payment until the updates made yesterday. The owner has also just experienced the error still appearing with Chrome. Once the error disappears then the payment went through successfully.
However, the error is still going to turn away customers until we stop it showing. What is the ‘SPCO’ referring to? Can we put some .css in place to remove it?
|
|
Josh
|
April 6, 2016 at 6:05 pm
SPCO is an abbreviation for Single Page CheckOut. Can you try bumping the memory available for WordPress? If there’s a fatal error where the memory is exhausted when the scripts run during checkout, that can cause the random errors you’re seeing.
http://codex.wordpress.org/Common_WordPress_Errors#Allowed_memory_size_exhausted
|
|
Florian Werner
|
April 7, 2016 at 9:51 am
Thanks guys, that’s perfect!
The memory increase did the job!
|
