from Moshe:

>
> So, Modr8 does a great job of logging outbound communication with the node
> author, but it would be really great to log inbound communication as well. I
> think the simplest way to do this is to expand the schema to log inbound
> messages about a node. Then, the user can reply via a simple form served by
> modr8. What do you think?

CommentFileSizeAuthor
#8 response-form-319073-5x-8.patch7.44 KBpwolanin
#7 response-form-319073-6x-fu.patch1.12 KBpwolanin
#6 response-form-319073-6.patch8.97 KBpwolanin
#5 response-form-319073-5.patch6.84 KBpwolanin

Comments

moshe weitzman’s picture

moshe weitzman commented

We'd implement a trigger as well so that an action can email the moderators or somesuch.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

There was just someone on IRC asking how they could respond back to the questions asked by the moderator since the email is "noreply" so this is definitely an area of confusion for at least one person.

Michelle

pwolanin’s picture

pwolanin commented

I think the ideal would be to have some sort of reply form - a coded URL for whichi would go out in the original e-mail

the response goulc either go into the moderation log, or sent to a list or ??? or all the above?

moshe weitzman’s picture

moshe weitzman commented

well, if the reply gets sent to a list then you just put the right reply-to in the outbound email and you are done. but modr8's raison d'etre is to keep a log and I feel this merits inclusion in the log.

yes, reply via email is nice and not that hard. see mail2web module for a nice implementation. but easiest is a web form so i think we should start there.

pwolanin’s picture

pwolanin commented
Status: Active » Needs review
StatusFileSize
new response-form-319073-5.patch6.84 KB

here's a first pass (for 6.x)

pwolanin’s picture

pwolanin commented
Status: Needs review » Patch (to be ported)
StatusFileSize
new response-form-319073-6.patch8.97 KB

revised patch based on feedback from Moshe plus testing and finding bugs.

committing this to HEAD for testing and 5.x backport.

pwolanin’s picture

pwolanin commented
StatusFileSize
new response-form-319073-6x-fu.patch1.12 KB

alter 6.x to use a HMAC-MD5 token rather than straight sha1 to avoid possibly leaking the private key.

pwolanin’s picture

pwolanin commented
Version: 6.x-1.x-dev » 5.x-2.4
Status: Patch (to be ported) » Needs review
StatusFileSize
new response-form-319073-5x-8.patch7.44 KB

here's a 5.x version for testing.

pwolanin’s picture

pwolanin commented

committed the patch to the DRUPAL-5 branch - please test in prep for a release.

pwolanin’s picture

pwolanin commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.