I am wondering what the best way to sync (one way is good). The only thing that would be nice to do is in case someone unsubscribed via a mailchimp link, we probably don't want them to be re-subscribed.
Also, in the README, I found the following two methods are similarly described.
There's also a convenience method to check if someone is already subscribed:
Newsletter::hasMember('nanny.ogg@discworld.com'); //returns a boolean
In addition to this you can also check if a user is subscribed to your list:
Newsletter::isSubscribed('lord.vetinari@discworld.com'); //returns a boolean
Is it the case that hasMember() checks if the email exists anywhere in mailchimp. And "isSubscribed" checks if that email address is actually subscribed to a list? (by the way why is list not provided via arguments? does it just assume the default list provided in the config?)
because this issue seems to be inactive for quite some time now, I've automatically closed it. If you feel this issue deserves some attention from my human colleagues feel free to reopen it.
I am wondering what the best way to sync (one way is good). The only thing that would be nice to do is in case someone unsubscribed via a mailchimp link, we probably don't want them to be re-subscribed.
Also, in the README, I found the following two methods are similarly described.
Is it the case that hasMember() checks if the email exists anywhere in mailchimp. And "isSubscribed" checks if that email address is actually subscribed to a list? (by the way why is list not provided via arguments? does it just assume the default list provided in the config?)