It seems the 2.2.3 update causes an error: "Uncaught PHP Exception ParseError: "syntax error, unexpected token "else"" at /modules/contrib/mailchimp/modules/mailchimp_lists/src/Plugin/Field/FieldType/MailchimpListsSubscription.php line 374
The update caused the patch to add the "else {}" statement to the wrong function in MailchimpListsSubscription.php.
I've moved it and updated the patch.
The exact situation we're going through. About 13K users and the field is null. New signups are being recorded as they should, but the older accounts are not synced properly with their MC accounts. If we edit/save, then they resync, and the information is updated.
I am receiving an error that states the API Key is missing even though we authenticated using OAUTH.
An error occurred pulling member info for a list. "cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://us6.api.mailchimp.com/3.0/lists/{audience}/members?offset=0&count=500&status=subscribed"
"{"type":"https://mailchimp.com/developer/marketing/docs/errors/","title":"API Key Invalid","status":401,"detail":"Your request did not include an API key.","instance":"xxxxxx-xxxx-xxxx-xxxxxxxxx"}"
Speaking with MailChimp Support, they state, "I can confirm that even with OAUTH, an API key is necessary when it comes to connection Drupal."
Are there more steps needed to integrate Mailchimp besides Authentication, and if so, where would you place the API info, settings.php?
To summarize,
Rolling Interval
- Rolling Interval starts when the license is activated and expires at the end of the interval period.
Interval based on reference date
- Interval based on reference date begins when the license is activated and expires at the reference date unless activated after the reference date; then, it expires at the end of the interval period.
- The reference date, which only needs to be set once, starts the interval period.
- When the current interval period ends, it will start a new period directly after.
- A license granted within the original or any subsequent interval periods will expire at the end of the current period it is in.
No, this was GREAT! Thank you for clearing some of this up.
You're correct; the Unlimited is straightforward.
The Rolling Interval is defined and less confusing now, thank you.
The Interval based on the reference date is still a little confusing. The example you gave works if you need to set a date for some sort of interaction, like the 1st of the month. However, I wouldn't have imagined using it in such a way. Wouldn't a fixed reference date be used for an event?
For example, a site has an annual membership begins on 7/1 each year. The company wants to allow people to purchase the license up to 3 months before or anytime after the 7/1 start date and have it expire on 6/30 the following year. I would have thought that regardless of when it was published, the granted licenses wouldn't expire until one year after the reference date.
So the best method would be to set the reference date to the date it is published and the Interval to 15 months (3 months early + 12 months membership) for the above scenario?
The role option is very useful for audience segmentation at MailChimp.
Thank you for this patch. It does add the role option to the available merge list and imports role(s) for new Drupal accounts to MailChimp.
If an existing user's account has a role added or removed, the MailChimp field does not update with the new information. Even after updating the Mailchimp Mergevar Values, nothing is changed on MailChimp.
Were you able to find a workaround for updating existing user roles?
May be a duplicate of https://www.drupal.org/project/commerce_paypal/issues/3343285 🐛 jQuery error on checkout Fixed
Are there any plans to add d7 migration ability, or is it already available and we just missed it?
On the Pattern's Page (/admin/config/search/path/patterns).
After a migration, the alias wouldn't work for my custom content types. I tried all the options with Bulk Generate, but the path only included the title "[node:title]." In my case, the issue was that the default content pattern was used before Pathauto could detect my other custom patterns B & C.
Content - Custom A - aliasA/[node:title]
Content - Custom B - aliasB/[node:title]
Content - Custom C - aliasC/[node:title]
Content - Default - [node:title]
Also, remember to place the custom patterns at the top of the list. I ran into this problem and the default [node:title] was being used before it could reach my custom patterns.
Thanks, Kristi, for creating this post and Dalemoore for the answer. Switching to nd_pdo_mysql worked for me.