Deleting all rows of last table page blocks user from continuing #4438
Unanswered
robbedekien
asked this question in
Ideas & Feature Requests
Replies: 2 comments
-
|
@crynobone have you perhaps been able to take a look at this? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@crynobone could this get another look please? This current UX is a blocking problem for our Client. Or is there any way around this issue? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
First off, if this should be a discussion, my apologies and feel free to transform this to a discussion.
When Deleting all remaining rows of the last page of a table the user gets the typical
No :resource matched the given criteria.message and cannot navigate back to a previous page as the table thinks there are no items of that resource at all.I understand why this is happening because the
resource_pagequery parameter is set. You can easily replicate this by setting the parameter to a value that is higher than the number of pages.This also happens with destructive actions that have been called for all items on the last page.
Would it be possible to implement a fallback either in the front or backend when trying to access a page that is higher than the number of available pages?
Detailed steps to reproduce the issue on a fresh Nova installation:
Alternative method:
resource_page=xwith x being a value greater than the number of available pagesBeta Was this translation helpful? Give feedback.
All reactions