Cache pagination pages properly #7089
Merged
+36
−3
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.
Description
Fixes #7088
Here we are fixing a regression from that PR: #6984
We now can cache pagination pages for terms (categories, tags, custom taxonomies like product_cat for woocommerce, ...etc.)
Type of change
Detailed scenario
To reproduce this issue, you need to visit a category page starting from the second page in pagination, before this PR, you will find it not cached.
Technical description
Documentation
We check if we are in a paged page so compare the urls with page query variable to match properly.
New dependencies
No
Risks
Do u know if we have any query variable like paged one or not?
Mandatory Checklist
Code validation
Code style
Additional Checks