Global Signup Settings for All Nodes
deviantintegral - July 25, 2008 - 02:15
| Project: | Signup |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Jump to:
Description
Hi,
I've created a module which allows signup to be set to only have one set of settings for all signup-enabled nodes. It doesn't require any changes to signup itself, but I've only tested agains 2.4. If there is enough interest here, I'll create a project page for it, or I'll rewrite it as a patch to include in signup itself. As is, I can see it being useful to enable on a per-content type basis, but I haven't done it as my current site doesn't need it.
Thanks,
--Andrew
| Attachment | Size |
|---|---|
| signup_global_defaults.tar_.gz | 1.4 KB |
#1
I haven't had time to download the code and try it out. Based solely on your description here, I don't fully understand what this does. You mean all the per-node signup settings, such as the reminder message template, signup limit, etc?
I'm definitely interested in adding a way to configure sites such that the site admins can specify this stuff and regular signup admins can't tweak it.
Here are some of the issues related to how I think the signup settings need to be reorganized and overhauled:
#118794-10: Using Event author for "send signups to" address
#237986: Default/Per Node Confirmation
#290305: Split out email functionality into separate submodule(s)
#290249: Make autoclose time per-node, not just site-wide
#279622: Add a setting to prevent cancellation after a certain date
How does this code of yours fit into this picture?
Thanks,
-Derek
#2
Here are the settings which are updated. It's essentially the same code, but without the WHERE nid=... clause.
$form_values['signup_forwarding_email'],$form_values['signup_send_confirmation'],
$form_values['signup_confirmation_email'],
$form_values['signup_reminder_days_before'],
$form_values['signup_reminder_email'],
$form_values['signup_close_signup_limit']
Right now, it's in the form of a checkbox on the signup settings page which makes the settings "global". As per the help, "Enabling or disabling signup reminders will not apply to existing nodes to prevent duplicate reminder emails." Though now that I think of it, it might be good to only ever flip that setting to 'off', or let it change it but get admin confirmation.
As per the issues you pointed out:
#118794: If we supported tokens in all headers, and exposed them as user-configurable settings, I think this would be solved.
#237986 is a narrower request of what's supplied here. Can probably be marked as a duplicate. However, this module is all or nothing, so perhaps we need settings for different groupings of fields?
#290305 would certainly affect this feature, but not in any negative way that I know of.
This doesn't do anything for the auto-close time, so that issue is still unsolved. Same with the cancellation - if it (or any other settings) are implemented, it'd be good if they could be per-site.
I think the "Valhalla" of this group of features would be to have it so that you have site-defaults, and node defaults only if they are changed. Something like a variable which says "use default settings", otherwise pull in settings for the specific node. Then you could do things like a list of all nodes with customized messages.
--Andrew
#3
I think the basic concept articulated in this feature request is a good one.
However, I believe the whole email functionality of this module is weird and needs rethinking.
Therefore, this is hereby postponed in favor of #290305: Split out email functionality into separate submodule(s).
#4
I'm bumping this to the same version that this issue is dependent on.