The public contact page currently shows an unrendered contact-form shortcode and two different email destinations. I observed this in Chromium on September 11, 2026 and followed the page's website-problem link to this tracker.
Reproduce
- Open https://datacommons.coop/contact/.
- Under “Contact the Data Commons”, the main email link displays and targets
info@staging.datacommons.coop.
- Below the postal address and social link, the page displays
[contact-form-7 id=”13″ title=”Contact form 1″] as text; there are no corresponding form fields.
- The footer instead displays and targets
info@datacommons.coop.
Expected
A working contact method, with the intended email address used consistently and no raw form shortcode shown to visitors.
Suggested fix
Confirm the intended public mailbox, then update the contact-page content to match. Restore the form's rendering in the deployed site, or remove the inactive shortcode and keep a clear email link.
The current master version of contact/index.html already uses the non-staging address and has no shortcode, so the deployed content appears to differ from that file. I haven't established the deployment source. No test email or form submission was sent.
The public contact page currently shows an unrendered contact-form shortcode and two different email destinations. I observed this in Chromium on September 11, 2026 and followed the page's website-problem link to this tracker.
Reproduce
info@staging.datacommons.coop.[contact-form-7 id=”13″ title=”Contact form 1″]as text; there are no corresponding form fields.info@datacommons.coop.Expected
A working contact method, with the intended email address used consistently and no raw form shortcode shown to visitors.
Suggested fix
Confirm the intended public mailbox, then update the contact-page content to match. Restore the form's rendering in the deployed site, or remove the inactive shortcode and keep a clear email link.
The current
masterversion ofcontact/index.htmlalready uses the non-staging address and has no shortcode, so the deployed content appears to differ from that file. I haven't established the deployment source. No test email or form submission was sent.