08-Jul-2026 — Joint walk leaders: display, export and CSV fixes ref #302

build 754 — commit 697fa76

What's new

Joint walk leaders now behave consistently across the site and in the Walks Manager export. Their names display in the same abbreviated style as single leaders, the export sends every leader in the official semicolon-separated format, and the pre-export checks validate each name individually. Walk web addresses are always plain ASCII and resolve to the correct walk even when many walks share a title, and the export page no longer reports false description differences caused by typographic punctuation or doubly-encoded text coming back from Walks Manager. Setting joint leaders on a walk no longer corrupts the primary leader's member record. CSV files are now received and parsed the same way everywhere.

At a glance

• Joint walk leaders display abbreviated (e.g. Jane S; John J) on the programme, walk pages and map popups, while full names are kept for Walks Manager matching
• The Walks Manager export includes every joint leader, semicolon-separated, in the format Walks Manager expects
• The pre-export check flags any individual leader name that looks abbreviated, so uploads no longer fail with "Walk leader not found"
• Walk web addresses no longer contain accented characters, and walks with similar titles open the correct walk
• Export validation reports an invalid website link before upload rather than failing at Walks Manager
• False "Description difference" results on the export page are eliminated, including where Walks Manager returns a plain hyphen for a typographic dash or a doubly-encoded ampersand
• Saving a walk with joint leaders keeps the leader's member record intact instead of overwriting their Walks Manager contact name with the joint text

Technical changes

• defaultDisplayName abbreviates each name in a joint leader list; MemberNamingService.createDisplayNameFromContactName delegates to it, removing duplicated abbreviation logic
• Walks map popups use fields.contactDetails.displayName instead of raw walk_leader.name
• Import preserves the full joint pairing on walk_leader.name and publishing.ramblers.contactName while writing the abbreviated form to contactDetails.displayName; member creation from imported leaders uses the full contact name
• walkLeader() exports the normalised semicolon-separated list; abbreviatedWalkLeaderNames() validates each listed name via abbreviatedWalksManagerContactName
• slugRegexFor anchored to (?:^|/)slug$ so a slug only matches a URL that is exactly it or ends with /-plus-it; the previous unanchored form also poisoned urlFromTitle uniqueness dedup; same pattern applied to cms-client.groupEventBySlug via new shared slug-matching module
• toKebabCase and toSlug transliterate accents (NFD normalise plus strip combining marks) so generated slugs are plain ASCII; toWalkExport validates the website link for non-ASCII characters
• replaceSpecialCharacters normalises en-dash and em-dash to hyphen-minus, matching how Walks Manager downgrades typographic dashes, so the export comparison stops flagging dash-only differences
• htmlToPlainText decodes HTML entities repeatedly until stable, collapsing doubly-encoded values such as &
• syncWalksManagerContactNameToMember writes only the first-listed leader name back to the member (via firstWalkLeaderName), so a joint contact name no longer overwrites the primary member's contactId with the whole joint string
• New STANDARD_CSV_PARSE_OPTIONS shared by the walks importer, member-bulk-load and parish CSV import; duplicate FileReader methods merged into csvRowsFromFile; dead walk-import-from-walks-manager component deleted
• Tests: joint-walk-leaders spec added; accent transliteration, per-name validation, dash and doubly-encoded entity, and slug-boundary cases covered; client 859 passing, server 841 passing