Bug 1025722 - Pagination issue: no way back from More>>
Summary: Pagination issue: no way back from More>>
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 3.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 4.0
Assignee: Julie Pichon
QA Contact: Ami Jeain
URL:
Whiteboard:
: 1030549 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-01 11:37 UTC by Jaroslav Henner
Modified: 2015-02-15 22:02 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-13 11:37:32 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1212174 0 None None None Never

Description Jaroslav Henner 2013-11-01 11:37:10 UTC
Description of problem:
One cannot go back if clicked on More >> in snapshots list.

Version-Release number of selected component (if applicable):
python-django-horizon.noarch          2013.1.3-1.el6ost    @puddle              

How reproducible:
always

Steps to Reproduce:
1. Have more than 20 snapshots
2. Click on More>> Under the snapshot list in /dashboard/project/images_and_snapshots/


Actual results:
Other images page is displayed, but there is no way to go back to the previous page other than going to /dashboard/project/images_and_snapshots/ directly.

Expected results:
 * buttons like << and >> displayed
 * page number displayed


Additional info:

Comment 2 Julie Pichon 2013-11-13 11:37:32 UTC
We're limited by the services APIs, which use the marker/limit system to determine how to paginate and navigate through result pages. There isn't much that can be done from the Horizon side at the moment.

See also https://bugs.launchpad.net/horizon/+bug/1212174 upstream for additional information and references to mailing list discussions on pagination.

Comment 3 Julie Pichon 2013-11-14 18:30:48 UTC
*** Bug 1030549 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.