-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pagination links not working because PagingListOfT.PageParameterName is set to 'page' which is a reserved route name. #21
Comments
This would be a breaking change, old code won't work any more. We must search for a solution for that. |
Added a PageParameterName to the PagingOptions. You can set this to for example pageIndex. Make sure you also rename the parameters of your Actions.
|
I am leaving this comment for anyone else who might encounter an issue similar to mine. In the documentation, it mentions a fix for applications with Areas. In my specific instance, my application is Multitenant, and also uses Areas. Thus the routes are something like this: None of the fixes mentioned here worked for me. The workaround for me was, instead of using:
I used the snippet below (taken from the original post), and that worked!:
Thank you for this package. |
Same here. |
THANK U SO MUCH UR HELPING ME |
There is more context on this question I submitted on StackOverflow. Right now the code is using a reserved route name called 'page', it doesn't work when the app has Identity features.
Here's a solution: change PagingListOfT.PageParameterName default name.
Additional: Insert in PagingOptions a 'public string PageLinkUrlGetName { get; set; } = "bookpage";' option.
The text was updated successfully, but these errors were encountered: