ETT-1332 My Collections won't display page 2#193
Merged
Conversation
- This bug affects all "lists of collections" (NOT "lists of collection items" i.e., items in a single collection) - The pagination math behind how the results array is sliced, is incorrect in that it does not multiply by items per page - Since we have a nice `Data::Page` object created at the end of the routine, I just move it ahead of the slicing and adjust for 0-based vs 1-based indexing. - The `Data::Page` code uses a config value for items per page; the bug locale uses hardcoded `100`; I swapped in the former.
carylwyatt
approved these changes
Mar 10, 2026
Member
carylwyatt
left a comment
There was a problem hiding this comment.
It's truly amazing that no one has reported this bug before now! Excellent sleuthing and fix.
I tested jumping to page 47 of results and paging my way back and forth. It all looks in order! Approve!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Data::Pageobject created at the end of the routine, I just move it ahead of the slicing and adjust for 0-based vs 1-based indexing.Data::Pagecode uses a config value for items per page; the bug locale uses hardcoded100; I swapped in the former.Reviewer:
Compare production vs dev-2 (or your own version):
-------2024_REFERENCESfollowed by'Generations', continuing on down to the last entry1934.'Generations'but the dev-2 version starts with1835which I think we can be confident is the beginning of the correct slice.