Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 'Using mailchimp' readme section #293

Merged
merged 1 commit into from
Aug 17, 2023

Conversation

jose-bittacora
Copy link
Contributor

While using your package, I followed the instructions, but I was always getting empty responses and I couldn't get any information from getLastError() or getLastResponse(). I ran the code step by step and found that if NEWSLETTER_ENDPOINT is set to an empty string as the documentation states, the Mailchimp endpoint isn't built correctly. The solution is to set that value to null instead.

While using your package, I followed the instructions, but I was always getting empty responses and I couldn't get any information from getLastError() or getLastResponse(). I ran the code step by step and found that if NEWSLETTER_ENDPOINT is set to an empty string as the documentation states, the Mailchimp endpoint isn't built correctly. The solution is to set that value to null instead.
@Arnwaltur
Copy link

Hi,
+1 for this Mailchimp patch

@Applejack21
Copy link

Bump for this to be merged. Fixed for me as using 'endpoint' => env('NEWSLETTER_ENDPOINT', ''), didn't subscribe the user to the mailing list but 'endpoint' => env('NEWSLETTER_ENDPOINT', null), does.

@code23-isaac
Copy link

+1 this fixes mailchimp issues

@DanDvoracek
Copy link

For anyone stumbling on this page, make sure to NOT put a NEWSLETTER_ENDPOINT value in your .env on top of it. If you specify it empty/without a value there you might have silent mistakes too.

@Datalink-Wouter
Copy link

Omg legends! I couldn't find why every endpoint returned a False, appears to be this NEWSLETTER_ENDPOINT thing.

@niekappartmedia
Copy link

@freekmurze is this something you can somehow merge because its something i stumbeld over with the simple fix of setting the value to null.

@freekmurze freekmurze merged commit 6f242da into spatie:main Aug 17, 2023
@freekmurze
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants