|
Carlos Flores
|
June 21, 2013 at 12:02 pm
I have the latest WordPress and Event Espresso. I am not using a Super Cache and have disabled WP Cache in my wordpress site.
For some reason sometimes there is a user who will pay for an event then come back the same day and pay for another event. When he goes to checkout the 1st event is still in his cart and even if he clears it from the checkout page it still somehow gets thrown in when he arrives to paypal. I am using the Multiple Registration plugin but some people still pay in a separate transaction (Go Figure!).
Seems to be happening only when someone registers for two events in a separate transaction on the same day.
Any way to force EE to not Cache that 1st event in the cart or when the info gets sent to paypal?
Thanks in advance!
|
|
Dean
|
June 24, 2013 at 4:09 am
Hi Carlos,
When the user paid for the first event was it a proper payment, via Paypal or similar or was it an “offline” payment such as an Invoice or Cheque?
There is an issue we are currently fixing where if a user fails to get to the thank you page for some reason then there “session” is not closed, as such there are still elements in there cart. We are hoping to have this fixed in the next release.
|
|
Carlos Flores
|
June 25, 2013 at 2:04 pm
Hi Dean,
Does this fix temporarily fix the issue?
This link:
https://eventespresso.com/topic/attendees-disappearing-2/
This is the code they recommended:
In file:
Place these lines in includes/process-registration/payment_page.php at line 353
else {
if (file_exists(EVENT_ESPRESSO_PLUGINFULLPATH . ‘includes/process-registration/pending_approval_page.php’)) {
require_once(‘pending_approval_page.php’);
echo espresso_pending_registration_approval($registration_id);
return;
}
}
unset( $_SESSION[‘espresso_session’][‘id’] );
ee_init_session();
}
|
|
Josh
|
June 25, 2013 at 3:59 pm
Hi Carlos,
The hotfix that was released this week (3.1.33.3) adds improvements to the payment page so folks will get a warning if they try to go back and register again without clearing out the session.
I think the code you posted here may cause issues with Multi Event Registration.
|
