{"id":"69b1f54c160f96869833696e","title":"2026 03 11","path":"how-to/committee/release-notes/2026-03-11","contentMarkdown":"# 11-Mar-2026 — Lightweight Booking System, Maps cleanup unused components, mail & walks fixes [#175](https://github.com/nbarrett/ngx-ramblers/issues/175)\n\n## [build 517](https://github.com/nbarrett/ngx-ramblers/actions/runs/22978121001) — [commit 6edae09](https://github.com/nbarrett/ngx-ramblers/commit/6edae09123092ead7878ccdb12c02afeba8e9e35)\n_____\n\nNote that during the development of this ticket, it transpired that there was a sizeable amount of clean up work that was required following issue [#12](https://github.com/nbarrett/ngx-ramblers/issues/12), as navigation from the walk summary → detail → edit and back was broken. The same issues were found with the same social event navigations. Several old components were deleted and the `social-event*` objects were renamed to `group-event*` in order to be more consistent with Ramblers data model.\n\n## Lightweight Booking System\nEvents can now accept bookings directly from any events page. When an event has `bookingEnabled: true` and a `maxCapacity` set on its fields, a **Book a Place** panel appears below the event details showing remaining capacity.\n### Admin — Booking (`/admin/bookings`)\nTo enable this feature, visit the above URL. A **bookings** button has also been added to the admin menu.\n\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/d60b2793-41a8-42b8-a0d6-5c03cfbc30b4.jpeg)\n\n- **Configuration tab**: Enable Booking on Events and choose which event types are enabled for bookings, default max capacity, max attendees per booking and member priority. \n- **Per-Event Detail** tab is the event-level booking admin view which lets you:\n - select an upcoming or existing bookable event\n - see each booking for that event in a table\n - view attendee names, email addresses, phone numbers, booking date, status, and places booked\n - spot waitlisted bookings separately from active ones\n - delete individual bookings if needed\n - download the selected event’s booking data as CSV\n - It is also used to prepare events before bookings open:\n - find an upcoming event from the selector\n - set or update that event’s max booking capacity even if nobody has booked yet\n - Select an event to see individual bookings with attendee\nnames, emails, phone numbers, and booking dates — also downloadable as CSV\n - Admin can delete bookings directly from the detail view\n- **Summary tab**: table of all bookable events with booked/capacity counts\n\n### Booking flow\n1. Visitors enter their name and email (required) plus optional phone number\n1. Additional attendees can be added (up to `maxGroupSize`, default 3)\n1. Clicking **Book Now** creates a booking and confirms with a success message\n1. The capacity counter updates in real time — once all places are taken the\npanel shows **Fully booked**\n1. An email is sent to the visitor and optionally the BCC address specified within the email configuration for Bookings.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/3c174bb5-16b7-4832-b042-bd9cf74be0b3.jpeg)\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/23125588-0eb2-4e87-8dc8-ac77937b294e.jpeg)\n\n\n### Cancellation flow\n1. After booking, a **Need to cancel a booking?** link appears\n1. The visitor enters their email to look up active bookings\n1. Each matching booking can be individually cancelled\n1. Cancellation is verified server-side: the email must match an attendee\non the booking, preventing unauthorised cancellations\n1. An email is sent to the visitor and optionally the BCC address specified within the email configuration for Bookings.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/437f5b31-ba12-4bd6-a224-756ed3ed3e08.jpeg)\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/464a11d2-8786-42b5-ad6a-447720df04e2.jpeg)\n\n## Booking Follow-up Enhancements\n### Booking email notifications\n- Booking workflows can now send confirmation, cancellation, waitlisted, and\nrestored emails using the configured booking notification template\n- Booking emails include attendee lists, event dates, salutation, and a direct\nlink back to the website event page\n- The event page link is passed from the current walk/group event view so the\nemail uses the same deep link already exposed in the UI\n### Booking configuration defaults\n- Added booking settings to walks config with defaults for enabled state,\nmaximum capacity, maximum attendees per booking, and member priority days\n- Added the walks config admin tab to manage those defaults centrally\n- Updated the unreleased walks config migration to seed booking defaults and to\nmove notification configuration role copies from `ccRoles` to `bccRoles`\n### Member priority and waitlist handling\n- During member priority periods, authenticated member bookings can displace\nnon-member bookings onto the waiting list when an event is full\n- Waitlisted bookings are restored automatically when places are freed by a\ncancellation and restored attendees are notified by email\n- Eligibility responses now expose member priority state and waiting list totals\n### Booking safeguards and lookup fixes\n- Prevent duplicate active or waitlisted bookings on the same event by attendee\nemail address\n- Fixed booking lookup responses to return API objects with `id`, allowing\ncancellation to work reliably after lookup\n- Added explicit validation for missing booking ids on cancellation requests\n- Cancellation entry points are available whenever an event already has bookings\n### Booking email configuration and workflow alignment\n- Booking notification configurations now behave as workflow-managed email\nconfigs instead of generic mailing-list selections\n- Booking notifications now use BCC recipient roles consistently, with support\nfor migrated legacy `ccRoles` data during the transition\n- Booking emails now send through the shared transactional mail sender logic so\nrecipient handling, BCC behaviour, template substitution, and Brevo request\nconstruction are maintained in one place\n### Walk and event view integration\n- Booking panels now render correctly on standalone deep-link walk pages after\nwalks config has loaded\n- Walk and group event views pass their canonical website links into booking\nworkflows so correspondence uses the same event URLs shown in related links\n- Booking form layout was refined for stacked narrow layouts and single-row wide\nlayouts, with panel spacing aligned to surrounding event panels\n### Migration consistency\n- Corrected booking-related config migrations to use the `config` collection,\nmatching the live mongoose model and runtime code\n### Global booking configuration and admin controls\n- Booking configuration is now stored in its own global `booking` config rather\nthan under `walks`, with environment setup and the unreleased migration moved\nto seed and migrate the new config cleanly before release\n- `/admin/bookings` now owns booking configuration through a dedicated\n**Configuration** tab instead of the walks config area\n- Booking configuration now supports per-event-type enablement so booking can\nbe turned on for walks, group events, and wellbeing walks independently\n### Per-event booking preparation\n- Booking admins can now search upcoming events from the existing autocomplete\npattern without typing before results appear\n- Upcoming event choices now include event type in the label for clarity\n- Admins can set event-specific maximum capacity before any bookings exist,\nallowing events to be prepared ahead of opening booking\n### Booking UX refinements\n- Cancellation lookup guidance now uses the same alert treatment as the rest of\nthe booking panel\n- Booking success and waiting-list messaging now use shared pluralisation\nhelpers for consistent wording\n- Group event and walk views now own their own booking panel spacing so page-\nspecific layout tuning no longer leaks through the shared booking component\n\n## GPX Parser: Support Route Elements\n- **Root cause**: GPX parser only handled `/` (track)\nelements but ignored `/` (route) elements. 37 of 39\nSevenoaks walking route GPX files use `` format, so only 2\nroutes were rendering on the map\n- **Fix**: added `parseRoute()` and `parseRoutePoints()` methods to\nconvert `/` elements into renderable `GpxTrack` objects\nalongside existing `` parsing\n- **Waypoint dedup**: changed `parseWaypoints()` from selecting\n`\"wpt, rtept\"` to just `\"wpt\"` — `` elements are now parsed\nas route tracks, not waypoints, preventing duplicate rendering\n## Map Viewport Hang Fix\n- **Root cause**: Dragging/zooming the map triggered an infinite feedback\nloop — `moveend` → `loadRoutes()` → layer reassignment + `fitBounds`\n→ Leaflet re-render → `moveend` again\n- **Debounced viewport handler**: 300ms debounce on `moveend`/`zoomend`\nprevents rapid-fire reloads during panning\n- **Re-entrancy guard**: `loadRoutesInProgress` flag skips concurrent\n`loadRoutes()` calls\n- **Suppress programmatic events**: `suppressViewportHandler` flag\nprevents layer/bounds assignment from re-triggering the viewport\nhandler (cleared after 200ms)\n- **Skip fitBounds on viewport reloads**: `loadRoutes(skipFitBounds)`\nparameter prevents `calculateFitBounds` on user-initiated pan/zoom,\nwhich was the primary loop trigger\n- **Removed cache eviction on viewport change**: the viewport filtering\nalready uses `currentBounds.intersects()` on cached data, so deleting\nand re-fetching GPX on every drag was unnecessary\n## Mail API Resilience (No API Key / Invalid Key)\n- **Short-circuit when no API key**: `MailMessagingService.initialise()`\nchecks `mailConfig.apiKey` after loading config — if absent, skips all\nBrevo API calls (account, lists, folders, templates) and sets safe\nempty defaults. Zero 401 errors in the console\n- **Short-circuit on account error**: if the account query fails (invalid\nkey), remaining Brevo calls are skipped with empty defaults\n- **Senders list guard**: `MailSendersListComponent` waits for the\n`mailMessagingConfig` via the `events()` observable before calling\nsenders/domain APIs — skips if `accountError` is set\n- **Create-or-amend sender guard**: checks `brevoAccountConfigured()`\nbefore calling `querySenders()`\n- **Mail provider stats guard**: `calculateMailProviderStats()` handles\n`this.list` being undefined when Brevo lists fail to load, showing\n\"No Brevo lists available\" instead of crashing\n- **List key values null safety**: added `?.` and `|| []` fallback when\n`brevo.lists.lists` is undefined\n- **Alert icon**: changed error alert icon from `faCircleCheck` to\n`faExclamationTriangle` for the account error panel\n## CommonDataService Double HTTP Request Fix\n- **Root cause**: `responseFrom()` used `.subscribe()` + `.toPromise()`\non a shared observable, causing two subscriptions and duplicate HTTP\nrequests\n- **Fix**: replaced with single `firstValueFrom()` call — one\nsubscription, one HTTP request, proper error propagation via `throw`\n## Config Save: Allow Clearing Sensitive Fields\n- **Root cause**: `restoreSensitiveFields()` in the backend config\ncontroller treated both missing keys AND falsy values (`\"\"`, `null`)\nas \"restore from DB\", making it impossible to clear the API key\n- **Fix**: changed condition from `!(k in incoming) || !incoming[k]` to\n`!(k in incoming)` — only restores when the key is truly absent\n(redacted), not when explicitly cleared\n## Mail Settings: Prevent Config Overwrite During Editing\n- **Root cause**: `MailMessagingService.initialise()` created new\nsubscriptions to `committeeConfig` and `systemConfigService` on every\ncall, causing accumulated subscriptions that re-emitted config and\noverwrote unsaved edits\n- **Fix**: moved one-time subscriptions to the constructor;\n`acceptNextConfigEmission` flag in `MailSettingsComponent` prevents\nsubscription emissions from overwriting local edits except after\nsave or undo\n## Domain API URL Refactor\n- Changed domain endpoints from path parameters\n(`/domains/:domainName/configuration`) to query parameters\n(`/domains/configuration?domainName=...`) across backend routes and\nfrontend service\n## Walk Search Layout\n- Alert inline when default filtering, own row with pagination/filters\n- Clear filters resets to default preset\n- Bug button hidden by default\n## Events\n- Bug button visibility fix\n\n### Server API for #175\n- `POST /api/database/booking` — create booking\n- `PUT /api/database/booking/:id` — update booking\n- `DELETE /api/database/booking/:id` — delete booking\n- `GET /api/database/booking/all` — list bookings (with query criteria)\n- `GET /api/database/booking/capacity/:eventId` — public capacity check\n- `POST /api/database/booking/lookup` — find bookings by event + email\n- `PUT /api/database/booking/cancel/:id` — cancel with email verification\n## Contact Us Persistence\nContact form submissions are now persisted to the database via\n`ContactInteractionService` and a new `/api/database/contact-interaction`\nendpoint. Each interaction records: name, email, subject, message, whether\nthe sender was anonymous, the recipient role, and a status\n(new/read/archived).\n## Social → Group Events Rename\nAll social event components, services, models, and routes have been renamed\nfrom `social-*` to `group-event-*` to align with the Ramblers API naming\nconvention. Key renames:\n- `SocialEditComponent` → `GroupEventEdit`\n- `SocialDisplayService` → `GroupEventDisplayService`\n- `SocialViewPage` → `GroupEventViewPage`\n- `SocialCard` → `GroupEventCard`\n- `social-events.model.ts` → `group-events.model.ts`\n- `social-auth-guard.ts` → `group-event-auth-guard.ts`\n## Removed Orphaned Code\nDeleted components and services no longer referenced anywhere:\n- `WalkList` (723 lines) — replaced by `EventsFull` CMS component\n- `GroupEventList` + sass\n- `GroupEventViewSelector`\n- `SocialViewSelector`\n- `SocialList` + sass\n- `SocialRoutingModule`\n- `SocialPopulationLocalGuard`\n- Hardcoded `PAGE_HEADER` and `ACTION_BUTTONS` anchors — walks and social\npages are now 100% content-managed\n## Event Navigation Fixes\n### Deep path dispatch (fixes wrong event for generic slugs)\nFor paths with 3+ segments (e.g. `/walks/weekends-away/swanage/day-2`),\npage content is now checked **before** event lookup. This prevents generic\nslugs like `day-2` from regex-matching unrelated events. Two-segment paths\n(e.g. `/walks/some-event-slug`) still try event lookup first.\n### Walk card title links (fixes pre-existing non-navigation)\n- `walkRouterLink()` now generates relative URLs so `routerLinkUrl()` returns\na valid path instead of null (absolute URLs were rejected as \"remote\")\n- Added `stopPropagation` on the title `` to prevent the parent card's\n`toggleView()` handler from intercepting the routerLink click\n### Edit/cancel navigation symmetry\n- `close()` strips `/edit` from the current path instead of reconstructing\nthe URL via `groupEventLink()`, which was reading the still-dirty URL\n- Added explicit `edit` and `new` routes to `walks-routing.module.ts` before\nthe `**` catch-all to prevent `/edit/edit/edit` URL corruption\n### Cleanup\n- `walksArea()` simplified to `urlService.area()` — removed stale fallbacks\nto `pageService.walksPage()?.href` and hardcoded `\"walks\"`\n","contentHtml":"

11-Mar-2026 — Lightweight Booking System, Maps cleanup unused components, mail & walks fixes #175

\n

build 517 — commit 6edae09

\n
\n

Note that during the development of this ticket, it transpired that there was a sizeable amount of clean up work that was required following issue #12, as navigation from the walk summary → detail → edit and back was broken. The same issues were found with the same social event navigations. Several old components were deleted and the social-event* objects were renamed to group-event* in order to be more consistent with Ramblers data model.

\n

Lightweight Booking System

\n

Events can now accept bookings directly from any events page. When an event has bookingEnabled: true and a maxCapacity set on its fields, a Book a Place panel appears below the event details showing remaining capacity.

\n

Admin — Booking (/admin/bookings)

\n

To enable this feature, visit the above URL. A bookings button has also been added to the admin menu.

\n

\"\"

\n
    \n
  • Configuration tab: Enable Booking on Events and choose which event types are enabled for bookings, default max capacity, max attendees per booking and member priority.
    • \n
  • Per-Event Detail tab is the event-level booking admin view which lets you:
      \n
    • select an upcoming or existing bookable event
      • \n
    • see each booking for that event in a table
      • \n
    • view attendee names, email addresses, phone numbers, booking date, status, and places booked
      • \n
    • spot waitlisted bookings separately from active ones
      • \n
    • delete individual bookings if needed
      • \n
    • download the selected event’s booking data as CSV
      • \n
    • It is also used to prepare events before bookings open:
      • \n
    • find an upcoming event from the selector
      • \n
    • set or update that event’s max booking capacity even if nobody has booked yet
      • \n
    • Select an event to see individual bookings with attendee\nnames, emails, phone numbers, and booking dates — also downloadable as CSV
      • \n
    • Admin can delete bookings directly from the detail view
      • \n
    \n
    • \n
  • Summary tab: table of all bookable events with booked/capacity counts
    • \n
\n

Booking flow

\n
    \n
  1. Visitors enter their name and email (required) plus optional phone number
    2. \n
  2. Additional attendees can be added (up to maxGroupSize, default 3)
    3. \n
  3. Clicking Book Now creates a booking and confirms with a success message
    4. \n
  4. The capacity counter updates in real time — once all places are taken the\npanel shows Fully booked
    5. \n
  5. An email is sent to the visitor and optionally the BCC address specified within the email configuration for Bookings.
    6. \n
\n

\"\"

\n

\"\"

\n

Cancellation flow

\n
    \n
  1. After booking, a Need to cancel a booking? link appears
    2. \n
  2. The visitor enters their email to look up active bookings
    3. \n
  3. Each matching booking can be individually cancelled
    4. \n
  4. Cancellation is verified server-side: the email must match an attendee\non the booking, preventing unauthorised cancellations
    5. \n
  5. An email is sent to the visitor and optionally the BCC address specified within the email configuration for Bookings.
    6. \n
\n

\"\"

\n

\"\"

\n

Booking Follow-up Enhancements

\n

Booking email notifications

\n
    \n
  • Booking workflows can now send confirmation, cancellation, waitlisted, and\nrestored emails using the configured booking notification template
    • \n
  • Booking emails include attendee lists, event dates, salutation, and a direct\nlink back to the website event page
    • \n
  • The event page link is passed from the current walk/group event view so the\nemail uses the same deep link already exposed in the UI
    • \n
\n

Booking configuration defaults

\n
    \n
  • Added booking settings to walks config with defaults for enabled state,\nmaximum capacity, maximum attendees per booking, and member priority days
    • \n
  • Added the walks config admin tab to manage those defaults centrally
    • \n
  • Updated the unreleased walks config migration to seed booking defaults and to\nmove notification configuration role copies from ccRoles to bccRoles
    • \n
\n

Member priority and waitlist handling

\n
    \n
  • During member priority periods, authenticated member bookings can displace\nnon-member bookings onto the waiting list when an event is full
    • \n
  • Waitlisted bookings are restored automatically when places are freed by a\ncancellation and restored attendees are notified by email
    • \n
  • Eligibility responses now expose member priority state and waiting list totals
    • \n
\n

Booking safeguards and lookup fixes

\n
    \n
  • Prevent duplicate active or waitlisted bookings on the same event by attendee\nemail address
    • \n
  • Fixed booking lookup responses to return API objects with id, allowing\ncancellation to work reliably after lookup
    • \n
  • Added explicit validation for missing booking ids on cancellation requests
    • \n
  • Cancellation entry points are available whenever an event already has bookings
    • \n
\n

Booking email configuration and workflow alignment

\n
    \n
  • Booking notification configurations now behave as workflow-managed email\nconfigs instead of generic mailing-list selections
    • \n
  • Booking notifications now use BCC recipient roles consistently, with support\nfor migrated legacy ccRoles data during the transition
    • \n
  • Booking emails now send through the shared transactional mail sender logic so\nrecipient handling, BCC behaviour, template substitution, and Brevo request\nconstruction are maintained in one place
    • \n
\n

Walk and event view integration

\n
    \n
  • Booking panels now render correctly on standalone deep-link walk pages after\nwalks config has loaded
    • \n
  • Walk and group event views pass their canonical website links into booking\nworkflows so correspondence uses the same event URLs shown in related links
    • \n
  • Booking form layout was refined for stacked narrow layouts and single-row wide\nlayouts, with panel spacing aligned to surrounding event panels
    • \n
\n

Migration consistency

\n
    \n
  • Corrected booking-related config migrations to use the config collection,\nmatching the live mongoose model and runtime code
    • \n
\n

Global booking configuration and admin controls

\n
    \n
  • Booking configuration is now stored in its own global booking config rather\nthan under walks, with environment setup and the unreleased migration moved\nto seed and migrate the new config cleanly before release
    • \n
  • /admin/bookings now owns booking configuration through a dedicated\nConfiguration tab instead of the walks config area
    • \n
  • Booking configuration now supports per-event-type enablement so booking can\nbe turned on for walks, group events, and wellbeing walks independently
    • \n
\n

Per-event booking preparation

\n
    \n
  • Booking admins can now search upcoming events from the existing autocomplete\npattern without typing before results appear
    • \n
  • Upcoming event choices now include event type in the label for clarity
    • \n
  • Admins can set event-specific maximum capacity before any bookings exist,\nallowing events to be prepared ahead of opening booking
    • \n
\n

Booking UX refinements

\n
    \n
  • Cancellation lookup guidance now uses the same alert treatment as the rest of\nthe booking panel
    • \n
  • Booking success and waiting-list messaging now use shared pluralisation\nhelpers for consistent wording
    • \n
  • Group event and walk views now own their own booking panel spacing so page-\nspecific layout tuning no longer leaks through the shared booking component
    • \n
\n

GPX Parser: Support Route Elements

\n
    \n
  • Root cause: GPX parser only handled <trk>/<trkpt> (track)\nelements but ignored <rte>/<rtept> (route) elements. 37 of 39\nSevenoaks walking route GPX files use <rte> format, so only 2\nroutes were rendering on the map
    • \n
  • Fix: added parseRoute() and parseRoutePoints() methods to\nconvert <rte>/<rtept> elements into renderable GpxTrack objects\nalongside existing <trk> parsing
    • \n
  • Waypoint dedup: changed parseWaypoints() from selecting\n"wpt, rtept" to just "wpt" — <rtept> elements are now parsed\nas route tracks, not waypoints, preventing duplicate rendering
    • \n
\n

Map Viewport Hang Fix

\n
    \n
  • Root cause: Dragging/zooming the map triggered an infinite feedback\nloop — moveend → loadRoutes() → layer reassignment + fitBounds\n→ Leaflet re-render → moveend again
    • \n
  • Debounced viewport handler: 300ms debounce on moveend/zoomend\nprevents rapid-fire reloads during panning
    • \n
  • Re-entrancy guard: loadRoutesInProgress flag skips concurrent\nloadRoutes() calls
    • \n
  • Suppress programmatic events: suppressViewportHandler flag\nprevents layer/bounds assignment from re-triggering the viewport\nhandler (cleared after 200ms)
    • \n
  • Skip fitBounds on viewport reloads: loadRoutes(skipFitBounds)\nparameter prevents calculateFitBounds on user-initiated pan/zoom,\nwhich was the primary loop trigger
    • \n
  • Removed cache eviction on viewport change: the viewport filtering\nalready uses currentBounds.intersects() on cached data, so deleting\nand re-fetching GPX on every drag was unnecessary
    • \n
\n

Mail API Resilience (No API Key / Invalid Key)

\n
    \n
  • Short-circuit when no API key: MailMessagingService.initialise()\nchecks mailConfig.apiKey after loading config — if absent, skips all\nBrevo API calls (account, lists, folders, templates) and sets safe\nempty defaults. Zero 401 errors in the console
    • \n
  • Short-circuit on account error: if the account query fails (invalid\nkey), remaining Brevo calls are skipped with empty defaults
    • \n
  • Senders list guard: MailSendersListComponent waits for the\nmailMessagingConfig via the events() observable before calling\nsenders/domain APIs — skips if accountError is set
    • \n
  • Create-or-amend sender guard: checks brevoAccountConfigured()\nbefore calling querySenders()
    • \n
  • Mail provider stats guard: calculateMailProviderStats() handles\nthis.list being undefined when Brevo lists fail to load, showing\n"No Brevo lists available" instead of crashing
    • \n
  • List key values null safety: added ?. and || [] fallback when\nbrevo.lists.lists is undefined
    • \n
  • Alert icon: changed error alert icon from faCircleCheck to\nfaExclamationTriangle for the account error panel
    • \n
\n

CommonDataService Double HTTP Request Fix

\n
    \n
  • Root cause: responseFrom() used .subscribe() + .toPromise()\non a shared observable, causing two subscriptions and duplicate HTTP\nrequests
    • \n
  • Fix: replaced with single firstValueFrom() call — one\nsubscription, one HTTP request, proper error propagation via throw
    • \n
\n

Config Save: Allow Clearing Sensitive Fields

\n
    \n
  • Root cause: restoreSensitiveFields() in the backend config\ncontroller treated both missing keys AND falsy values ("", null)\nas "restore from DB", making it impossible to clear the API key
    • \n
  • Fix: changed condition from !(k in incoming) || !incoming[k] to\n!(k in incoming) — only restores when the key is truly absent\n(redacted), not when explicitly cleared
    • \n
\n

Mail Settings: Prevent Config Overwrite During Editing

\n
    \n
  • Root cause: MailMessagingService.initialise() created new\nsubscriptions to committeeConfig and systemConfigService on every\ncall, causing accumulated subscriptions that re-emitted config and\noverwrote unsaved edits
    • \n
  • Fix: moved one-time subscriptions to the constructor;\nacceptNextConfigEmission flag in MailSettingsComponent prevents\nsubscription emissions from overwriting local edits except after\nsave or undo
    • \n
\n

Domain API URL Refactor

\n
    \n
  • Changed domain endpoints from path parameters\n(/domains/:domainName/configuration) to query parameters\n(/domains/configuration?domainName=...) across backend routes and\nfrontend service
    • \n
\n

Walk Search Layout

\n
    \n
  • Alert inline when default filtering, own row with pagination/filters
    • \n
  • Clear filters resets to default preset
    • \n
  • Bug button hidden by default
    • \n
\n

Events

\n
    \n
  • Bug button visibility fix
    • \n
\n

Server API for #175

\n
    \n
  • POST /api/database/booking — create booking
    • \n
  • PUT /api/database/booking/:id — update booking
    • \n
  • DELETE /api/database/booking/:id — delete booking
    • \n
  • GET /api/database/booking/all — list bookings (with query criteria)
    • \n
  • GET /api/database/booking/capacity/:eventId — public capacity check
    • \n
  • POST /api/database/booking/lookup — find bookings by event + email
    • \n
  • PUT /api/database/booking/cancel/:id — cancel with email verification
    • \n
\n

Contact Us Persistence

\n

Contact form submissions are now persisted to the database via\nContactInteractionService and a new /api/database/contact-interaction\nendpoint. Each interaction records: name, email, subject, message, whether\nthe sender was anonymous, the recipient role, and a status\n(new/read/archived).

\n

Social → Group Events Rename

\n

All social event components, services, models, and routes have been renamed\nfrom social-* to group-event-* to align with the Ramblers API naming\nconvention. Key renames:

\n
    \n
  • SocialEditComponent → GroupEventEdit
    • \n
  • SocialDisplayService → GroupEventDisplayService
    • \n
  • SocialViewPage → GroupEventViewPage
    • \n
  • SocialCard → GroupEventCard
    • \n
  • social-events.model.ts → group-events.model.ts
    • \n
  • social-auth-guard.ts → group-event-auth-guard.ts
    • \n
\n

Removed Orphaned Code

\n

Deleted components and services no longer referenced anywhere:

\n
    \n
  • WalkList (723 lines) — replaced by EventsFull CMS component
    • \n
  • GroupEventList + sass
    • \n
  • GroupEventViewSelector
    • \n
  • SocialViewSelector
    • \n
  • SocialList + sass
    • \n
  • SocialRoutingModule
    • \n
  • SocialPopulationLocalGuard
    • \n
  • Hardcoded PAGE_HEADER and ACTION_BUTTONS anchors — walks and social\npages are now 100% content-managed
    • \n
\n

Event Navigation Fixes

\n

Deep path dispatch (fixes wrong event for generic slugs)

\n

For paths with 3+ segments (e.g. /walks/weekends-away/swanage/day-2),\npage content is now checked before event lookup. This prevents generic\nslugs like day-2 from regex-matching unrelated events. Two-segment paths\n(e.g. /walks/some-event-slug) still try event lookup first.

\n

Walk card title links (fixes pre-existing non-navigation)

\n
    \n
  • walkRouterLink() now generates relative URLs so routerLinkUrl() returns\na valid path instead of null (absolute URLs were rejected as "remote")
    • \n
  • Added stopPropagation on the title <a> to prevent the parent card's\ntoggleView() handler from intercepting the routerLink click
    • \n
\n

Edit/cancel navigation symmetry

\n
    \n
  • close() strips /edit from the current path instead of reconstructing\nthe URL via groupEventLink(), which was reading the still-dirty URL
    • \n
  • Added explicit edit and new routes to walks-routing.module.ts before\nthe ** catch-all to prevent /edit/edit/edit URL corruption
    • \n
\n

Cleanup

\n
    \n
  • walksArea() simplified to urlService.area() — removed stale fallbacks\nto pageService.walksPage()?.href and hardcoded "walks"
    • \n
\n"}