- 🇳🇿New Zealand quietone
Two years a maintainer asked for more information about this problem, including steps to reproduce. The same information was asked for again, 6 months ago. Since we need that information to continue here, and it is has not been supplied I am closing this issue.
If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue → (starting from "Install Drupal core").
- Status changed to Postponed: needs info
21 days ago 5:36pm 5 December 2024 - 🇺🇸United States jnicola
Just ran into this in 10.3.x with views on the USDOJ website where the pager would sometimes not render without a discernable rhyme or reason. Sure enough, adjusting the pager ID to 99 ensured that there weren't issues.
I don't have steps to reproduce from scratch, nor the liberty of time to faff around with reproducing this, but the pager ID collision does appear to be something that can still happen.
Stands to reason you could perhaps write a test for this that has a view rendering content, some of which has a pager on it, and both using the same pager ID of 0, but the view in the content pager is empty, which in turn bubbles up to the overall view pager ID.
I wish there were an easy solution such as setting pager ID to the views limit + 1, but if the overal view is 25, and the view in the content displaying in the view is limited to 25, you'd have the same pager ID collision again.
Why does pager ID need to be numeric anyways? If it could be alphanumeric you could go view-name_dislay-name?