You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating System and Version: macOS Catalina 10.15.7 (19H15)
Browser type and version: Chrome 87.0.4280.67
Reproduction Repository: n/a
Description:
When visiting a resource page I am able to change the Per Page drop down to load more than the default number of records. When I do this, ?users_per_page=[chosen option] is appended to the URL.
However, if I refresh this page, ?users_per_page= is ignored.
I would like and expect this value to be recognised and utilised, especially since I can link to other filter options by serialising that data. Alternatively, I would expect ?users_per_page= to be handled in the same way as the other filter options (i.e. by being passed as a serialised string).
Detailed steps to reproduce the issue on a fresh Nova installation:
Visit a fresh resource page (e.g. Users).
Change the Per Page option to something other than the default (e.g. 100).
Observe that more rows are loaded successfully.
Refresh the page.
Observe that the URL still has ?users_per_page=[chosen option] in it, but value in the Per Page option has reverted back to the default and the number of rows loaded also adheres to the default.
The text was updated successfully, but these errors were encountered:
Description:
When visiting a resource page I am able to change the Per Page drop down to load more than the default number of records. When I do this, ?users_per_page=[chosen option] is appended to the URL.
However, if I refresh this page, ?users_per_page= is ignored.
I would like and expect this value to be recognised and utilised, especially since I can link to other filter options by serialising that data. Alternatively, I would expect ?users_per_page= to be handled in the same way as the other filter options (i.e. by being passed as a serialised string).
Detailed steps to reproduce the issue on a fresh Nova installation:
The text was updated successfully, but these errors were encountered: