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
Comment #2
lquessenberry commentedI 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.
Comment #3
lquessenberry commentedI'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.
Comment #4
avpadernoComment #5
avpadernoAs 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.
Comment #6
lquessenberry commentedHello. I am picking this one back up for support for the next few days.
Comment #7
avpadernoComment #8
avpadernoComment #9
alvar0hurtad0I see no movement, and I keep my offer. Now we need to prepare the code for drupal 12.
Comment #10
avpadernoI will try to handle this offer this evening.
Comment #11
avpadernoThe project link is https://www.drupal.org/project/cloudinary.
Comment #12
avpadernoOnly 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.
Comment #13
avpadernoThis is the message I sent.
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.
Comment #14
lquessenberry commentedI am also happy to support this. I wish I could add members, but I can't.
Comment #15
wouters_f commentedIt's good!
Added alvar0hurtad0 as maintainer
Comment #16
wouters_f commentedgave lquessenberry also maintainer rights so they can also manage maintainers and also nginex.
Comment #17
lquessenberry commentedThanks wouters_f I hope you are well old friend.
Comment #18
avpadernoTruly, alvar0hurtad0 has been added as co-maintainer. To be maintainer, he should have all the permissions on the project.
Comment #19
alvar0hurtad0Now I've permissions to create releases and push to repo.
We are a lot of maintainers, how are we supposed to coordinate?
Comment #20
avpaderno