{"id":"69e88c801ffe81f1664ec36a","title":"2026 04 22 Issue 247","path":"how-to/committee/release-notes/2026-04-22-issue-247","contentMarkdown":"# 22-Apr-2026 — sync pagination widget page count with paginated page size [closes #247](https://github.com/nbarrett/ngx-ramblers/issues/247)\n\n## [build 619](https://github.com/nbarrett/ngx-ramblers/actions/runs/24768904941) — [commit 4825ab3](https://github.com/nbarrett/ngx-ramblers/commit/4825ab329c64015f82c207d727e0d4561b659fe1)\n\n_____\n\n\n\n- The NGX-Ramblers pagination component defaults its itemsPerPage to\n15 when the input is not bound. The events list components paginate\nwith a different page size (8 for the events-header flow used in\ndynamic content rows, 10 for events-full), so with fewer than ~15\nitems the widget would render fewer page buttons than the\nupdatePaginationStatus alert reported. On [Winchester Walking Weekend Walks Page](https://winchesterwalkingweekend.org.uk/walks) the\nalert said \"1 to 8 of 18 events - page 1 of 3\" but the widget only showed buttons 1 and 2, leaving page 3 unreachable.\n\n- Events Row now accepts an itemsPerPage input and forwards it\nto <pagination>, defaulting to 10 for components that do not set it\n- events.ts passes its pageSize (8) as itemsPerPage to\napp-events-header, and also uses it for the new repeated pagination\nrendered below the card list\n- Events Row now binds itemsPerPage to its pageSize (10) on the\nshared paginationControls ng-template, fixing the same latent\ninconsistency that would have surfaced at totals where\nceil(total/10) and ceil(total/15) diverge.\n- See below for corrected pagination control On [Winchester Walking Weekend Walks Page](https://winchesterwalkingweekend.org.uk/walks) showing all three pages now accessible:\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/ca37c0b6-274a-43d8-aa2c-852cd140b1d7.jpeg)","contentHtml":"<h1>22-Apr-2026 — sync pagination widget page count with paginated page size <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/247\">closes #247</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/24768904941\">build 619</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/4825ab329c64015f82c207d727e0d4561b659fe1\">commit 4825ab3</a></h2>\n<hr>\n<ul>\n<li><p>The NGX-Ramblers pagination component defaults its itemsPerPage to\n15 when the input is not bound. The events list components paginate\nwith a different page size (8 for the events-header flow used in\ndynamic content rows, 10 for events-full), so with fewer than ~15\nitems the widget would render fewer page buttons than the\nupdatePaginationStatus alert reported. On <a href=\"https://winchesterwalkingweekend.org.uk/walks\">Winchester Walking Weekend Walks Page</a> the\nalert said &quot;1 to 8 of 18 events - page 1 of 3&quot; but the widget only showed buttons 1 and 2, leaving page 3 unreachable.</p>\n</li>\n<li><p>Events Row now accepts an itemsPerPage input and forwards it\nto <pagination>, defaulting to 10 for components that do not set it</p>\n</li>\n<li><p>events.ts passes its pageSize (8) as itemsPerPage to\napp-events-header, and also uses it for the new repeated pagination\nrendered below the card list</p>\n</li>\n<li><p>Events Row now binds itemsPerPage to its pageSize (10) on the\nshared paginationControls ng-template, fixing the same latent\ninconsistency that would have surfaced at totals where\nceil(total/10) and ceil(total/15) diverge.</p>\n</li>\n<li><p>See below for corrected pagination control On <a href=\"https://winchesterwalkingweekend.org.uk/walks\">Winchester Walking Weekend Walks Page</a> showing all three pages now accessible:</p>\n</li>\n</ul>\n<p><img src=\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/ca37c0b6-274a-43d8-aa2c-852cd140b1d7.jpeg\" alt=\"\"></p>\n"}