|
mpurse
|
February 16, 2015 at 3:04 pm
The last person to book on our events receive an ‘event full’ message even though it was that person that took the last place.
Is there an easy fix for this please?
Thanks.
|
|
Sidney Harrell
|
February 16, 2015 at 7:38 pm
That’s very odd, we didn’t see that in our rounds of testing. Can you be more specific about what version of EE you are using, how you are able to reproduce the error, etc?
|
|
mpurse
|
February 17, 2015 at 2:01 am
Using Version 3.1.36.6.P (can’t upgrade to 4 as we are waiting for the rest of the add-ons to become available for 4).
It happens when someone takes the last place.
Here is a screen shot of the message seen by the user: http://awesomescreenshot.com/0584f9tnf6
Yet the transaction was actually successful:
http://awesomescreenshot.com/0714f9vzd0
I believe this had also led to some customers paying twice because they didn’t believe their payments went through.
|
|
Lorenzo Orlando Caum
|
February 17, 2015 at 10:38 am
Hi,
The issue that you described sounds like a timing issue. Try reducing the ticket reservation time setting in WP-admin –> General Settings –> Optional Event Settings:
http://cl.ly/image/1E3G3r2g2f3K
—
Lorenzo
|
|
mpurse
|
February 17, 2015 at 10:40 am
What do you suggest reducing it to?
|
|
Lorenzo Orlando Caum
|
February 17, 2015 at 11:43 am
Hi, that reservation time should be based on how quickly your events sell out. If the events are really popular, then I would allow 10 to 15 minutes before the time is reset and another person can register.
—
Lorenzo
|
|
mpurse
|
February 17, 2015 at 11:51 am
OK, but you do understand that I am talking about the last person that registered getting this message?
|
|
Lorenzo Orlando Caum
|
February 17, 2015 at 12:42 pm
Okay, I see what you are referring to. Have there been any changes to the core plugin?
Also, are there any caching services running on the site?
—
Lorenzo
|
|
mpurse
|
February 17, 2015 at 12:43 pm
No changes to core. Yes there is caching on the site or it runs too slow.
|
|
Sidney Harrell
|
February 17, 2015 at 1:37 pm
Most of the site can be cached, but the dynamic content generated by EE’s registration pages cannot be cached. Do you have a mechanism in your caching for excluding the EE pages?
|
|
mpurse
|
February 17, 2015 at 3:22 pm
Will try and report back. Perhaps this is the same reason some of our transactions don’t show go through successfully on the website – when actually they have via the payment gateway? (about once per month)
|
|
Dean
|
February 19, 2015 at 5:44 am
Might be, though that might also be a slow return notification from the gateway merchant.
Please keep us updated as to whether the cache white listing helps or not.
|
|
mpurse
|
February 19, 2015 at 12:56 pm
We removed caching from EE pages, but it didn’t make a difference. Screen shot here from last attempt: http://awesomescreenshot.com/05b4g4bc81
|
|
Josh
|
February 20, 2015 at 11:41 am
Hi there,
I checked the URL of the Thank you page for your site and it’s saying it’s still being served as a cached file. You can see this by going to the /thank-you/ page URL on your site, then hit the View Source button on your web browser. At the very bottom of the page it has this message:
So I can advise double checking the strings that were input for the do not cache these pages list. The /thank-you/ page needs to be included in that list.
Along with that, there are a number of EE template files that were moved over to /wp-content/uploads/espresso/templates. If these templates were from older versions of Event Espresso, then they may need to be updated by hand so they have the correct code that was added to help prevent events from older selling. A quick test to find out if this is the case is to run a quick test with the /wp-content/uploads/espresso/templates folder renamed. This will allow the templates from Event Espresso core to load instead.
|
|
mpurse
|
February 23, 2015 at 3:02 pm
OK, removed caching, temporarily removed template. Same problem. 🙁
|
|
Josh
|
February 23, 2015 at 4:00 pm
Hi there,
Can you outline how you are removing the caching? Is it:
a) Deactivate the caching plugin?
b) Disable the caching via the plugin’s settings
c) Add the Event Espresso pages to the no-cache rules?
|
|
mpurse
|
February 24, 2015 at 1:59 am
a) deactivated the caching plugin.
Same problem: http://awesomescreenshot.com/0f74h1mp4b
|
|
Lorenzo Orlando Caum
|
February 24, 2015 at 1:40 pm
Hi, that step alone may not deactivate the caching since that is set on the WordPress-level. That is, caching may still be running even if your caching plugin is disabled because a macro is enabled via the wp-config.php file.
First, could you reactivate your caching plugin and ensure that no-cache rules are setup for your Event Espresso pages:
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/
Then clear your cache and re-test.
If the issue continues, then there may be old caching files that are not clearing as expected. Try these additional steps:
Deactivate caching through your caching plugin. Then deactivate the caching plugin and login to your WP site with an SFTP or FTP client (e.g. FileZilla, Cyberduck, Transmit). Then browse to this location using your client:
/wp-content
Look for a cache_ related files and then remove those.
Then re-test again. Does the issue continue?
—
Lorenzo
|
