Implemented handling of URLs with pagination segments for PagePathHistory module #1036
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The core module
PagePathHistory
didn't handle URLs with pagination segments until now.Steps to reproduce the problem
/objects/
/objects/page2
/objects/page3
PagePathHistory
module in the admin.objects-new
./objects/
works flawlessly by redirecting to the now correct URL/objects-new/
./objects/page2
leads to a 404 Page not found error instead of redirecting to the now correct URL/objects-new/page2
.Patch
This patch adds basic handling of URLs with pagination segments to
PagePathHistory
. Redirection after changing page URL prefixes is not supported, though.