User signs up for Event 1. Db table signup_log shows one signup. Same user now signs up for Event 2. Db table signup_log now shows three signups: two for Event 1, one for Event 2. If he now signs up for Event 3, it will cumulate again, resulting in three signups for Event 1, two signups for Event 2, one signup for Event 3.

This seems to be tied to the checkout pane that shows all existing signups plus the current/new signup. Checking out adds all of those signups (past and present) rather than just the one new signup shown in the cart.

Comments

gjmokcb’s picture

gjmokcb commented
Priority: Critical » Major

Maybe not quite critical. Major, I guess. Sorta useless until fixed, at least to moi.

TimelessDomain’s picture

TimelessDomain commented

this is a huge problem if signups are limited to 1 signup. It prevents the user from purchasing event 2 & gives the error "Signups are closed for this event." (since it is trying to add another signup for event 1)

ezra-g’s picture

ezra-g commented
Status: Active » Postponed (maintainer needs more info)

This definitely sounds like a big problem if it exists.

However, I'm not able to reproduce it with the latest dev of uc_signup.

Could you try on a fresh install with the latest dev of uc_signup? If you get the problem, it would be great to see the output from {uc_signup_log} and {signup_log}.

Thanks!

ezra-g’s picture

ezra-g commented

It sounds like this could potentially be another side-effect of not cross-referencing the $_SESSION['uc_signup'] products with those in the order.