{"id":"69a01e15067457ea4e35300b","title":"2026 02 21","path":"how-to/committee/release-notes/2026-02-21","contentMarkdown":"# 21-Feb-2026 — restore recaptcha siteKey visibility for logged-out users [closes #163](https://github.com/nbarrett/ngx-ramblers/issues/163)\n\n## [build 501](https://github.com/nbarrett/ngx-ramblers/actions/runs/22437204477) — [commit 04f52c8](https://github.com/nbarrett/ngx-ramblers/commit/04f52c8e4b38a97df83c36e4da7e7e1a4f58843b)\n\n_____\n\n### restore recaptcha siteKey visibility for logged-out users ([#163](https://github.com/nbarrett/ngx-ramblers/issues/163))\n\nThe reCAPTCHA siteKey was incorrectly listed as a sensitive field,\ncausing it to be redacted from system config responses for non-admin\nusers. Logged-out visitors received no siteKey, so the contact form\nshowed \"Recaptcha site key not configured\" and the Send button was\npermanently disabled.\nThe siteKey is a public key by design — it must be accessible to all\nusers to render the captcha widget. Only the secretKey requires\nprotection, which it retains.\nAlso remove the unused &edit= parameter from the committee contact\nmarkdown link generator; the contact-us route never consumes it.","contentHtml":"<h1>21-Feb-2026 — restore recaptcha siteKey visibility for logged-out users <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/163\">closes #163</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/22437204477\">build 501</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/04f52c8e4b38a97df83c36e4da7e7e1a4f58843b\">commit 04f52c8</a></h2>\n<hr>\n<h3>restore recaptcha siteKey visibility for logged-out users (<a href=\"https://github.com/nbarrett/ngx-ramblers/issues/163\">#163</a>)</h3>\n<p>The reCAPTCHA siteKey was incorrectly listed as a sensitive field,\ncausing it to be redacted from system config responses for non-admin\nusers. Logged-out visitors received no siteKey, so the contact form\nshowed &quot;Recaptcha site key not configured&quot; and the Send button was\npermanently disabled.\nThe siteKey is a public key by design — it must be accessible to all\nusers to render the captcha widget. Only the secretKey requires\nprotection, which it retains.\nAlso remove the unused &amp;edit= parameter from the committee contact\nmarkdown link generator; the contact-us route never consumes it.</p>\n"}