Closed
Bug 496655
Opened 15 years ago
Closed 15 years ago
Tag Page: Functionality
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
addons.mozilla.org Graveyard
Public Pages
Tracking
(Not tracked)
RESOLVED
FIXED
5.0.7
People
(Reporter: mikelee, Assigned: markwunsch)
References
Details
(Whiteboard: [webmocha])
Attachments
(1 file)
4.55 KB,
patch
|
Details | Diff | Splinter Review |
As indicated on the Tagging Spec (http://docs.google.com/Doc?docid=dds6vwb4_1dxwx5vg3&hl=en) 1.10 - Tag page A tag page should have an URL that is easy to understand, like "addons.mozilla.org/tag/photography". This page should contain a listing (similar to a search results page) for add-ons with a specific tag. This bug involves: + CakePHP code + unit tests via Simpletest
Updated•15 years ago
|
Whiteboard: [webmocha]
This is basically a Search Results page (bug 488519), except that the UI wouldn't have text reading "Search Results, Showing 1-10 of 401 results..." at the top and "Refine Results" in the left column.
Updated•15 years ago
|
Assignee: expatrick → markwunsch
ETA: possibly tomorrow. Yem and Mark looking into this now.
Comment 5•15 years ago
|
||
(In reply to comment #4) > ETA moved to EOD Monday. Status?
Notes from Mark: I resolved my bugs involving SERP so unless something mysterious appears I'm trying to focus in on Tag Pages, which have caused me endless head scratching. I'm spinning my wheels about it. Originally, since the UI for SERP and Tag pages were so similar, it made sense to not repeat the code and instead to make a route amo/tag/tag_name => amo/search?tag=tag_name But I ran into a bunch of obstacles with this approach. After talking it over, it makes more sense to do this the proper way (even if some code will be repeated) by creating this functionality in the Tag controller. I'd like to have this knocked out at the very latest by eod tomorrow night.
Assignee | ||
Comment 7•15 years ago
|
||
Assignee | ||
Comment 8•15 years ago
|
||
The attached patch updates the tag controller with a new function, display(). Took the naming convention from the addons controller. Display takes a tag_name and runs a search() with it. Had to pull in some additional Models and Components. In addition, I also updated the routes so you can have what the spec describes: addons.mozilla.org/tag/tag_name as well as addons.mozilla.org/tags/display/tag_name I added the UI task (bug 496657) as a dependency to this bug. The new view will be attached there.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•9 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
•