If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Issues in Review Add-ons->Logs page from Content Tools

RESOLVED WONTFIX

Status

Marketplace
Developer Pages
P3
normal
RESOLVED WONTFIX
2 years ago
2 years ago

People

(Reporter: ValentinaP, Assigned: ngoke)

Tracking

Avenir
2016-01-26
x86_64
Windows 7
Points:
---

Details

(Whiteboard: [marketplace-transition][possible_future_need])

(Reporter)

Description

2 years ago
Steps to reproduce:
1. Load MP-stage Content Tools page https://marketplace.allizom.org/content/ 
2. Go to “Firefox OS Add-ons”- “Review Add-ons” page
3. Click “Logs” link
4. Navigate through pages using “Next Page/Prev Page”

Expected results:
If there are more than one page, the buttons are available. 
Every time  the buttons are clicked other add-ons are displayed in the page and the page number is changing. “Prev Page” button becomes available after first click on “Next Page”.

Actual results:
Same add-ons are displayed in every page although the page number is changing in the URL. “Prev Page” button does not become available after first click in the “Next Page” button.

Notes/Issues:
Verified on FF46(Win 7). Issue is reproducing on MP-stage and MP-dev.
Screencast for this issue: http://screencast.com/t/keksDxz04M

Updated

2 years ago
Assignee: nobody → kngo
Priority: -- → P3
Target Milestone: 2016-01-19 → 2016-01-26
(Reporter)

Comment 1

2 years ago
Also, the search field disappears after clicking one time on the "Next Page" blue button.
Please see the screencast: http://screencast.com/t/aIsBrwO5Rso
(Assignee)

Comment 2

2 years ago
Workaround to use the search function

Going to wontfix given the activity on the logs page. The first page gives results back to December 25th, and the activity is slowing. So I think what is there is usable.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX

Updated

2 years ago
Whiteboard: [marketplace-transition][possible_future_need]
You need to log in before you can comment on or make changes to this bug.