The two issues are related.

I have absolutely no idea how the user's profile entry is ending up with that 
value set to.. null? Or something. 

Actually, for any user hitting this, I'd love to get an SQL dump of their 
accounts_profile table entry, if you can find it, before they fix it with the 
double-toggle workaround.


Christian Hammond -
Review Board -
Beanbag, Inc. -

On May 28, 2013, at 7:29 AM, Kristin Thomas <> wrote:

> Was there a resolution to this issue?  We are experiencing a similar problem. 
>  We have 16 users with no problem and one user that cannot load any diffs (in 
> IE, Chrome, or Firefox).  Same error as mentioned previously:
> [08:21:52.611] SyntaxError: syntax error @ 
> [08:21:52.809] ReferenceError: gReviewRequestId is not defined @ 
> [08:21:52.837] TypeError: RB.setFileAttachmentComments is not a function @ 
> I'll attach the log.
> Any help would be greatly appreciated.
> Kristin Thomas
> On Tuesday, April 23, 2013 7:16:04 PM UTC-6, Jonathan Wilson wrote:
> Hi Christian,
> Sorry for the late reply, I tried view a diff with the Chrome console and no 
> error messages were displayed.
> I only received the following messages while clicking on the initial review 
> request link:
> Uncaught SyntaxError: Unexpected token ; /r/593/:40
> Uncaught ReferenceError: gReviewRequestId is not defined reviews.min.js:112
> Uncaught TypeError: Object #<Object> has no method 
> 'setFileAttachmentComments'
> I have 2 other colleagues who have the same issue, but the majority of my 
> colleagues have no issues viewing multiple diffs.
> -JW
> On Monday, April 22, 2013 2:33:58 PM UTC-4, Christian Hammond wrote:
> On Mon, Apr 22, 2013 at 8:57 AM, Matthew Woehlke <> wrote:
> On 2013-04-20 01:55, Christian Hammond wrote:
> Hi Jonathan,
> I don't think I've seen this. Can you open the Chrome console log, try
> again, and see what errors may appear?
> Is the server able to generate the diffs? I'm sure Christian knows much more 
> about RB than I do :-), but multiple browser failures still sounds to me  
> more like a server problem.
> While you're checking your browser console logs, it is probably worth also 
> checking the server logs if there is any message that would indicate a 
> problem generating the diffs.
> It very well might be the server. I stated on the browser side because 
> generally, if there's a server-side error, we should be showing it. We load 
> the diffs dynamically, so if there's a browser-side script error, we may fail 
> to either load or render (or show the error).
> Christian 
> -- 
> Christian Hammond -
> Review Board -
> Beanbag, Inc. - 
> <errors.txt>

Want to help the Review Board project? Donate today at
Happy user? Let us know at
To unsubscribe from this group, send email to
For more options, visit this group at
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to