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 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
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 showing all three pages now accessible: