Closed (fixed)
Project:
Entity Registration
Version:
7.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
3 Jul 2012 at 20:11 UTC
Updated:
26 Jan 2013 at 19:08 UTC
I'm looking for assistance in the use of registration states. I'm using
What I'd like to do is set up a system for putting registrants on a waitlist if all the slots are full.
I see that I can add registration states, but it's not making much sense to me:
Presumably there would be a way to change the state of any particular registration, but I haven't found that either. I figured it might be done with Rules, but nothing has popped out at me as I've clicked through options there.
Answers to any of these questions would be appreciated.
Comments
Comment #1
visuaLatte commentedI don't have an answer for how multiple registration states could be "default", but as to the "Show on form" option, checking that box causes the registration status option to show up on the registration form-- i.e. the form people fill out when registering. This form usually appears at a path like node/[node:nid]/register, with [node:nid] being the NID of the node that people are registering for.
One issue I noticed, however, is that there don't appear to be permissions for the various registration states. If, for example, I only want site admins to be able to set the status, I can't do that; the "State" field appears even for anonymous or other non-admin users.
An alternate method, which may help with the permissions issue and with granularity, would be to accomplish "registration statuses" via a field on the registration entity, or via Taxonomy. That way, multiple configurable registration statuses could be created, per-entity-bundle, and of course permissions could be accomplished via the Field Permissions module.
Hope this helps!
Comment #2
msypes commentedThanks! The taxonomy idea may give me just what I want. I'll have to try it out.
Comment #3
seanbA permission to make to registration state only available to certain user roles does seem to make sense. I will add it with a form_alter() for now.
Comment #4
jhm commentedI believe this is a very important enhancement. Currently the registration form displays all states (marked to display in form), which practically makes a Pending state useless because a user can just change to the desired state when registering.
When the state is marked as not in form, there is no way to change the registration state, because it won't be in ANY form.
Comment #5
levelos commentedThis is already implemented.
Comment #6
levelos commentedThis is already implemented.
Comment #7
jhm commentedIndeed. I accidentally overwrote my -dev version of the module with the 1.0 version (thanks drush)