Hello,

I'm currently using this module in production sites and I'll be happy to move forward a drupal 11 compatible version with a good performance and bug free.

I've tried to contribute in a couple of key issues but they seem to be unattended:

https://www.drupal.org/project/cloudinary/issues/3571476
https://www.drupal.org/project/cloudinary/issues/3428387

Comments

alvar0hurtad0 created an issue. See original summary.

lquessenberry’s picture

I second this. I was part of the revitalization of the Drupal 8/9 version. My current client is considering Cloudinary for a DAM/CDN and I will need Drupal 11 compatibility.

lquessenberry’s picture

I've completed the Drupal 11 compatibility work and created a merge request with all necessary patches.
Work Completed

Merge Request: !38 https://git.drupalcode.org/project/cloudinary/-/merge_requests/38/diffs

Changes:

Updated core_version_requirement to ^9.3 || ^10 || ^11 in all 8 .info.yml files
Fixed PropertyNormalizer final class extension in AssetNormalizer (#3571476)
Changed from inheritance to composition pattern using ObjectNormalizer
Added getSupportedTypes() method for Symfony 6.2+ compatibility
Updated method signatures for PHP 8.3+ type hints

Testing: ✅ Tested on Drupal 11.2.8 with PHP 8.3.23 ✅ All modules install without errors ✅ cloudinary_media_library_widget enables successfully (critical test) ✅ No PHP fatal errors ✅ No watchdog errors ✅ GitLab CI tests running

Files Modified (9 total):

All .info.yml files (8 files)
AssetNormalizer.php (1 file)

Related Issues:

#3428387 - Drupal 11 compatibility
#3571476 - PropertyNormalizer fix

The module is now fully compatible with Drupal 11 and ready for a 3.0.0 stable release.

avpaderno’s picture

Title: Offering to maintain cloudinary » Offering to maintain Cloudinary Integration
Version: 3.0.0-rc5 » 3.0.x-dev
avpaderno’s picture

As a reminder: These offers can be moved in the Drupal.org project ownership queue, after they have been kept in the project queue for at least 14 days, and none of the maintainers commented to decline the offer, if the person who made the offer is still interested.

Only the person who made the offer can move the issue.

lquessenberry’s picture

Hello. I am picking this one back up for support for the next few days.

avpaderno’s picture

Project: Cloudinary Integration » Drupal.org project ownership
Version: 3.0.x-dev »
Component: Miscellaneous » Maintaining offer
Category: Support request » Task
avpaderno’s picture

Project: Drupal.org project ownership » Cloudinary Integration
Version: » 3.0.x-dev
Component: Maintaining offer » Miscellaneous
Category: Task » Support request
alvar0hurtad0’s picture

Project: Cloudinary Integration » Drupal.org project ownership
Version: 3.0.x-dev »

I see no movement, and I keep my offer. Now we need to prepare the code for drupal 12.

avpaderno’s picture

Category: Support request » Task

I will try to handle this offer this evening.

avpaderno’s picture

avpaderno’s picture

Assigned: Unassigned » avpaderno

Only everright and wouters_f can add co-maintainers or maintainers, but only one of them logged in at least once in the past 12 months. I will contact that person.

avpaderno’s picture

Component: Miscellaneous » Maintaining offer
Status: Active » Postponed

This is the message I sent.

Hello wouters_f,

I am contacting you because Alvaro (https://www.drupal.org/u/alvar0hurtad0) offered to become maintainer for Cloudinary Integration (https://www.drupal.org/project/cloudinary), a project for which you are maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3576523 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Alvaro will be probably made maintainer.

I am contacting all the project maintainers, and the project co-maintainers with the "Administer maintainers" permission, who logged in at least once in the past 12 months. In this case, that is just you.

Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

As last note: This offer is about being maintainer, which is different from being co-maintainer. A maintainer is a person who has all the drupal.org permissions on a project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
If there is any reason for not giving all those permissions, please explain that on the offer issue. We need this to know it was intentional and not a misunderstanding on what the offer required.

Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator

The status is Postponed because we are waiting for a reply.

Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder that a project moderator's action is required.

lquessenberry’s picture

I am also happy to support this. I wish I could add members, but I can't.

wouters_f’s picture

It's good!
Added alvar0hurtad0 as maintainer

wouters_f’s picture

gave lquessenberry also maintainer rights so they can also manage maintainers and also nginex.

lquessenberry’s picture

Thanks wouters_f I hope you are well old friend.

avpaderno’s picture

Truly, alvar0hurtad0 has been added as co-maintainer. To be maintainer, he should have all the permissions on the project.

alvar0hurtad0’s picture

Now I've permissions to create releases and push to repo.

We are a lot of maintainers, how are we supposed to coordinate?

avpaderno’s picture

Status: Postponed » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.