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.
I have just updated to version 7.x-4.x and it broke my site because the module used PHP syntax that my PHP site doesn't understand yet. When I quickly fixed that manually, the library did the same thing and that's obviously much more complex to adjust.
So, this module should document on the project main page and declare in the info and composer.json the required PHP version, otherwise a disaster is pretty likely to happen.
Whil on it, the composer.json also declares a name ("drupal/contrib/mailchimp") which is not valid. Such a name can not contain 2 slashes, it has to be one.
Comments
Comment #2
idebr CreditAttribution: idebr at One Shoe commentedHi Jürgen,
The Mailchimp module uses the Guzzle library, which has a minimum PHP version of 5.5 or greater. The module maintainer commented on this before: https://www.drupal.org/node/2502657#comment-11727663
I am not sure on the correct naming of the composer file, but perhaps someone else can help out.
Comment #3
ruscoe CreditAttribution: ruscoe at ThinkShout commented@idebr is correct in the minimum required PHP version being 5.5. In the next module release (7.x-4.7) the required PHP version will be lowered to 5.4.
You're absolutely right about the module name being invalid in composer.json. I've committed a fix.
Comment #4
aitala CreditAttribution: aitala commentedWhere are we on the version which supports PHP 5.4??
Thanks,
Eric
Comment #5
ruscoe CreditAttribution: ruscoe at ThinkShout commentedReleased last month:
https://www.drupal.org/project/mailchimp/releases/7.x-4.7
Comment #6
Bès CreditAttribution: Bès at Happyculture commentedThis issue seems a duplicate of https://www.drupal.org/node/2825998
Comment #7
aitala CreditAttribution: aitala commentedOk but you know it does not work since the .info file still requires PHP 5.5
I know that is easy to fix and I did but the module still has issues. I will report those elsewhere.
Eric.
Comment #8
a.ross CreditAttribution: a.ross commentedGreat. So the info on upgrading wasn't merely confusing, it was incomplete. I'm now faced with either an involved process of updating a test environment, or taking the risk and updating the module directly on the live environment.
Comment #9
idebr CreditAttribution: idebr commentedThe documentation for the minimum PHP version was updated in #2846462: This module requires PHP version 5.5.* and is incompatible with PHP version 5.4.40. I'll close this issue as a duplicate.