Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.There is an issue with the mailchimp_signup_set_target function that was created as part of #2354325 where the feeds import value is wrapped in an extra array and then not processed properly by the mailchimp integration. The attached patch addresses that function.
However, we should also consider moving the hook_feeds_node_processor_targets_alter and mailchimp_signup_set_target functions into the mailchimp_lists submodule, since that is where the fields are actually being defined, rather than its current location in the mailchimp_signup submodule.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | mailchimp-allow_raw_value_feeds_imports-2676820-4.patch | 2.63 KB | gcb |
| |||
| #2 | mailchimp-allow_raw_value_feeds_imports-2676820-1.patch | 678 bytes | mikemccaffrey |
| |||
Comments
Comment #2
mikemccaffreyComment #3
gcbComment #4
gcbThis helped, but there is a related issue where nonsense values in the feeds importer get treated as booleans: blank values, random text, etc. The attached patch refactors mailchimp_signup_set_targets to recognize that multi-value mailchimp fields are not allowed, and to coherently handle non-standard values, including some that people might like to use in feeds importers like "yes" and "true".
Comment #5
ruscoe CreditAttribution: ruscoe at ThinkShout for Mailchimp commentedWe're going to be ending support for the 7.x-3.x branch due to the upcoming deprecation of the v2.0 MailChimp API.
This patch should be rerolled for the 7.x-4.x branch.
Comment #6
ruscoe CreditAttribution: ruscoe at ThinkShout for Mailchimp commentedComment #7
alex.xequals CreditAttribution: alex.xequals commentedI'm having the same issue on 7.51. Importing subscriptions via feeds, using a tamper on the subscription field to convert to boolean, and no matter what I do the actually check box is not being ticked. Everything else is running fine without error however it seems the target is not receiving the data well. Will this patch also work for 7.51? Is there a specific tamper that others have used which will populate the subscription field the way that the module wants?
Comment #8
gcbYou will need this patch. Try applying it: if it does not apply we'll need to re-roll it. I'm not sure a special tamper will help you. This property is an odd one: it stores in mailchimp, not the database.