Closed (cannot reproduce)
Project:
Mail Comment
Version:
6.x-2.0-beta2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Aug 2011 at 19:58 UTC
Updated:
14 May 2012 at 16:02 UTC
When I run cron, it tells me that new comments have been created. I get email notifications about them, containing the comment body and commenter name. But they don't show up on the node, and when I check in the log, they link to /node-alias/node-name#comment-0.
Doesn't seem to matter who I post as, what authentication scheme I use (I'm using "From address" to keep it simple for testing)... it creates comments but doesn't put them anywhere.
Any idea what might be missing? I can help debug if I know where to start. It looks like a variable - comment number? isn't getting where it needs to go :)
I'm using PHP5.3 and V.2 all matched-up.
Comments
Comment #1
Renee S commentedFurther to this, the message ID looks to be totally correct.
SOMETIMES there is a comment ID, and a notification is triggered either way... but the comment still doesn't show up either on the node or in the comments table.
Comment #2
danepowell commentedI'm going to release beta2 today- can you please try Mailhandler and Mail Comment beta2, run update.php, go to admin/messaging/mailcomment, check the settings, and click 'save configuration', and let me know if this is still an issue?
If so, please let me know what other modules you have enabled. Specifically, it looks like you have pathauto or some other 'node alias' module enabled, please try disabling that and see if it helps.
Comment #3
danepowell commentedNo response from OP- going to assume this is a case of user error
Comment #4
Renee S commentedNope, sorry: I did give it a shot, it didn't work. It may be an Organic Groups thing?
Comment #5
danepowell commentedWeird. Can you tell me what modules you have enabled, or are you able to disable modules to determine if one might be causing a conflict?
Comment #6
danepowell commentedComment #7
danepowell commentedI just set up an OG test site and replied via Mail Comment to a node posted in a group, and it worked fine. So it's not just an issue with OG. Are you also using Spaces, Open Atrium, or something like that? Are you using the "Mailcomment Default" importer? If not, can you send me an exported copy of your imported config?
Comment #8
danepowell commentedI just tested with Open Atrium (which makes use of Spaces and Organic Groups) and it works fine. So I suspect this is a case of misconfiguration. Sorry, but unless you can tell me how to reproduce this or narrow down the incompatibility to a particular module, I'm not going to be able to help you...
Comment #9
danepowell commentedAlso, it would help to see a raw copy (including headers) of a problematic message. Do only certain messages cause this problem?
If you don't reply in the next few days, I'll assume this has been resolved on your end.
Comment #10
danepowell commentedAfter re-reading your report a few times, I think I better understand what you're saying re: the comment path (it wasn't very clear to me what you were trying to say): you are saying that if you click the link to the 'original comment' at the bottom of comment notifications, you get sent to some path that ends in '#comment-0', is that correct?
If so, it sounds like the message signature in the footer is malformed, can you please send me a copy of the comment notification message that you receive, especially the footer with the link to the original comment?
Comment #11
danepowell commentedNo reply from OP
Comment #11.0
danepowell commentedclarification