Description of problem:
On the Subscriptions page, the default pagination is 20. However, if user changes it and tries to go back... well, their only options are "5, 10, 15, 25, 50".
Version-Release number of selected component (if applicable):
6.4.0 snap 10
Steps to Reproduce:
1. Upload a manifest to an Org (presumably a manifest with many subs) and navigate to Subscriptions.
2. Scroll to bottom of list, and note the default pagination.
3. Select a different pagination option and reload
4. Attempt to choose 20 again
"20" is not an option in the selector.
Obvious workaround is to navigate back to the subscriptions page via the UI.
But this is just silly.
I am not sure where in the UI, if anywhere, this is also a problem.
Created attachment 1455857 [details]
20 does not actually appear in selector.
IMHO 25 should be the default.
This also seems to be an issue on the repos page as well.
Changing component to WebUI as, per comment #3, it affects more than just the Subs page.
Pagination behaves like this when the default value in settings is configured to a value that's not in the list. Corey, could you look into your settings what value is there, please?
I suppose that's the point; either the default value in the setting should be one of those in the pagination page, or the default value should be added to the options.
It is strange experience from from a UI/user perspective, not to be able to return back to whatever the default value is.
(In reply to Corey Welton from comment #6)
> I suppose that's the point; either the default value in the setting should
> be one of those in the pagination page, or the default value should be added
> to the options.
> It is strange experience from from a UI/user perspective, not to be able to
> return back to whatever the default value is.
I think we should probably prepend the per page setting to the list of selectable values unless it equals one of the values already in the list.
Created redmine issue https://projects.theforeman.org/issues/24311 from this bug
Upstream bug assigned to email@example.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/24311 has been resolved.
VERIFIED on Sat6.4#18
Reproducer via comment #0
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.