Forum Replies Created
-
AuthorPosts
-
Clair
ParticipantHi Hunter
Ryan may well have given us a pointer on this (thanks Ryan!). I’ve just checked the ticket field sets, and all of the fields have “:” at the end of the field label (see attached screenshot).
However, I don’t think this is the problem in this case. I’ve just gone through the ticket field set and remove all “:”, and then run the test again (purchasing 5 tickets for the event).
Again we’re still not getting data recorded for attendees (see attached screenshot – this shows me placing an order for 5 attendees with no data recorded, and Peter placing an order for a newly created test ticket using a newly created ticket fieldset where he could register 5 attendees).
We’re struggling to work out what is going on, so your assistance is appreciated.
Cheers
ClairClair
ParticipantHi Hunter
I’ve just shared our system details with you. To clarify, because the client’s website is a large and very active website we couldn’t just switch over to the default WP theme and deactivate all of the other plugins.
So what we’ve done is taken a copy of the site, theme and plugins and installed it in our staging environment to conduct the testing.
What we found when we did the testing, is that it seems the problem is isolated to the ticket fieldset used for this particular event.
The process we went through for testing was as follows:
On the problem event when we tried to register 4 or more attendees, the attendee data was not recorded. However when we registered 1, 2 or 3 attendees on this same event, the attendee data WAS recorded.
When we tried to register 4 or more attendees on another (un related) event the client had already set up, the attendee data was recorded.
We then created a new ticket and attendee data fieldset and added it to the problem event. When we tried to register 4 or more attendees against this ticket, the attendee data WAS recorded.
So it seems that within the problem event, there is either an issue with the ticket, or the attendee data fieldset applied to that ticket; so whenever you try to register 4 or more attendees, the data is not recorded (but for 3 or less attendees the data IS recorded).
I did post a topic about attendee data being wiped whenever you update the global fields (see here: https://theeventscalendar.com/support/forums/topic/attendee-data-wiped-when-global-ticket-fieldsets-are-updated/), but this applied to all orders, regardless of number of attendees.
There doesn’t appear to be any settings to limit/restrict sales by number of attendees per ticket, so we’ve no idea what is going on.
I’ve attached a screenshot from the attendee data section of the event. There are a number of orders with < 4 attendees and you can see the ‘View details’ link under the ticket name for these orders. However, for the order 2921 (Phillip Baker), where 5 tickets were purchased, there is no link and no attendee data has been recorded.
Hopefully that clarifies the issue?
Cheers
ClairClair
ParticipantThis reply is private.
May 26, 2016 at 6:50 pm in reply to: Attendee data wiped when (global) Ticket Fieldsets are updated #1119549Clair
ParticipantHi Brook
Just wanted to check in and see if the patch had been released? Can you please let me know?
Thank you
Clair
ParticipantOne final update.
When I create a new ticket on the same event with a different field set, it works.
So I’ve tried to narrow it down for you. There is something wrong with the specific field set that we have there.
Hope you can shed some light.
Clair
Clair
ParticipantHunter
Another update to this.
We have found that when we register more than 3 people for different events it works.
So what could it be specifically with that event that is causing the problem?
Peter
Clair
ParticipantThis reply is private.
Clair
ParticipantThanks Nico. I’ve posted this as a feature request… hopefully it’ll be one that you’ll adopt!
May 17, 2016 at 5:30 pm in reply to: Attendee data wiped when (global) Ticket Fieldsets are updated #1115699Clair
ParticipantThanks Brook
Appreciate the response. Do you have a timeframe for the fix?
Cheers
Clair -
AuthorPosts
