{"id":"69f26baabd28ba8b2142b8f5","title":"2026 04 29 Issue 234","path":"how-to/committee/release-notes/2026-04-29-issue-234","contentMarkdown":"# 29-Apr-2026 — Committee page title override and original filename downloads [#234](https://github.com/nbarrett/ngx-ramblers/issues/234)\n\n## [build 629](https://github.com/nbarrett/ngx-ramblers/actions/runs/25131677331) — [commit 143d908](https://github.com/nbarrett/ngx-ramblers/commit/143d908ca4d4e3b40686072ff029e50ca14eb503)\n\n_____\n\nTwo changes requested by Stag Walkers for the\ncommittee documents feature, plus a few small improvements made while testing.\n\n### Custom page heading on committee documents pages\n\nEditors can now set a \"Page Title Override\" on any committee\ndocuments row. When set, the page heading uses that text directly;\nwhen blank, the existing \"Committee events for {url-derived-name}\"\ndefault is preserved. Useful for replacing auto-generated headings\nlike \"Committee events for Agm Meetings\" with something more\nappropriate to the audience.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/ff95bf3c-3218-4022-b3af-b211eb9c5dec.png)\n\n*The new **Page Title Override** input at the top of the committee documents row editor. Leave it blank to keep the existing URL-derived heading; type any text to replace it on the public page.*\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/514002a9-b375-41c7-9e4b-55b6fb85b9e4.png)\n\n*The same row rendered on the live page. The override text \"Some override\" replaces the auto-generated \"Committee events for 2025\" heading. The file links beneath now use the original uploaded filenames (\"AGM Agenda\", \"AGM Minutes\").*\n\n### Downloads use the original uploaded filename\n\nCommittee file downloads now suggest the original uploaded name in\nthe browser's save dialog instead of the hashed S3 object key.\nExisting files work without re-upload because the original filename\nwas already captured at upload time.\n\n### File editor tweaks\n\n- The link preview in the file editor no longer shows\n\"{date} - (none)\" when a file has no display title; it shows just\nthe date.\n- When a display title is set, it is joined to the date with an em\ndash with spaces (matching the convention used elsewhere in the\napp for event time ranges).\n- The \"File or Event Date\" and \"File Type\" fields in the file\neditor are now aligned on the same horizontal line.\n\n## Other changes in this release\n\n### **env-setup**: clone-mode wizard fixes, memory dropdown, streamed deploy\n\nCluster of fixes to the environment-setup wizard surfaced while\ncreating a new environment via \"Create from Existing\":\n\n### Ramblers API key entry in clone mode\n\n- The clone branch of step 1 had no API key UI, so when the source\nenvironment's secrets did not include RAMBLERS_API_KEY (older\nenvs predate it being persisted), step 4 validation failed with\n\"Ramblers API Key: API key is required\" with no way to recover.\n- Add a Ramblers API Key secret-input plus Validate API Key button\nto the clone branch, scoped to a selected source environment.\nEditing the key resets apiKeyValid so the user can re-validate.\n- Fall back to the current admin's\nsystemConfig.national.walksManager.apiKey when the cloned source's\napiKey is empty, so the request is seeded with something usable\nrather than the empty string that createEmptySetupRequest left\nbehind after the clone reset.\n- Drive the post-clone apiKeyValid flag from the resulting request\nvalue rather than the raw details payload, so the systemConfig\nfallback is reflected in the indicator.\n\n### Auto-load group/area info on clone\n\n- environment-details/:environmentName: when any of\nRAMBLERS_GROUP_CODE / RAMBLERS_GROUP_NAME / RAMBLERS_AREA_CODE /\nRAMBLERS_AREA_NAME are missing from the source's secrets, connect\nto its MongoDB and fall back to systemConfig.group.{groupCode,\nlongName} and systemConfig.area.{shortName, longName}. Existing\nsecret-derived values still take precedence.\n- validateSetupRequest: add a Ramblers Group entry that fails when\ngroupCode is empty so the wizard stops at validation rather than\nexploding with \"Failed to fetch group details for\" during deploy.\n\n### Memory configuration UX\n\n- Replace the free-text \"Memory (MB)\" input with a select bound to a\nnew FlyioMemory enum (MB_256/MB_512/MB_1024/MB_2048/MB_4096/\nMB_8192), iterated via the existing enumKeyValues helper to match\nother dropdowns in the app. FLYIO_DEFAULTS.MEMORY now points at\nFlyioMemory.MB_512.\n- Drop the trailing \"MB\" in the review summary so the display reads\n\"512mb\" instead of \"512mbMB\".\n\n### Streamed flyctl deploy output\n\n- The streaming infrastructure already existed (runCommandStreaming +\nDeployOutputCallback, used by the resume-environment WS path), but\nthe create-environment path was wiring only a progress callback,\nso the wizard saw \"[running] deploy-app: Deploying to Fly.io\"\nfollowed by silence until \"[completed] deploy-app\". The actual\nflyctl output (Verifying app config, Building image, Provisioning\nips, Launching new machine, etc.) only went to the server stdout.\n- createEnvironment: accept an optional onDeployOutput callback and\nforward it to deployToFlyioCommand using the options-object form\nalongside the existing onProgress handler.\n- handleEnvironmentCreate (WebSocket handler): pass an onDeployOutput\nthat emits each streamed line as a PROGRESS message prefixed with\n\"[deploy] \", matching the prefix the resume-environment handler\nalready uses. The HTTP /create route is unchanged because it\nreturns a single response and cannot stream.","contentHtml":"

29-Apr-2026 — Committee page title override and original filename downloads #234

\n

build 629 — commit 143d908

\n
\n

Two changes requested by Stag Walkers for the\ncommittee documents feature, plus a few small improvements made while testing.

\n

Custom page heading on committee documents pages

\n

Editors can now set a "Page Title Override" on any committee\ndocuments row. When set, the page heading uses that text directly;\nwhen blank, the existing "Committee events for {url-derived-name}"\ndefault is preserved. Useful for replacing auto-generated headings\nlike "Committee events for Agm Meetings" with something more\nappropriate to the audience.

\n

\"\"

\n

The new Page Title Override input at the top of the committee documents row editor. Leave it blank to keep the existing URL-derived heading; type any text to replace it on the public page.

\n

\"\"

\n

The same row rendered on the live page. The override text "Some override" replaces the auto-generated "Committee events for 2025" heading. The file links beneath now use the original uploaded filenames ("AGM Agenda", "AGM Minutes").

\n

Downloads use the original uploaded filename

\n

Committee file downloads now suggest the original uploaded name in\nthe browser's save dialog instead of the hashed S3 object key.\nExisting files work without re-upload because the original filename\nwas already captured at upload time.

\n

File editor tweaks

\n\n

Other changes in this release

\n

env-setup: clone-mode wizard fixes, memory dropdown, streamed deploy

\n

Cluster of fixes to the environment-setup wizard surfaced while\ncreating a new environment via "Create from Existing":

\n

Ramblers API key entry in clone mode

\n\n

Auto-load group/area info on clone

\n\n

Memory configuration UX

\n\n

Streamed flyctl deploy output

\n\n"}