Problems with a popup/form that uses mailerlite integration
Have a subscribe form that was working just fine but now on submission it keeps saying "OOPS! PLEASE TRY AGAIN."
Have looked at the integration, API key etc etc and everything looks ok.
Any ideas?
-
Hi Martin,
We would like to take a look at this error. Please let us know the URL where we can see this error.
0 -
Hi Thanks for that.
I looked into it a bit more by inspecting the network traffic. The ajax response from the mailerlite API was basically returning a 500 error.
{"success":false,"data":{"code":500,"message":"Member was not created."}}There's not much I could find in the MailerLite API about why this was the case. It only seemed to be occurring for a particular email address that was already in the MailerList subscriber list but with a status of "Unconfirmed".
Again, I'm not sure why that particular subscriber was in that state. And deleting the subscriber in MailerLite (ML) and retrying the registration via the Brizy form simply re-activate the subscriber in ML but with the same unconfirmed status and the same error in the brizy popup.
The subscriber *may* have been created with an earlier popup (using ML embedded code) that required double opt-in (which didnt' get actioned perhaps?) and left it in the unconfirmed status. And the unconfirmed status is somehow being rejected when the Brizy form makes it's API call. That's my guess anyway.
For now, there doesn't seem like there's very much I can do for that particular emails address - other than use ML's "forget" functionality. Which takes 30 days... After which the subscriber might be able to try again.
Best wishes
0 -
Hi Martin,
If a user has opted in and his email address is already in the MailerLite subscriber database, obviously the same user cannot opt-in again. If you are attempting to confirm the user, please follow the procedure here https://www.mailerlite.com/help/what-are-unconfirmed-subscribers
0 -
Hi George
Yes, that was my initial thinking too. However, when I try subscribing other existing subscribed users using exactly the same form, the form UI displays "THANK YOU! YOU ARE NOW SUBSCRIBED" and the API does in fact return a 200.
{"success":true,"data":200}The main difference seems to be that these subscribers are listed in MailerLite as having a status of "Active", whereas the one causing the problems is "Unconfirmed".
So for me it's more a UX issue caused by the API returning a 500 error in this case so that the user doesn't get meaningful feedback as to why they can't re-subscribe or give them any indication that they are unconfirmed and how they can confirm. Or perhaps the API shouldn't return a 500 in this case and should carry on with the subscription.
I've solved it by deleting the user in MailerLite so that will have to do as a work around.
Thanks for the link re unconfirmed subscribers. I'll take a look at that.
0
Please sign in to leave a comment.
Comments
4 comments