Closed (fixed)
Project:
Signup
Version:
6.x-1.x-dev
Component:
Themeability
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Anonymous (not verified)
Created:
10 Nov 2008 at 13:42 UTC
Updated:
12 Jan 2018 at 14:42 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedComment #2
dwwPerhaps, but only if you also fixed theme_signup_user_form() in signup.theme to add the argument and a properly formatted PHPDoc comment. ;)
Comment #3
dwwFixed theme_signup_user_form(), ported to HEAD (needed to modify the record for 'signup_user_form' in hook_theme()), tested, and committed to both HEAD and DRUPAL-5--2. Thanks.
Comment #4
dwwComment #5
scottrigbyHi dww, I have two questions:
1. I followed from here #29568: Flexible number and type of fields where the proposed patch allowed form fields that could be specified per-node, or per-node-property (like taxonomy term), in theme_signup_user_form($node). There you said you committed a basically identical change - so I'm wondering if the per-node-property fields (such as checkbox and radio widgets) are now possible in the current commit to HEAD?
2. Second Q (please let me know if this shoudl be a separate issue)... is there a way to take advantage of other CCK fields in the Signup form using a similar method? For example, the Phone field in theme_signup_user_form($node) is a textfield:
Could this for instance be a phonefield instead (taking advantage of that module's validation, etc) -- or other specific cck field modules? If so, do you have any recommendations on how to go about adding them?
Comment #6
scottrigby@dww: One further thought about Q2 above...
Is there any possibility of drawing specific CCK fields from the node-type itself? For instance, could there be a way to specify a particular fieldset in the node form to hold all the cck fields we want to include in the Signup form? These fields could then be hidden on the node-form using content permissions or something, and selected on a per-node basis using cck option widgets? This would allow node-type & node-specific fields to on the Signup form, and take advantage of things like not only phone validation, but location fields, etc.
Comment #7
dww@scottrigby: The answer to most of what you're talking about is: "No. Read http://groups.drupal.org/node/3430 -- none of that is implemented yet".
All I committed is a change that passes the $node object into theme_signup_user_form() for context. You could mostly do this yourself already by checking arg(), but it's cleaner this way. What I committed allows you to do stuff like this in your template.php file: