I wanted to get some feed back and thoughts on this idea. I've read other posts that inquire about opening up the value field for the signup limits, but they haven't really gotten anywhere.

I was thinking that the current limit field's submit location (/admin/settings/signup) could act as the default value if no value is entered for the content type (or at least no field is associated with that node->type). Under the Signup tab in each content type (admin/content/types/[type-name]/edit) that has a) signup turned on and b) a CCK integer field associated with it, a drop down menu would be available to select the field to connect to the Signup limit. The location would be the same as the CCK date field settings and would act the same, in the way it lists the available CCK fields to select from. That way when a person creates a node for signups they can enter the limit value all at once and not go back to edit the node again to change the default value. This would also make the display of this CCK field customizable and could also be labeled as something other then signup limit, such as "team members", "passengers", "seats", etc.

Maybe this is something that can be worked into version 7.x easier then version 6.x? Another option I thought about would be to incorporate Tokens, but it seems more stable to use CCK. At least then there would be more control over what value is entered into the signup limit field. With Token I don't think there would be any way to restrict it to an integer value.

Comments

cybermache’s picture

Status: Active » Closed (outdated)