It would be nice to have the option to use a default message under ManageRegistrations>>Settings>>Reminder>>Send Reminder. Can a generic message populate the field with the option to change as needed?

Comments

seanberto’s picture

seanberto commented

This is a good idea. We should also support Token module.

seanberto’s picture

seanberto commented
Status: Active » Fixed

Hehe, actually, this is such a good idea that it's already in place. Sorry, forgot about that. If you enable "reminders" on the "manage registrations" tab, you can create a templaed message. Enable Token module for token support in these messages.

rdas’s picture

rdas commented
Status: Fixed » Active

I meant that it would be nice to have a default message pre-populated in the field such as "You have registered for [node:title] on [node:field_date]." And then I could change this as needed. We do dozens of programs each month and it would be nice to not have to type in the same basic message for each of the programs individually.

seanberto’s picture

seanberto commented
Status: Active » Closed (won't fix)

Aha. I don't see that as a very general use case. It's also something that you could do pretty easily in a custom module, probably with a hook_node_save() call. This is not a feature that we'll implement within the module.

tomdisher’s picture

tomdisher commented

Hmm, this is a shame. You could do this in signup and it was nice, since we have 120+ events in a week that all need a token-ized reminder email.

Could you explain how you'd do this with a custom module?

ezra-g’s picture

ezra-g commented

@seanberto, as @tomdisher points out, this was a nice UX improvement for event admins in the Signup module.

Given that it's relatively trivial to implement, would you be open to patches for this functionality?

dpi’s picture

dpi
Location Perth, Australia
commented

This should have been implemented in #1430870: Automatically Create Registration Settings when Entities are Created

/admin/structure/types/manage/xxxxxxx_content_type/fields/registration_field_name

levelos’s picture

levelos commented
Status: Closed (won't fix) » Closed (fixed)

@ezra-g, we certainly would, although @dpi's correct, we took care of this by having defaults for all registration settings at the registration field level. This ticket wasn't keeping up with those developments. Changing to closed->fixed to reflect that.

ezra-g’s picture

ezra-g commented

Cool - thanks for the clarification!