Skip to content
This repository has been archived by the owner on Nov 6, 2019. It is now read-only.

Only first attendee in a group is shown when using [camptix_attendees] #194

Open
erichahn opened this issue Dec 24, 2017 · 0 comments
Open

Comments

@erichahn
Copy link

TL;DR;
Really I'd just like to create a page that shows, Each individual, and each ticket type.

Where I'm at.
Customers who only purchase one ticket at a time are shown on the attendees page.

Customers who purchase multiple tickets using multiple names are not shown. Only the first purchaser is shown. I'm able to see both individuals on the admin page, but not if I'm trying to make a public attendees page.

Currently I have an attendees tag for each ticket type and then a little description of the ticket type above.

Example

Ticket A
[camptix_attendees tickets="ticketa"]

Ticket B
[camptix_attendees tickets="ticketb"]

Result
Ticket A
Person A Person B Person C

Ticket B
Person E (Person F is missing, because Person E chose to purchase 2 tickets at once)

How could I just do the following
Example
[camptix_attendees tickets="[separate_types]"]

Result
Ticket A
Person A Person B

Ticket B
Person C Person D

Related but not as important, I had to view the page source on the tickets page in the admin interface to view the ticket id. I couldn't find it anywhere else.

coreymckrill added a commit that referenced this issue Mar 6, 2019
For some reason the render callback was taking an array of attendee
IDs and re-keying it to the attendee's email address. In the case
where a person purchased multiple tickets and didn't specify a separate
email address for each ticket, this meant that often the
attendee IDs associated with that email address would keep getting
overwritten, so that only one attendee per email address would be
output in the list. (This was further complicated by the fact that the
query is paginated, so for events with more than 200 attendees there
was the possibility that some attendees wouldn't get overwritten if
they were on separate pages). The email address key isn't actually
used for anything, so by removing this step, we ensure that all
attendees with the same email are able to be output in the list.

I suspect this also addresses #194.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant