Issue 826 in reviewboard: Publishing screenshot comment reviews fails and duplicates comments

2009-03-24 Thread codesite-noreply
Updates: Status: Incomplete Comment #4 on issue 826 by trowbrds: Publishing screenshot comment reviews fails and duplicates comments http://code.google.com/p/reviewboard/issues/detail?id=826 (No comment was entered for this change.) -- You received this message because you are listed

Issue 826 in reviewboard: Publishing screenshot comment reviews fails and duplicates comments

2009-01-29 Thread codesite-noreply
Updates: Status: NeedInfo Owner: chipx86 Comment #3 on issue 826 by chipx86: Publishing screenshot comment reviews fails and duplicates comments http://code.google.com/p/reviewboard/issues/detail?id=826 If you could show me the URLs that it attempted to POST to (using Firebug)

Issue 826 in reviewboard: Publishing screenshot comment reviews fails and duplicates comments

2009-01-24 Thread codesite-noreply
Comment #2 on issue 826 by timw.at.work: Publishing screenshot comment reviews fails and duplicates comments http://code.google.com/p/reviewboard/issues/detail?id=826 I have seen this occur once more (on someone else's computer/account). I have only just applied the fix for issue 820 (and up

Issue 826 in reviewboard: Publishing screenshot comment reviews fails and duplicates comments

2009-01-21 Thread codesite-noreply
Comment #1 on issue 826 by timw.at.work: Publishing screenshot comment reviews fails and duplicates comments http://code.google.com/p/reviewboard/issues/detail?id=826 I have not had this problem since correcting an issue in my database (probably related to a local test I was running). I have

Issue 826 in reviewboard: Publishing screenshot comment reviews fails and duplicates comments

2009-01-20 Thread codesite-noreply
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 826 by timw.at.work: Publishing screenshot comment reviews fails and duplicates comments http://code.google.com/p/reviewboard/issues/detail?id=826 *NOTE: Do not post confidential information in this bug report.* What's the