Closed (cannot reproduce)
Project:
Mail Comment
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Sep 2011 at 18:56 UTC
Updated:
16 Aug 2013 at 14:40 UTC
Gmail and other mail clients do or can show a user's own messages in a thread along with messages from others. If you reply to your own reply and try to import the message as a comment, the feeds importer complains: "Unable create comment with empty NID".
I'm not sure if this is easy, hard, or even possible to fix. But at least in Gmail, it is definitely easy to wind up replying once to a message, realizing you had more to say, mindlessly clicking reply again, and replying to your own message instead of the parent, thus causing the message to be lost in the ether.
Comments
Comment #1
danepowell commentedI cannot reproduce this bug. It's also not immediately obvious to me why this would happen. Are you able to provide any additional information, and also try the latest dev version that will roll tonight?
Comment #2
davideads commentedI'll do some additional troubleshooting and see what I can dig up. Seems pretty low priority from my standpoint -- we're using mailcomment with some private work groups for my project and nobody has run into this one in normal use, perhaps because the scenario is the sort of contrived thing that you only do while testing :)
Comment #3
danepowell commentedLet me know what you can come up with: FYI, I am testing with gmail and the Mail Comment Default importer, with basically all options at default.
Comment #4
danepowell commentedComment #5
danepowell commentedAlso, just to make sure I'm not misunderstanding your problem, you could post a complete walkthrough of how to reproduce the problem. Including raw copies of the problematic messages and exported copies of your Feeds importer would be especially helpful.
Comment #6
ezra-g commentedI get the same error, though it's not limited to when replying to my own comment.
I'm able to reproduce by replying from gmail, changing the subject (which removes in-reply-to-headers) and with the hack from #1650654: Messages without headers are not imported in place.
Comment #8
danepowell commented