Closed
Bug 1437068
Opened 7 years ago
Closed 7 years ago
Link to add-on reviews page from Add-on Manager redirects to AMO Reviewer Tools
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1402064
People
(Reporter: LexaSV, Unassigned)
Details
Attachments
(1 file)
398.64 KB,
image/gif
|
Details |
[Affected versions]:
- Firefox 60.0a1(20180201192139)
[Affected Platforms]:
- Windows 10x64
- All Mac OS X 10.13.2
- Linux 12.04 LTS
[Steps to reproduce]:
1. Start AMO-stage on the following buid https://queue.taskcluster.net/v1/task/F8_PEL5JTwmnDnCRkfNTSQ/runs/0/artifacts/public/build/target.zip
2. Install an extension (i.e. https://addons.allizom.org/en-US/firefox/addon/noscript/)
3. Go to about:addons - Extensions - and look for the installed add-on
4. Click on 'More' to view more details about the installed extension
5. In the Rating section, click on <# reviews> link to view all the available reviews for this add-on
[Expected results]:
The link redirects to https://addons.allizom.org/en-US/firefox/addon/noscript/reviews/
[Actual results]:
The link redirects to https://reviewers.addons.allizom.org/en-US/reviewers/review/noscript, which is the Reviewer Tools domain
Notes:
Reproduced on AMO-stage, Win10x64 with the following build https://queue.taskcluster.net/v1/task/F8_PEL5JTwmnDnCRkfNTSQ/runs/0/artifacts/public/build/target.zip
Comment 1•7 years ago
|
||
Andrew, see above, I'm just using the review_url property. Should I be using something else or is this a problem on the server side?
Flags: needinfo?(awilliamson)
Comment 2•7 years ago
|
||
review_url is actually the url to the reviewer tools review page, so frontend could display a link to it for privileged users. The equivalent for user ratings would be `ratings_url`... but we don't have that in the API - frontend renders the ratings page itself so never needed a link.
If you want a link we could add `ratings_url` to the API (issue please) - it's just Addon.url + "ratings/" (or even more confusingly, Addon.url + "reviews/")
Flags: needinfo?(awilliamson)
Comment 3•7 years ago
|
||
This doesn't need to be tracked separately, it will get fixed in 1402064
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
No longer blocks: 1402064
status-firefox60:
affected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•