Found the root cause. The list I use has additional fields set to required (first name, last name, birthday, etc.) These are not collected through the changes made to the widget, and thus fails during put api call. Changes to the widget no longer direct users to my custom sign-up form through the form action url, where the additional data can be collected. Thus users receive this failed to subscribe error because data for those required fields are missing.
While this simplifies sign-up for the newsletter, in the event the only data you want is an email. It forces multiple data collection methods for businesses to send customer to multiple locations for data entry and setup additional backend resources to merge information to update contact info and lists.
Definitely not a fan of the changes here. Allowing the widget flexibility to account for both functions would be an awesome feature. Using an if statement based on form action url field being blank use the new function, else with form field filled use old function.
-
This reply was modified 6 years, 8 months ago by ebblio.
-
This reply was modified 6 years, 8 months ago by ebblio.
-
This reply was modified 6 years, 8 months ago by ebblio.
