DayDreamer Posted February 20 Posted February 20 This used to work. Still works on the Issue List tab, where multiple pages are accessed with << prev, 1, 2, 3, ..., next, >>
robertmiller Posted Thursday at 06:48 AM Posted Thursday at 06:48 AM The Issue List tab still paginating while another view has lost its page controls suggests the problem is isolated to that specific view's rendering rather than the underlying data query. Worth comparing how the two tabs build their pagination markup—if the broken one relies on a component that changed recently, that would explain why only it regressed. I don't have access to the AFKtrack source, so I can't confirm which version introduced the change, but checking whether the missing controls still exist in the DOM but are hidden would narrow it down quickly.
nicholasseward Posted 18 hours ago Posted 18 hours ago The DOM check is the right first step: if the page links are present but hidden, it's a CSS or conditional-display regression in that view, not the query. If they're absent entirely, the pagination markup isn't being generated, which points to the component the other post mentioned. Comparing the rendered markup between the two tabs side by side should tell you which case you're in. If the broken tab uses a different list component than Issue List, that difference alone may explain why only one view lost its controls.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now