Closed
Bug 522605
Opened 15 years ago
Closed 14 years ago
[AMO] Review count mismatch between details and reviews page
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect, P5)
Tracking
(Not tracked)
VERIFIED
FIXED
5.11.7
People
(Reporter: vish_moz, Assigned: jbalogh)
References
()
Details
Addons details page for this addon https://preview.addons.mozilla.org/en-US/firefox/addon/1865 shows 1379 reviews whereas https://preview.addons.mozilla.org/en-US/firefox/reviews/display/1865 shows 1294
Updated•15 years ago
|
Target Milestone: --- → 5.2
Updated•15 years ago
|
Target Milestone: 5.2 → ---
Comment 1•15 years ago
|
||
regression of https://bugzilla.mozilla.org/show_bug.cgi?id=428118
Comment 2•15 years ago
|
||
Smaller example is as follows: https://addons.mozilla.org/en-US/seamonkey/search?q=littlemonkey&cat=all Showing 4 reviews https://addons.mozilla.org/en-US/seamonkey/addon/309 Showing 3 reviews https://addons.mozilla.org/en-US/seamonkey/reviews/display/309 Only has 2 reviews
Comment 3•15 years ago
|
||
This is also the case with Minimap sidebar: https://preview.addons.mozilla.org/en-US/firefox/addon/5203 Showing 67 reviews https://preview.addons.mozilla.org/en-US/firefox/reviews/display/5203 Showing 66 reviews
Updated•15 years ago
|
Severity: normal → trivial
Priority: -- → P5
Target Milestone: --- → Future
Updated•15 years ago
|
Target Milestone: Future → 4.x (triaged)
Reviews count is mismatched: https://preview.addons.mozilla.org/en-US/firefox/addon/3615#reviews showing 401 reviews https://preview.addons.mozilla.org/en-US/firefox/reviews/display/3615 showing 387 reviews
Comment 5•14 years ago
|
||
I'm noticing this in Zamboni, too, but it's much worse there. STR: 1. Load https://preview.addons.mozilla.org/z/en-US/firefox/addon/10218/#reviews 2. Look at the link that says "See all 3 reviews of this add-on >" 3. Click it 4. You're taken to https://preview.addons.mozilla.org/z/en-US/firefox/addon/10218/reviews/ 5. Look at the # of results at the bottom Shouldn't this be 5.9, given that we're doing details pages in Zamboni in 5.9?
Assignee | ||
Comment 7•14 years ago
|
||
I'm going to call this fixed by switching to a zamboni cronjob in http://github.com/jbalogh/zamboni/commit/2c4525a7 and http://github.com/jbalogh/zamboni/commits/7949674. /reviews will still be remora, so it may not match there, but /z/reviews should be consistent.
Assignee: nobody → jbalogh
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: 4.x (triaged) → 5.11.3
Assignee | ||
Comment 9•14 years ago
|
||
(In reply to comment #8) > Verified, FIXED. Not on https://preview.addons.mozilla.org/z/en-US/firefox/addon/6028/, the cronjob hasn't run yet.
Status: VERIFIED → RESOLVED
Closed: 14 years ago → 14 years ago
Assignee | ||
Updated•14 years ago
|
Target Milestone: 5.11.3 → 5.11.4
Vishal, please verify this; thanks!
Reporter | ||
Comment 11•14 years ago
|
||
This addon https://preview.addons.mozilla.org/z/en-US/firefox/addon/6028/ has 3 reviews but it says 0 reviews. (Not reopening because not sure if the cron job needs to run)
Updated•14 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•14 years ago
|
Target Milestone: 5.11.4 → Future
Comment 12•14 years ago
|
||
This addon https://next.addons.mozilla.org/en-US/firefox/addon/6028/ has 0 reviews, but clicking on the link https://next.addons.mozilla.org/en-US/firefox/reviews/display/6028 shows 3 reviews
Assignee | ||
Updated•14 years ago
|
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•14 years ago
|
Target Milestone: Future → 5.11.7
Verified FIXED: In Zamboni, https://preview.addons.mozilla.org/z/en-US/firefox/addon/1865/reviews/ has 1,851 reviews listed, which matches its details page https://preview.addons.mozilla.org/en-US/firefox/addon/1865/, while Remora still has 1,712 reviews: https://preview.addons.mozilla.org/en-US/firefox/reviews/display/1865
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
•