Closed Bug 750001 Opened 12 years ago Closed 12 years ago

[Firefox Flicks] Search by category, region or keyword is broken

Categories

(Websites :: Firefox Flicks, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: shollmann, Assigned: osmose)

Details

Description
When you search by category, region or keyword and then you change to another page of the results search, the website shows all the results without filtering them.

Steps
1- Go to videos
2- Choose Latin America in region
3- Click on search
4- Go to the bottom and click on page number 2

Problem
When you change of page number, the website redirects to https://firefoxflicks.mozilla.org/en-US/recent?limit=&page=2 but it should redirect to https://firefoxflicks.mozilla.org/en-US/recent?category=all&region=latin_america&page=2
Assignee: nobody → mkelly
Target Milestone: --- → 1.5
Summary: [Firefox Flicks] When you search by category, region or keyword and then you change to another page of the results search, the website shows all the results without filter them → [Firefox Flicks] Search by category, region or keyword is broken
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
This is still broken
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Resolved doesn't mean the bugfix has been released. QA needs to verify the fix and then it will go into the next possible release. I will work on getting this verified and out as soon as possible.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
(In reply to Chris Beard from comment #2)
> This is still broken

As Christie mentioned, "resolved fixed" does not always mean it is live on the website. Since no developer has access to push changes to production, a QA engineer must first verify the fix. The workflow in bugzilla is set up that QA only verify items that have been set to "resolved fixed". If a bug is left "open", QA will not verify it and it will not be released on the public website. Once a QA engineer verifies the bug, it will ready to go out on the next available release executed by IT. 

I will let Christie update us when it has been verified on dev/stage and when IT can release the fix.
Thanks Raymond for getting this through QA phases today.
You are welcome. Thanks to everyone that helped push this
Great guys! It's working perfectly :)
You need to log in before you can comment on or make changes to this bug.