We just ran across this issue on a recent installation ourselves; one 
single user out of 18 reported this behaviour.

While tracking this down, I spotted a seemingly unrelated issue where 
gOpenAnIssue wasn't being set despite the user's account settings saying 
that it was. Getting my colleague to reset the Open An Issue setting on his 
account fixed his ability to view more than one diffed file.  This appears 
to be related to the fact that his account was created manually through the 
admin pages rather than being auto-created through login. Will need to do 
some testing of that idea, though.


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' rb-server.myreviewboard.org:415
> 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 <mwoehlk...@gmail.com>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 - chi...@chipx86.com
>> Review Board - http://www.reviewboard.org
>> Beanbag, Inc. - http://www.beanbaginc.com 

Want to help the Review Board project? Donate today at 
Happy user? Let us know at http://www.reviewboard.org/users/
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 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to