I think it would be a good idea to have default e-mails be possible based on the content type. Right now it is only a global setting, but if I have different content types that have signup enabled, I most likely do not want the same e-mail message being sent for all of them.

Anyone else think this would be beneficial? Has anyone already created this functionality?

Thanks,
Shane

CommentFileSizeAuthor
#2 signup_295865.patch4.93 KBstborchert

Comments

lonehorseend’s picture

lonehorseend commented

Definitely useful!

stborchert’s picture

stborchert
he/him
Primary language German
commented
Status: Active » Needs work
StatusFileSize
new signup_295865.patch4.93 KB

First draft of this feature.
It does nothing but adding the signup settings form to the node type settings page at the moment.

Question: where do we want to store the content type specific settings? General settings are stored in database ({signup}, nid = 0). This would be the best for these settings also, but there is no other nid we could use.

shanefjordan’s picture

shanefjordan commented

It would probably have to store it into the variable table. Probably a name something like signup_X (x = content type machine name). Then, you could store any information specific to that content type in that variable.

I'm working through getting my site live right now, but soon as I finish that (hopefully this week) I will be able to test this patch and see what it is doing.

- Shane

dww’s picture

dww
we/he/they
commented
Status: Needs work » Postponed

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).

doublejosh’s picture

doublejosh commented

+1

duaelfr’s picture

duaelfr
he/him
Primary language French
Location Montpellier, France
commented
Status: Postponed » Closed (won't fix)

This version of Signup is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.

simon georges’s picture

simon georges commented
Status: Closed (won't fix) » Postponed

Reverting recent closing.