The Mailcomment Message Notify module has the following line:
$message['body'][0] .= 'View original post: ' . url('mailcomment/redirect/' . mailcomment_build_messageid($messageid_params), array('absolute' => TRUE));
which is not really necessary anymore, because users can compose message templates on /admin/structure/messages/manage page using all kind of tokens available there.
For example, it is quite possible to re-instate the above link putting the following template in the "View modes: Notify - Email body" field:
View original post: [site:url]node/[message:field-comment-ref:node:nid].
So if the above redirection link is not absolutely needed for some other features, then I'd like to file a patch that removes it, so that users of Mail Comment module had better control of sent messages' look and could compose message templates per their likings.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2773097-remove-view-original-post-link.patch | 753 bytes | nickonom |
Comments
Comment #2
nickonom commentedInitially I filed a support request on how to suppress the "View original post" part, but then I through it really make sense for all users of the module to get rid of that line completely, so I am changing this to task.
Comment #3
nickonom commentedComment #4
jweirather commentedWe attempted to comment out this same line of code, as we didn't want to include that link/reference in the body of the email, but it caused the feeds importer to stop working, as apparently this line of code was the source of the message/node ID parameters used by the feeds importer to associate the email with a nid/cid, and its absence caused feeds to fail with the message:
Unable to create comment with empty NID.This may in part be due to our outgoing mail system (sendgrid) modifying the message headers?? Speculation...
I'm currently modifying the code to try to look a bit less conspicuous and not be a URL, for now a bit hacky, but may try to create a proper patch for it.
Adding to this thread to help future searchers who might see the same error we did.