When a user replies to a posting (so far tested with blog and forum postings) via e-mail, their response should be posted as a reply on the site and also e-mailed out to the other group members, correct?
Well, the response is posted on the site but the e-mail that is sent out to the other group members does not have the reply content, it has "n/a".
However if the posting originator replies (via e-mail), their response is correctly e-mailed to the other members.
To explain in steps:
User A and User B are members of group bikers.
User A makes a blog post to the group bikers.
User B receives an e-mail containing the content User A posted.
User B responds to the bikers list address.
User B's response is added as a comment on User A's blog post.
User A should also receive an e-mail with this comment, but instead is receiving an e-mail with body "n/a".
If User A responds via e-mail to this e-mail (User B's comment) then User B IS receiving that response and not "n/a".
Hopefully that was not too confusing. I'm going to look into patching this myself, but appreciate any comment such as if it can be reproduced.
Comments
Comment #1
coltraneAfter looking into it more, the reason the message contains "n/a" is because check_markup() on line 435 of og2list.module is returning "n/a". check_markup() is returning "n/a" because this line of the check_markup() code is returning false
$edit['format'] in function og2list_send_mail() has the value 1 for the particular messages I am sending. 1 is FILTER_HTML_STRIP so filter_access() should be returning true, since 1 is set, correct?
I can get around this error by not rewriting $body in og2list_send_mail() if check_markup returns "n/a", but I do want filters to be applied so I need some expertise here. By the way, my comments are simple strings and are not complicated html pages (that I know of, unless gmail is doing so).
Comment #2
killes@www.drop.org commentedI've seen this workngn on a lot of sites now. I'd need more info to see what goes wrong in your case.
Comment #3
coltraneAfter an upgrade I'm not experiencing the error anymore, thanks.
Comment #4
(not verified) commented