Optout checkbox for RSVP only affects first attendee when updating

[Andras]

We have detected an inconsistency when RSVP tickets are updated and the checkbox “Don’t show me in public attendee list” (optout checkbox) value is changed. The test scenario is as follows:

– There is an event with one RSVP ticket type having a couple of custom event fields.
– A user enters two (or more) attendees, does not check the “Hide from public attendee list”, enters values in the name/email fields and presses the “RSVP” button to create the tickets.
– All tickets are saved in the database correctly and are displayed in the attendee list on the events page.
– The user clicks the “View my RSVPs” link to enter the View my RSVPs page.
– The page displays all the attendees the user previously registered.
– The user checks the “Hide from public attendee list” and presses the “Save RSVPs” button.
– When returning to the events page, only one of the attendees is hidden from the attendee list on the events page, all other are displayed. We have confirmed this in the database, the meta value “_tribe_rsvp_attendee_optout” is only set for one of the attendee tickets, all other have a NULL value.

When the checkbox “Hide from public attendee list” is displayed only once for any number of listed attendees, we (and users) normally assume that the checkbox will affect all attendees in the list in a similar manner. You software seems to only affect exactly one attendee. We think this is a bug in your code. If only one attendee is updated, there should be an separate optout checkbox for each attendee in the list, otherwise the user interface and implemented code is not consistent.

We have found the exact location of the bug in your code and added code to set the optout flag for all attendees present in the list, and this code change passes all our test scenarios successfully.

We also found in your code that the optout flag for attendees is set multiple times in the same save operation, first in Tribe__Tickets__RSVP::update_attendee_data() and immediately after that in a call to Tribe__Tickets_Plus__Tickets_View::save_meta(), but the optout values are retrieved/handled in slightly different ways, which is a possible cause for more bugs.

Please look into this issue.

[Geoff B.]

Good evening Andras and welcome back!

Sorry for the delay replying.

Thank you for running such thorough tests. This is quite impressive indeed!

As a small token of our appreciation, I just went ahead and extended both of your licenses for 6 months.

We apologize for the inconvenience caused by this glitch.
I have logged it has a legitimate bug so that it goes through the complete Dev cycle.

Unfortunately, I cannot commit to a release date for a fix at this point.
But you will be contacted as soon as there is one.

Thank you for your patience as we see this through.

Best regards,

Geoff B.

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts