|
MR DECLAN J MAIR
|
August 11, 2015 at 5:31 am
Someone has booked an event and somehow has overpaid???
There are no taxes set up via event espresso or paypal.
I’m using a page cache plugin (w3 total cache) but the booking pages are set not to be cached.
|
|
MR DECLAN J MAIR
|
August 11, 2015 at 5:42 am
http://www.adambrowntennisacademy.com/booking/adult-beginnerintermediate-6-week-block/
This was the event… I went through the process and it came up with £70 rather than £36. This is what happened to the customer to???
|
|
Tony
|
August 11, 2015 at 5:51 am
I just ran through a registration on that event and it shows me £36 – http://take.ms/Wk3Oi
Within w3tc do you have other caching other than Page caching enabled? Database? Object etc?
|
|
MR DECLAN J MAIR
|
August 11, 2015 at 3:04 pm
Yes other options are selected to, can they affect it?
|
|
Tony
|
August 12, 2015 at 5:31 am
Yes it can.
Basically caching works by returning values that have already been retrieved from the database, without re-querying the database.
For example Page caching works by saving the page generated from using details from the database (lets say the ‘Example’ page) when the first user visits the page. The next user comes along, goes to the Example page and W3TC say’s “I already have that page, here you go”
That works fine for static content, but if details change on a per visitor basis (which they do with registrations) that becomes a problem. The cache may be generated with a ticket total of £70 even though they only selected a ticket for £36. Then the £70 value is used as that’s what is in the cached page, make sense?
It’s a fair bit more complex than that, but that’s the general idea.
Now the same can also happen with Object or Database caching. Grabbing an ‘Event’ object? W3TC – “I already have that object from earlier, use this one”
Running a query to grab the price of selected tickets? W3TC – “I already have that from earlier, use this value”.
Make sense?
This becomes a problem when your querying for new values but get the ones generated earlier from another user.
So what I would do first is try de-activating the caching options and clearing the cache (page caching should still be find as its excluded) do not just de-activate the plugin as it doesn’t clear the current cache.
Then monitor and see if the same happens again.
|
|
MR DECLAN J MAIR
|
August 13, 2015 at 12:57 am
Hi Tony,
Explanation perfectly dummed down 🙂
I’ve managed to find out the reason for the overpayment… the person booked a class at £70 and also one at £36, in two separate transactions. She received the confirmation email and payed for them both via paypal. Only 1 is showing in the registrations page, the class that costs £36 but it had £70 against it?
I looked at the options in W3, only page cache was activated with the correct pages set to be ignored.
Since this I had a comment of someone booking who kept getting taken back to the homepage when going through the process.
During this though the site has taken other bookings with no issues, but I suspect something similar has been happening as I’ve seen some duplicate booking that looks like people have gone through the process again manually.
I’ve deactivated W3 in hope that it’ll resolve it. Yesterday the servers moved across to cloudflare also.
Does this sound like something that W3 could have been causing?
Thanks in advance
|
|
Tony
|
August 14, 2015 at 5:38 am
Possibly yes, caching can cause some strange issues.
I’ve managed to find out the reason for the overpayment… the person booked a class at £70 and also one at £36, in two separate transactions. She received the confirmation email and payed for them both via paypal. Only 1 is showing in the registrations page, the class that costs £36 but it had £70 against it?
This is strange, I’m assuming this is the first time this has happened?
I notice your using the Multi Event Registration Add-on on the site, is that a recent change or have you been using if for a while?
|
|
MR DECLAN J MAIR
|
August 14, 2015 at 5:56 am
Hi Tony,
Yes this is the first time its happened… the payment was marked as an overpayment hence how it came to our attention, the customer clarified what she had done being how we worked it out. Since the switch to EE4 the multi event plugin has always been activated.
Between the times of issues we’ve had booking that appear to have no issues. All caching is now switched off, apart from cloudflare as there doesn’t appear to be an option. As far as I’m aware things seem to be working ok now.
|
|
Tony
|
August 14, 2015 at 8:43 am
As other payments are working and this seems to have been a single instance I think the best step here is to just simply monitor the registrations and see if this comes up again.
I’m going to run some test registrations using PayPal and making multiple payments for different registrations to confirm it works as expected on my test sites.
|
