Closed fnagel closed 2 years ago
Looks like this is an issue due to page_localized
aspect has the same default value "page" as the actual parameter. This might be the reason why EXT:news uses currentPage
instead of page
as parameter name.
If this really is the issue, we need to change the methods argument name and the routing config.
Changing the argument to currentPage
does not help. Seems this is an issue with our page_localized
prefix. Maybe a core bug.
Seems it's not about page_localized
but using "page" as a prefix (/page/{page-placeholder}
). Which seems strange as this is even the case when all arguments (controller action argument, pagination partial, routing config) have been changed to currentPage
. Only working solution would be using something like /page-{page-placeholder}
which is different to what we had before.
Any help appreciated.
Implemented a workaround by using /{post_page_localized}-{post_page}
for pagination routing.
I was not able to make pagination routing work.
When enable routing for pagination, the current page is no longer available in controller, not sure why... In addition, it breaks all other routes.
Any help appreciated!
See 09ba868b163603ab9fc8ac2e9f8be614c3a40c7e