🇺🇸United States @aprice42

xenophyle → credited aprice42 → .

Rerolled for with the 10.x compatible release (8.x-1.1)

Forgot to update this, but the appspot url is no longer being used as of 2.2.2 https://www.drupal.org/project/mailchimp/releases/2.2.2 →

It is difficult to determine how the mailchimp module is causing this problem for you. Can you please provide the steps so that someone can reproduce this issue?

I can appreciate this feeling like a critical issue, however being a support request I am going to downgrade the priority to Normal.

This looks like an issue with drupal packagist, I am not sure why release 2.2.1 was given a null reference. I opened an issue with that team so hopefully they can resolve or provide some direction about how to fix!

In the meantime as @laborouge pointed out you can manually change your composer.json file to require version 2.2.2 - something like this worked for me:

    "require": {
        "drupal/mailchimp": "^2.2.2"
    },

Followed by:

composer update drupal/mailchimp

aprice42 → created an issue.

Thanks for raising this issue, we are looking into it now!

greggles → credited aprice42 → .

Sounds like your Mailchimp API PHP library is not properly installed. See this issue for a fix: https://www.drupal.org/project/mailchimp/issues/3349727 🐛 Composer install of 2.2.0 fails on Drupal 10.0.5 w/o prior MailChimp Fixed . Also see the readme for more info on how to install this module properly.

aprice42 → created an issue.

Going to close this issue out since the latest thread is now on #3350229, but please feel free to reopen if you feel there is something else unresolved here.

I believe the latest release should resolve your issue. I was able to install without issue on a fresh d10 site install. If you still have a problem, can you provide steps to reproduce?

@Rob230 I wonder if this patch might resolve the issue? Just adding a check over that entire block of code to see if the new_interest_groups exists and is an array.

@TomBe I understand this feels like a major issue, however this might be entirely to do with the way you have your system set up, so I am downgrading the priority to Normal until we know more.

Can you please provide some additional details about:
- How you have mailchimp configured, (details like which submodules are you using and what how do you have them configured).
- What your Drupal Feeds is doing (saving user objects, setting specific values, etc..)?

Then we can try to provide some support into how to fix this issue.

Thanks!

Thanks for your work on this! If you two would like to combine your efforts I can review and see about getting this merged in.

Thanks for raising this issue. The middleware application hosted at 'https://drupal-mailchimp-oauth.uw.r.appspot.com is a Mailchimp owned middleware application. We are working with the Mailchimp team to get this url updated to a mailchimp.com subdomain ASAP.

Will update here as soon as that happens.

Just rolled a new release that includes a fix for this.

@RoSk0 please see the comment on the other thread where you posted this question. In the future please only post questions one time. Thanks!

https://www.drupal.org/project/mailchimp/issues/3345228 📌 Update docs to reflect new OAuth config method Fixed

Hi @RoSk0,

To be clear, this documentation is only referring to API key usage with this Drupal module. We deprecated API key usage now because, in the v3 release of this module, the API key connection will no longer be supported.

We are still working with the Mailchimp team on an update to their Mailchimp for Drupal documentation. That new documentation will note the deprecation of API keys with regard to the Mailchimp Drupal module. We will be sure to update the module description with a link to that documentation as soon as it is available.

This issue was fixed with release v3.0.0-rc4 of the Mailchimp API PHP library.

aprice42 → created an issue.

Thanks for verifying Berdir. And thanks for the feedback on the BC issue. I have a PR ready for review to fix that issue https://github.com/thinkshout/mailchimp-api-php/pull/113. Changing this issue status back to fixed and will file a separate issue for that.

I am not seeing the reported issue. Perhaps the resource was unavailable when you tried it yesterday? Here are the steps that worked for me just now:

rm -rf vendor
rm composer.lock
composer require thinkshout/mailchimp-api-php:^3.0

aprice42 → created an issue.

Thanks for reporting! Marking this as a duplicate of https://www.drupal.org/project/mailchimp/issues/3261477 🐛 In php 8.1 the explode function throws a notice when default value is null Fixed . A patch has been applied to resolve this issue and a number of other uses of explode in the module.

Thanks for reporting! There were some additional uses of explode that needed to be updated as well so we added them all under this issue.

Merged into 2.x and will be part of the next release coming later this week!

aprice42 → made their first commit to this issue’s fork.

This work was merged into 2.x and will be made part of Release 2.2.0-rc1.

aprice42 → created an issue.