diffviewer_diffset.name isn't in GROUP BY

2016-02-15 Thread Jason Woodrich
Greetings, I upgraded from 1.7 to 2.5.2 today and everything seemed to go smoothly, but now when I try to access reviews I'm getting this error: 2016-02-15 21:01:54,090 - ERROR - - Exception thrown for user X at http://X/r/102/ (1055, "'reviewboard20.diffviewer_diffset.name' isn't in GROUP BY"

Re: Javascript errors when clicking expand buttons in diff view

2016-02-15 Thread travis
I just noticed that the expander buttons in the code snippets of a review (on the reviews tab, not the diff tab) work correctly, strangely enough... -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons

Re: Javascript errors when clicking expand buttons in diff view

2016-02-15 Thread Christian Hammond
Hey Travis, Sorry for the delay. Was out yesterday and today. I forgot to mention before that the diffs in the diff viewer load asynchronously, so the page's source won't actually work. If you open the Network tab in the browser's developer tools, and then load the diff viewer, you'll see request

Re: diffviewer_diffset.name isn't in GROUP BY

2016-02-15 Thread Christian Hammond
Hi Jason, What version of MySQL are you running? Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On Mon, Feb 15, 2016 at 1:06 PM, Jason Woodrich wrote: > Greetings, > I upgraded from 1.7 to 2.5.2

Re: Javascript errors when clicking expand buttons in diff view

2016-02-15 Thread travis
No worries Christian. So I followed your instructions to get the fragment HTML and it strangely seems to include the tbody element as you are expecting (see attachment). I've also attached the html of the entire #diffs element after this fragment is inserted and you can see that the tbody eleme

Re: Javascript errors when clicking expand buttons in diff view

2016-02-15 Thread Christian Hammond
Hi Travis, Can you see if you can get the raw version of that first file, maybe using wget or curl or something? There's a "" at the top of the file, which we don't emit in our template. Can you also perform the expansion, see what URL the developer tools are showing gets loaded, and grab that ve