|
Audrea Robbins
|
July 8, 2013 at 12:10 pm
I have a current event for today on my site. We have had clients calling asking if they are the only ones signed up and if so, they aren’t coming… why are they asking this? Because the event still shows available spaces as the same amount it was when they signed up. I have checked this myself and they are correct. It didn’t change any. I cleared cache and that didn’t show either. I’ve had 18 people sign up so I am positive the spaces should be going down. 22 should show as the amount remaining. However, on our ipad, multiple browsers and multiple computers, we are getting mixed numbers. One out of all of those we tried showed 22. The remaining showed 38. UGH! Also, 1/2 my clients called saying their tickets having the wrong time on them. I checked each ticket and they are correct, about 1/2 the 18 tickets are showing the WRONG TIME on the ticket! I have the time correct in the event itself and the ticket is customized with a logo and a photo with this wording only “This ticket or your QR Code via a Smartphone is REQUIRED at check-in.” That’s all I have on my ticket, so the error in time has to be coming from your code. Guys, can you also tell me when the new 4.0 Arabica is coming out? PLEASE let me know with a response here because I don’t have time to watch a 1 hour video on the blog to find out or hear about all that is supposedly being done on it… I’m a user, not a developer. I’ve given this plugin my everything but I’m about done with your plugin if you all cannot get one that works properly at least MOST of the time… I understand issues here and there but I have to post about something constantly. I’ve only held 3 events and none of them have been smooth. Something is constantly wrong. And yes, I keep my plugins up to date as soon as I see there is an update available… Even if I don’t, there shouldn’t be so many problems each time causing so many updates… Please, just level with me and help me get this fixed!
|
|
Josh
|
July 8, 2013 at 12:30 pm
Hi Audrea,
While I can’t give you a release date for when Arabica will be released, I can help you with the issue with the available spaces not being correct.
Caching plugins like W3 total cache can cause many random issues like these if they are not set up correctly. When in doubt, it’s best to not enable features like caching unless you’re sure of what they do.
A quick test to see if it’s a caching plugin that’s causing the different numbers to show up for the Available spaces is to log in to the site and view the page that displays the number of available spaces (typically the page that has the list of events). Then you can log out or try another browser where you’re logged out and compare. If the numbers are different it’s because the logged out visitors are getting a cached version of the page.
You check further and view the source of the page and check for the date of the cached file that’s being served. If visitors are being served a cached file from last month, for example, the available spaces number will be incorrect if people have registered since then.
Most caching plugins will have an advanced option that will let you disable caching for specific pages. This will help with the front end pages not displaying the correct number of available spaces, it may not help with the ticket time not being displayed though. In that case you might want to try an alternate caching plugin like quick cache.
|
|
Audrea Robbins
|
July 8, 2013 at 1:17 pm
ok, disabling the w3total cache plugin worked so I will look into learning more about cacheing plugins. I was just told I needed one. However, that doesn’t solve my problem with people receiving the wrong time on their tickets… I didn’t change anything in the event to cause the correct time to just magically start showing the correct time. Did you guys issue an update around July 2nd?
|
|
Audrea Robbins
|
July 8, 2013 at 1:20 pm
I re-read your reply. The time is incorrect on the ticket they print out, not on the site… It’s incorrect on the tickets! I can provide a screenshot if needed.
|
|
Dean
|
July 9, 2013 at 2:46 am
Hello Audrea,
I am not able to recreate this locally, do you have a link to a ticket and the event we can look at?
Have you modified the ticket template in any way?
|
|
Audrea Robbins
|
July 9, 2013 at 12:27 pm
See screenshots links below.
http://www.wealthmanagementuniversity.com/wp-content/uploads/2013/07/Full-Screen-Event.png
http://www.wealthmanagementuniversity.com/wp-content/uploads/2013/07/Ticket-10-am.png
http://www.wealthmanagementuniversity.com/wp-content/uploads/2013/07/Ticket-6pm.png
No I didn’t edit the ticket template as far as I remember. But if I did, the template magically began showing the correct time on the tickets as of July 2nd. I didn’t change anything on the event either after the client emailed me about the wrong time being on the ticket. It was brought to my attention on June 29th by someone who registered. I checked the event online that day and everything was fine as far as the time of the event being 6pm. So, I changed nothing. 7 more people registered after I checked it for 2 more days and all 7 received tickets saying 10 am. Then it suddenly began putting 6 pm on the tickets from that point forward for everyone else that registered. Idk when I did the most recent update but I don’t think I did one that week, I think I did the update the week before…
|
|
Josh
|
July 9, 2013 at 1:35 pm
It looks like the time was getting recorded as 10:00am in the earlier registration records, so the ticket was only displaying the time as recorded in each of the registrations.
This might actually be the caching plugin serving up some incorrect event time variables that ended up getting saved in the earlier registrations. Which would explain why it started working without any intervention. Usually the cache will expire automatically at some point and get rebuilt. This is why we highly recommend not caching any of the pages that handle registrations. The pages that handle registrations need to be served dynamically in order to work correctly.
|
