Closed Bug 1227656 Opened 10 years ago Closed 10 years ago

Clicking on a search result containing add-ons returns a 404

Categories

(Marketplace Graveyard :: Consumer Pages, defect, P2)

x86
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
2016-03-29

People

(Reporter: krupa.mozbugs, Assigned: spasovski)

Details

(Whiteboard: [ktlo])

steps to reproduce: 1. Launch marketplace-dev app on your 2.5 device 2. Switch to the add-ons tab 3. Search for M in status bar 4. Click the add-on in the search results expected behavior: add-on detail page loads actual behavior: add-on details page returns a 404 since we are loading https://marketplace-dev.allizom.org/api/v2/fireplace/app/m-in-status-bar/?cache=1&dev=firefoxos&lang=en-US&limit=10&pro=%3D%2F%2F%2F%2F%2F%2F%2F%2FLw%3D%3D.54.9&region=us&vary=0 basically trying to find an app when the user is looking for an add-on
Not just a model caching issue (through that's part of it, see appOrWebsite() https://github.com/mozilla/fireplace/blob/master/src/media/js/helpers_local.js#L159 ) : all templates for search, product list, call app_tile(). Despite the name, that macro knows how to handle websites, but I don't think it knows how to handle add-ons correctly - there is a separate macro for add-ons.
Revised STR: You don't need to switch the the add-ons tab, you just need to search for something that will return add-ons. The add-on listing page is ok, it's the search page that's wrong when add-ons are shown in it.
Summary: Clicking on a search result returns a 404 since we store model entries in the cache as websites even though they are addons → Clicking on a search result containing add-ons returns a 404
Priority: -- → P2
Whiteboard: [ktlo]
Target Milestone: --- → 2015-12-08
Assignee: nobody → mpillard
According to mat, this is a fireplace issue.
Assignee: mpillard → dspasovski
Can't seem to repro this anymore please reopen if still an issue.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Target Milestone: 2015-12-08 → 2016-03-29
You need to log in before you can comment on or make changes to this bug.