The "queued payment" code reflects the online payment process; when the user indicates that they want to pay, the payment is recorded in OCS, but it isn't considered fulfilled until the payment has been processed -- typically by a third-party payment processing system such as Paypal. Payments that have been entered but not fulfilled are called "queued payments", and fulfilled payments are called "completed payments".
By overlooking, I meant scenarios like this:
- Registrant registers for conference, opting out of a banquet.
- Conference manager exports registrant list in order to prepare for the event. This includes banquet attendees.
- Registrant returns to add a banquet option to their registration.
- No notification of the change is sent to the Conference Manager, and thus they aren't aware of the additional seat.
There are a number of options that might work for dealing with this, ranging from introducing an email notification to the Manager for a changed registration (this may be too onerous for them to handle this way), or setting additional dates that act as deadlines for registration changes. Each would require code modifications to accomplish.
Public Knowledge Project Team