fix: temporarily disable duplicate newsletter form on homepage
Description
Fixes #913
Problem
Embedding the same EmailOctopus form snippet twice on the homepage causes a JavaScript data-form ID conflict, preventing the second instance from rendering/submitting properly. Resolving this natively requires duplicating the form in the EmailOctopus dashboard.
What i did
- Temporarily disabled the second newsletter subscription form on the homepage so users don't encounter a broken UI.
- the primary homepage form active after the news and announcement section.
- Made some few texts update.
Important Note: Subscription forms on all other pages remain unaffected and are working as expected, since they only load a single instance of the form per page.
Next Steps
Pending confirmation from the team lead on our EmailOctopus plan, we will re-enable the second homepage placement by creating a duplicate embeddable form with a unique ID in the EmailOctopus dashboard.
Confirmation
This PR can go ahead as is because creating a duplicate will not be possible due to the current emailoctopus plan.
@LukasWallrich
Type of Change
- Content/documentation update
- Bug fix
Testing
- Tested locally
- Previewed on staging.forrt.org
Checklist
- Self-reviewed my changes
- Verified links and formatting are correct
- No new warnings or errors
Notes
Summary by cubic
Temporarily removes the duplicate newsletter form on the homepage so the remaining form stops breaking from a JavaScript data-form ID conflict when the same EmailOctopus snippet is embedded twice.
- Deletes the secondary "Stay Updated" newsletter section; only the primary "Subscribe to our newsletter" band remains.
- Updates the primary form's label to mention events and opportunities.
Re-enable the second placement once a duplicate form with a unique ID is created in the EmailOctopus dashboard. Forms on other pages load a single instance and remain unaffected.