Closed
Bug 477350
Opened 15 years ago
Closed 15 years ago
3 broken queries on stats pages when not logged in
Categories
(addons.mozilla.org Graveyard :: Statistics, defect)
addons.mozilla.org Graveyard
Statistics
Tracking
(Not tracked)
VERIFIED
FIXED
5.0.2
People
(Reporter: clouserw, Assigned: clouserw)
Details
Attachments
(1 file)
2.25 KB,
patch
|
lorchard
:
review-
|
Details | Diff | Splinter Review |
When you aren't logged in and you visit /en-US/firefox/statistics/1865 you get 3 SQL queries that fail due to syntax. This is because we're assuming the user is logged in when they might not be. This patch fixes the problem. The only reason I'm r?ing it is I wanted someone to double check that my returning false in checkOwnership() isn't going to break anything else. I'm pretty sure it will eventually return false anyway but want to make sure.
Attachment #361018 -
Flags: review?(lorchard)
Comment 1•15 years ago
|
||
Starting to look at this, I think I already have some fixes for these in my patch in bug 473244, since the warnings were blocking me from getting things working. Might need to see which work better and resolve any conflicts
Comment 2•15 years ago
|
||
Comment on attachment 361018 [details] [diff] [review] fix broken queries Can't get this patch to apply after my commit for bug 473244. Also looks like that included a fix for the same thing in controllers/components/amo.php
Attachment #361018 -
Flags: review?(lorchard) → review-
Assignee | ||
Comment 3•15 years ago
|
||
I agree, this is fixed. thanks
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 4•15 years ago
|
||
Was the failure ever visible to the end-user, or was it just debug-spew? Thanks.
Assignee | ||
Comment 5•15 years ago
|
||
(In reply to comment #4) > Was the failure ever visible to the end-user, or was it just debug-spew? > > Thanks. Only visible on development sites.
Assignee | ||
Updated•15 years ago
|
Status: RESOLVED → VERIFIED
Updated•8 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•