# 22-Apr-2026 — sync pagination widget page count with paginated page size [closes #247](https://github.com/nbarrett/ngx-ramblers/issues/247)

## [build 619](https://github.com/nbarrett/ngx-ramblers/actions/runs/24768904941) — [commit 4825ab3](https://github.com/nbarrett/ngx-ramblers/commit/4825ab329c64015f82c207d727e0d4561b659fe1)

_____



- The NGX-Ramblers pagination component defaults its itemsPerPage to
15 when the input is not bound. The events list components paginate
with a different page size (8 for the events-header flow used in
dynamic content rows, 10 for events-full), so with fewer than ~15
items the widget would render fewer page buttons than the
updatePaginationStatus alert reported. On [Winchester Walking Weekend Walks Page](https://winchesterwalkingweekend.org.uk/walks) the
alert said "1 to 8 of 18 events - page 1 of 3" but the widget only showed buttons 1 and 2, leaving page 3 unreachable.

- Events Row now accepts an itemsPerPage input and forwards it
to <pagination>, defaulting to 10 for components that do not set it
- events.ts passes its pageSize (8) as itemsPerPage to
app-events-header, and also uses it for the new repeated pagination
rendered below the card list
- Events Row now binds itemsPerPage to its pageSize (10) on the
shared paginationControls ng-template, fixing the same latent
inconsistency that would have surfaced at totals where
ceil(total/10) and ceil(total/15) diverge.
- See below for corrected pagination control On [Winchester Walking Weekend Walks Page](https://winchesterwalkingweekend.org.uk/walks) showing all three pages now accessible:

![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/ca37c0b6-274a-43d8-aa2c-852cd140b1d7.jpeg)