|
June Sadowski-Devárez
|
February 6, 2013 at 12:23 pm
Canceling the registration of an attendee (Delete) who was part of a group registration. How not to mess it up like I did last time! I’ve learned that there is no automatic refund to a credit card when canceling a registration and that it is necessary to credit the card through Authorize.net. But, how does a delete affect the total amount paid in EE?
Also, is there a record of deleted registrations anywhere?
|
|
Jonathan Wilson
|
February 6, 2013 at 1:24 pm
Hello,
Right now there isn’t an easy way to delete one person from a group registration. The whole group will need to be deleted and added again minus the registration that needs to be deleted.
There isn’t a record kept for the deleted attendees.
|
|
June Sadowski-Devárez
|
February 11, 2013 at 10:15 am
What about changing the registration info for one person from a group registration?
|
|
Dean
|
February 12, 2013 at 2:41 am
Hi Daniel,
So long as the additional attendees have some information attached to them (personal information or full registration details) they are entered in the system as an individual attendee, so their data can be deleted/modified.
If there was no additional attendee data then the primary attendee can have their ticket quantity number modified by editing that attendee.
|
|
June Sadowski-Devárez
|
February 25, 2013 at 4:03 pm
Thanks Dean. It does look like this feature is available. All our attendees have full contact info and there is a delete link next to each person inside a group registration.
Unfortunately, we get an error “The request failed to pass a security check.” when trying to delete an individual attendee, or even trying to edit their email address. We successfully edited the emails of attendees on single events. It appears there is some sort of bug related to editing/deleting from within a group registration. This is a very critical issue for us. Can you please take a look at this and advise?
Thanks and kind regards,
Daniel
|
|
Dean
|
February 26, 2013 at 2:51 am
Hello June,
Yes that bug was fixed in version 3.1.30, so I would advise you to update your existing version.
|
