{"id":"6a666ce9ed5d9c4b976bb9fe","title":"2026 07 26 Issue 302","path":"how-to/committee/release-notes/2026-07-26-issue-302","contentMarkdown":"# 26-Jul-2026 — publish leader diffs without confusing display and contact names [ref #302](https://github.com/nbarrett/ngx-ramblers/issues/302)\n\n## [build 795](https://github.com/nbarrett/ngx-ramblers/actions/runs/30218005751) — [commit 48e8030](https://github.com/nbarrett/ngx-ramblers/commit/48e80304b3bef2145e4a97d38b0d1a16d493efab)\n\n_____\n\nExport and the walk-page Publish action treat website display names and Walks Manager contact names as different fields. Leader changes use the contact name, and when Walks Manager does not disclose a leader they fall back to the previous contact name in walk history so a real change (for example Deborah Kellond to Nick Barrett) is still selected for edit-in-place and named in the status text. A successful publish records a published-to-Ramblers history event so later leader compares have a clear baseline.\n\nChoosing a walk leader (or other advanced filters) no longer expands Past Year, Past Month and similar relative ranges to All Time. The selected preset stays in force, so a leader search on Past Year still only covers that year rather than every walk since the earliest record.\n\n- display name is for this site only; contact name is for CSV and Walks Manager matching\n- compare contact name to the listed Walks Manager leader when a name is present\n- if Walks Manager hides the name, use the prior contact name from walk events\n- status and Publish tooltip show before and after contact names\n- leader updates on Walks Manager use edit-in-place, not a full walk replace\n- a published-to-Ramblers history event is written after a successful publish\n- Past Year (and other relative presets) stay put when you add a walk leader filter\n- The URL keeps both the preset name and matching date-from / date-to values\n- Search summary text only names a preset when the dates still match that preset\n\n- `walk-leader-fields` accessors and field-role contract tests\n- `remoteWalksManagerContactNameForCompare` blends listed name with `priorWalkLeaderContactName`\n- fuzzy match for abbreviated surnames (for example Jenny B. / Jenny Brown)\n- `SelectWalkLeaders` Serenity task for basic-information edit\n- walk-view re-checks Publish after system config loads\n- `EventType.PUBLISHED_TO_RAMBLERS` / `publishedToRamblersEvent` after Ramblers upload\n- Stop `filterSelectType` from always calling `applyFilterRangePreset` (All Time)\n- Constrain criteria to the selected relative preset when the date span is much wider\n- Write `date-range-preset` with criteria and prefer the active preset range when resolving search dates\n- Import `resolvePresetByLabel` for summary matching","contentHtml":"<h1>26-Jul-2026 — publish leader diffs without confusing display and contact names <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/302\">ref #302</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/30218005751\">build 795</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/48e80304b3bef2145e4a97d38b0d1a16d493efab\">commit 48e8030</a></h2>\n<hr>\n<p>Export and the walk-page Publish action treat website display names and Walks Manager contact names as different fields. Leader changes use the contact name, and when Walks Manager does not disclose a leader they fall back to the previous contact name in walk history so a real change (for example Deborah Kellond to Nick Barrett) is still selected for edit-in-place and named in the status text. A successful publish records a published-to-Ramblers history event so later leader compares have a clear baseline.</p>\n<p>Choosing a walk leader (or other advanced filters) no longer expands Past Year, Past Month and similar relative ranges to All Time. The selected preset stays in force, so a leader search on Past Year still only covers that year rather than every walk since the earliest record.</p>\n<ul>\n<li><p>display name is for this site only; contact name is for CSV and Walks Manager matching</p>\n</li>\n<li><p>compare contact name to the listed Walks Manager leader when a name is present</p>\n</li>\n<li><p>if Walks Manager hides the name, use the prior contact name from walk events</p>\n</li>\n<li><p>status and Publish tooltip show before and after contact names</p>\n</li>\n<li><p>leader updates on Walks Manager use edit-in-place, not a full walk replace</p>\n</li>\n<li><p>a published-to-Ramblers history event is written after a successful publish</p>\n</li>\n<li><p>Past Year (and other relative presets) stay put when you add a walk leader filter</p>\n</li>\n<li><p>The URL keeps both the preset name and matching date-from / date-to values</p>\n</li>\n<li><p>Search summary text only names a preset when the dates still match that preset</p>\n</li>\n<li><p><code>walk-leader-fields</code> accessors and field-role contract tests</p>\n</li>\n<li><p><code>remoteWalksManagerContactNameForCompare</code> blends listed name with <code>priorWalkLeaderContactName</code></p>\n</li>\n<li><p>fuzzy match for abbreviated surnames (for example Jenny B. / Jenny Brown)</p>\n</li>\n<li><p><code>SelectWalkLeaders</code> Serenity task for basic-information edit</p>\n</li>\n<li><p>walk-view re-checks Publish after system config loads</p>\n</li>\n<li><p><code>EventType.PUBLISHED_TO_RAMBLERS</code> / <code>publishedToRamblersEvent</code> after Ramblers upload</p>\n</li>\n<li><p>Stop <code>filterSelectType</code> from always calling <code>applyFilterRangePreset</code> (All Time)</p>\n</li>\n<li><p>Constrain criteria to the selected relative preset when the date span is much wider</p>\n</li>\n<li><p>Write <code>date-range-preset</code> with criteria and prefer the active preset range when resolving search dates</p>\n</li>\n<li><p>Import <code>resolvePresetByLabel</code> for summary matching</p>\n</li>\n</ul>\n"}