Closed (fixed)
Project:
Entity Registration
Version:
7.x-1.x-dev
Component:
Registration Core
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 May 2015 at 16:15 UTC
Updated:
18 Aug 2015 at 21:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
.bert commentedI'm experiencing the same issue after upgrading to 1.4 from 1.3. It's as though the wait list settings are being ignored completely.
I've tried uninstalling & reinstalling the wait list module and creating new registration entities with wait list enabled as the default, but I get the same result.
It doesn't look like the wait list module changed with the last update, so it must be something else that changed with the main registration module.
Is anyone able to look into this? Or even point me in the right direction of where to look with the changes?
Thanks
Comment #2
smithmilner commentedLooks like I have the same issue. I've just installed entity registration on a clean drupal install and I can't get the waitlist to work. The registration form disappears as soon as capacity is met.
Comment #3
smithmilner commentedThis is caused because registration_waitlist compares what errors are active on the registration form. If the error is a capacity error (the event is full) that the waitlist features turn on. Looks like there was a text change to the capacity error message which is being compared.
Comment #4
smithmilner commentedComment #5
sclsweb commentedIs this a duplicate of these other issues?
Insufficient Spaces Remaining Text breaks Waitlist
Make module more waitlist-aware, bonus: making waitlist work!
Comment #6
dkane commentedI am experiencing the same issue after updating to 1.4.
Comment #7
bahebert commentedI'm experiencing the same problem. When capacity is reached, the form disappears and there's no way to get anyone on the waiting list.
Comment #8
.bert commentedThanks for the patch smithmilner. I can confirm that it works as expected in our setup.
Comment #9
Alienpruts commentedConfirmed, patch works.
Thanks,
Comment #10
cboyden commentedComment #11
nrackleff commentedComment #12
nrackleff commentedThank you @smithmilner. We are using your patch and have also made this message a constant so it will always get updated in all instances. You patch will be added to next release.
Comment #14
nrackleff commented