You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While investigating a build error in the app, open-sauced/app#3796, @netlify/plugin-nextjs@5 requires migration steps to support Netlify Forms. Refer to https://ntl.fyi/next-runtime-forms-migration for migration example., I discovered that our newsletter signup no longer collects emails in the app. I tried it out in the landing-page, and it's the same behviour, it no longer works.
The last one collected appears to have been in March, but a couple tests I did does not collect the emails.
We're using the pages router, but it appears we may need to do the same fix as suggested in the Netlify docs to be able to use Netlify Forms with Next.js. Not sure when this broke.
We haven't seen build failures in the landing-page project yet, but when we do, you'll need to add this environment variable to the project temporarily until this issue is fixed, and then remove the env var, once this issue is resolved.
The text was updated successfully, but these errors were encountered:
While investigating a build error in the app, open-sauced/app#3796,
@netlify/plugin-nextjs@5 requires migration steps to support Netlify Forms. Refer to https://ntl.fyi/next-runtime-forms-migration for migration example.
, I discovered that our newsletter signup no longer collects emails in the app. I tried it out in the landing-page, and it's the same behviour, it no longer works.The last one collected appears to have been in March, but a couple tests I did does not collect the emails.
We're using the pages router, but it appears we may need to do the same fix as suggested in the Netlify docs to be able to use Netlify Forms with Next.js. Not sure when this broke.
The fix is detailed at https://docs.netlify.com/frameworks/next-js/overview/#breaking-changes.
We haven't seen build failures in the landing-page project yet, but when we do, you'll need to add this environment variable to the project temporarily until this issue is fixed, and then remove the env var, once this issue is resolved.
The text was updated successfully, but these errors were encountered: