|
C9
|
November 7, 2019 at 7:18 pm
Good Day.
I would just like to ask if how can remove the
“ee_spco_reg_step_payment_option get selected method of payment” check
on the registration process (https://prnt.sc/pttc3v) because it should be on this page ( https://prnt.sc/pu0eij )? I got this error (https://prnt.sc/ptssh7) when booking a course from a registering user but when I refresh the error is gone , it’s just we need to get rid of the error message.
The error shows after clicking this button (https://prnt.sc/pu0dyw) where it checks for the payment method. This only happens when registering a new account in the payment process.
Thanks 🙂
|
|
Tony
|
November 8, 2019 at 7:44 am
Hi there,
Removing the above method isn’t the solution to this issue, it’s trying to pull a payment method because something on the request is set to do so.
Is there an event I can run a test registration on to view what happens?
Do you have any caching enabled on the site?
|
|
C9
|
November 10, 2019 at 6:09 pm
Hi
Thanks for your response.
You can try to book a course here http://c9.studiopilates.com/education/book-a-course/ any course will do and you can also register. The error comes up when registering a new account on the booking process
Thanks 🙂
|
|
C9
|
November 10, 2019 at 7:16 pm
This reply has been marked as private.
|
|
Tony
|
November 11, 2019 at 7:15 am
W3 Total Cache for cache
Which caching types do you have enabled?
Have you added the EE critical pages to your exclusions? If not, please follow the steps here:
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/#w3totalcache
|
|
Tony
|
November 11, 2019 at 7:50 am
Ok, I’ve had a look at your site and I remember this setup from viewing your site a little while ago.
The ‘register for an account here’ link you have is basically altering the current session and when it does that it’s setting something in the session/request which tells Event Espresso it needs to check for a payment method.
So I can tell you what EE is checking for and from there you’ll need to work through your custom code to find why that’s being set.
If selected_method_of_payment is set on the current request or within the user’s session EE will try to determine what payment method it is, so whatever custom code you have needs to not that that within the request/session.
|
