🇮🇳India @vinodhini.e

Hello @eric.vvf,
I installed the module on Drupal 11.2.3 and ran PHPCS checks.
There are some coding standard violations reported.
Could you please confirm if you would like me to work on fixing these issues and submit a patch or merge request?
Thanks.

Installed the module on Drupal 11.2.3.
The module was not compatible with Drupal 11.
Applied Merge Request #3, and the module is now compatible with Drupal 11. Thanks.

Hi,
Installed the module on Drupal 11.2.3.
Applied Merge Request #8, the module became compatible with Drupal 11 and is now working fine.
Thanks.

Hello,

Steps followed:

Installed the Gin theme on Drupal 11.2.3
Added three taxonomy reference fields — Tags, Subject, and Category.
Changed the order of these fields in both Manage display and Form display.
I see the "you have unsaved changes" message. Not able to reproduce the issue
Is there any additional step we might be missing?

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

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

Hi, Steps to Reproduce:

Tested the module on Drupal 11.2.3.
Installed the CRM Field module without installing the CRM module, and it installed.
Applied Merge #93, Attempted to install the CRM Field module without installing the CRM module.

Observed that after applying the patch, the CRM Field module cannot be installed independently. Thanks.

Hi, I have installed this module in Drupal 11.2.3 and tested the functionality. I encountered the same issue as originally reported.
After applying Merge Request #34, the issue still persists and has not been fixed.

Hi, Steps to Reproduce the Issue

Tested this on Drupal 11.2.3.
Faced the same issue: after form submission, the confirmation message was not visible. Applied Merge Request #670.
After applying, the confirmation message appeared and working fine.

Thanks.

Hi, I have updated composer.json to require "setasign/fpdi": "^2.6.4" and ran composer update.
I tested the Views PDF functionality locally on Drupal 10.5.1, and the memory exhaustion / DoS issue is no longer observed.
The patch successfully resolves the reported vulnerability.

Thanks.

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

Hi @maxilein,
Steps to Reproduce (Unable to Replicate the Issue):
1. Upgraded Drupal core from 11.2.2 to 11.2.3.
2. Ran database updates using: drush updb
3. The update ran successfully without any errors. Unable to reproduce the reported issue.

Could you please provide more details or specific steps so I can attempt to reproduce the issue on my setup?

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

Hi, I have installed this module on a Drupal 11.2.2.
Identified compatibility issues with Drupal 11.
After merging MR !18, the module is now compatible with Drupal 11. Thanks.

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

Hi, Steps to Reproduce the Issue
Installed the module on a Drupal 10.5.1 site.
Observed the issue: Initially, the logout message markup was not rendered correctly. The user was not shown any login link after being logged out.
Applied the patch from Merge Request #80, The logout message markup was rendered properly.
The message now correctly includes a login link, allowing users to log in again.

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

Hi, I have installed this module on a Drupal 11.2.2.
Identified compatibility issues with Drupal 11.
After merging MR !7, the module is now compatible with Drupal 11. Thanks.

Hi, I have installed this module on Drupal 11.2.2.
I was able to replicate the issue in the configuration form.
After applying the provided patch #4, the issue was resolved.

The Canonical Protocol options are now correctly displayed in the configuration form.
Thanks.

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

Hi, I have installed this module on Drupal 11.2.2.
I faced the same issue while adding and editing the UUID configuration.
After applying Merge 16, it is working fine.

I have installed this module on Drupal 11.2.2.
I ran the Upgrade Status report and found two issues.
I have fixed both issues, and the module is now compatible with Drupal 11. Thanks.

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

Hello @milant, I tested the module using Patch #5 on Drupal 11. However, I'm encountering the following fatal error when trying to install the module:

TypeError: Drupal\saml_rules\EventSubscriber\SAMLRulesAnonymousLogin::checkAuthStatus(): Argument #1 ($event) must be of type Symfony\Component\HttpKernel\Event\GetResponseEvent, Symfony\Component\HttpKernel\Event\RequestEvent given, called in /var/www/html/vendor/symfony/event-dispatcher/EventDispatcher.php on line 246 in Drupal\saml_rules\EventSubscriber\SAMLRulesAnonymousLogin->checkAuthStatus() (line 24 of modules/contrib/saml_rules-3434309/src/EventSubscriber/SAMLRulesAnonymousLogin.php).

Hi, @zhelmet , Could you please provide it as a merge request?

Hi, I have installed this module on a Drupal 11.2.2.
I encountered the same issue when visiting the /admin/config/anti-duplicates page.
After applying the patch from MR !10, its working fine without any issues. Thanks.

Hi, I have installed this module on a Drupal 11.2.2.
Identified compatibility issues with Drupal 11.
After merging MR !4, the module is now compatible with Drupal 11. Thanks.

Hi @ericgsmith,
I've updated the core_version_requirement in the .info.yml file to support both Drupal 10.2+ and future versions, including Drupal 11. Thanks.

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

Hi @akashkumar07,
I've updated the constructor parameter details and verified the code with PHPCS — no warnings or errors were reported.
Please review and let me know if anything else needs to be addressed.
Thanks..

Hi, I have tested this module on Drupal 11.2.2.

I encountered a fatal error when an entity referenced in a menu item was deleted.

To resolve this, I updated the TranslatedMenuLink.php file by making the $entity property nullable and adding a check to ensure both entity_type and entity_id are set before attempting to load the entity.

This avoids the TypeError when the entity is missing or deleted and ensures graceful fallback behavior for title, description, and cache methods.

After applying the changes, the issue is resolved and the menu works correctly without throwing errors.

Please review and let me know if anything further needs to be added or adjusted. Thanks.

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

Thank you for the detailed context. I'll review #3477375 before proceeding further.

@abramm,
Thank you for your feedback.
My intention was not to hijack your merge request, but to address the Twig deprecation issue that I encountered while testing the module on Drupal 11.2.2. I made minimal changes limited only to the Twig template file only.
Specifically, I removed two lines related to the deprecated spaceless, as it is no longer supported in Drupal 11 / Twig 3.12+.
These changes were committed directly to the current branch: 3535811-drupal-11-support, to help ensure compatibility with Drupal 11.

Hi, Installed this module in Drupal 11.2.2.
Encountered a Twig deprecation error related to the use of the spaceless filter (Since Twig 3.12: Twig Filter "spaceless" is deprecated).
Updated the Twig template file to remove the deprecated spaceless filter and replaced it with a compatible structure.
Submitted a Merge Request with the fix.
The module is now working as expected and is compatible with Drupal 11. Thanks.

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

Hi, I have installed this module on a Drupal 11.2.2.
Identified compatibility issues with Drupal 11.
After merging MR !3, the module is now compatible with Drupal 11. Thanks.

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

Hi , I have installed this module on Drupal 11.2.2.
The module was not compatible with Drupal 11 initially.
After applying Merge #6, the issue was resolved.

The module is now working fine and compatible with Drupal 11. Thanks.

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

Hi,
I installed the module and reproduced the issue on Drupal 11.2.2.
The paragraph label set in the field configuration was not shown when adding a paragraph.
I applied the patch from Merge Request 49.
After applying the custom label was correctly displayed when adding a paragraph.

Thanks.

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

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

Hi @randalv, I have installed this module on a Drupal 11.2.2.
Identified compatibility issues with Drupal 11.
After merging MR !1, the module is now compatible with Drupal 11. Thanks.

Working on it!

Hi, I have installed the module on a Drupal 11.2.2 and applied the merge request #2

Reviewed the test file, which covers test cases for the number of lines in the DeferJsForm.

Thanks.

Hi, I also replicated the issue on Drupal 11.2.2.

Encountered a missing Media module dependency during testing.

After applying Merge Request #9, working fine. thanks.

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

Hi @baldwinlouie,
Steps to Replicate the Issue:
I followed the steps mentioned to reproduce the issue.
I also encountered the same issue — the font changes were not applied on the frontend.
After applying Merge Request #94, the font settings were applied correctly.
I tested with multiple fonts, and it is now working as expected.

Thanks.

Hi, I have tested this module on Drupal 11.2.2 and I also faced the same issue while running the Upgrade Status module.
After applying merge request #39 and running Upgrade Status again, the issue did not occur, and it is working as expected.

Hi , Tested on Drupal 11.2.2 with Gin theme and Navigation module:

I have set up the Gin theme on Drupal 11.2.2.
After installing the Navigation module, I also encountered the same padding issue when flushing the image styles.
After applying and merging MR !639, the issue is resolved.
The padding now appear to be working as expected.

Thanks for the fix!

Hi, I upgraded to the latest version 8.x-1.38.
After the upgrade, I was not able to reproduce the issue.
It seems to be working fine without any issues on Drupal 11.2.2.

Hi, I have installed this module on Drupal 11.2.2.
It was not compatible with Drupal 11 – also facing coding standards (PHPCS) issues.
After merging the 4.x branch, it became compatible.
The PHPCS issues have also been fixed. Thanks.

Hi, I have tested this module on Drupal 11.2.2 and applied Merge Request 9. It is compatible and working without any issues. Thanks.

Steps Taken to Reproduce the Issue (Unable to Reproduce)
1. Installed the module on Drupal 11.2.2.
2. Navigated to the Rigel settings page and checked the font settings.
3. Verified that we were able to change the fonts from the dropdown without applying the patch.

We were not able to reproduce the issue as described.

I have also tested this feature on Drupal 10.4.8, and the expanded options working as expected. Thanks.

@nick dewitte,

Steps to Reproduce and Test the Fix
Installed the module on Drupal 11.2.2.
Replicated the issue where the error message is restricted to 128 characters.
Applied the patch from Merge Request !35.

Re-tested by adding an error message longer than 128 characters. and its working fine.

Thanks.

Hi, I’m also encountering the same problem on Drupal 10.5.1.

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

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

Hi @harlor,
Steps taken to test the issue and verify the fix:
1. I faced the same issue while installing the module on Drupal 11.2.2.
2. Applied Merge Request #13 from the issue queue.
3. After applying the MR, I was able to install the module without any errors.

Verified that the /admin/structure pages are loading correctly.

Hi,

I faced the same issue while installing this module on Drupal 11.2.2.
After applied Merge Request #7, I was able to install the module successfully, and it is now compatible with Drupal 11.2.2.

Hi @programeta,

Steps I followed to replicate and test:

1. Installed Drupal core version 11.2.2 locally.
2. Installed the Migrate Wizard module using Composer.
3. Tried to import configuration using drush cim and encountered the same fatal error as reported:
4. Applied Merge Request #31 from the issue queue.

After applying the MR, I was able to run Drush commands like drush cim, drush uli, etc., without any errors.
The patch from MR #31 resolves the compatibility issue with Drupal 11.2.2.

Thanks!

Ask ChatGPT

Hello @Imoeni, I encountered the same issue while working with the CKEditor 5 Premium Features module.
Below are the steps I followed and the results:

1. Installed the CKEditor 5 Premium Features module version 1.4.0 on a Drupal 11.2.x site.
2. Ran the Upgrade Status module to scan for deprecated functions.
3. Encountered the following error during the scan:
Call to deprecated function editor_load(). Deprecated in drupal:11.2.0 and is removed from drupal:12.0.0.
4. Applied the patch provided in MR !32.
5. Re-ran the Upgrade Status scan after applying the patch.

The patch successfully removes the two deprecation errors in Drupal 11.2.x.

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

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

@divyansh.gupta, Tested MR !32 on Drupal 11.1.7. The patch applied cleanly and and is working fine.

Steps to Test:

1. Install and enable the Reset Password Email/SMS module.
2. Add the corresponding block via Block layout.
3. After applying the patch, the Enter key correctly triggers the Next button by default.

Thanks.

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

Hi, I encountered this issue identified the cause. I've implemented a fix and provided a merge request. I also tested the fix on a Drupal 11 site, and it's working as expected.

Please review the MR and let me know if any further changes are needed.

@mradcliffe,

Thank you for following up! Yes, the instructions were clear and straightforward.
This is my understanding: I was able to identify the correct file (calendar/meetings.csv) and confirm that the meeting time needed to be updated from 17:00 UTC to 13:00 UTC starting from 2025-07-24, as proposed.

I also noticed that meetings.md references a .ics file (files/mwg.ics), which wasn’t present in the repo, so I paused there and planned to confirm with maintainers whether that file should be updated or generated.

If my understanding is incorrect at any point, please feel free to clarify.

Thanks.

Hi,
I have installed this module and applied the changes on Drupal 10.4.5. It is compatible with Drupal 10. Thanks.

Hi @mradcliffe,
I had prepared a similar update locally, and I see your patch already covers the proposed change (13:00 UTC). Thanks for getting it in!

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

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

Hello @ok4p1,
Thank you for the explanation.
I have tested this scenario, and it is working as expected.
Marking the issue as RTBC. Thanks.

Hi,
I have installed this module and applied the changes. It is compatible with Drupal 11. Thanks.

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

I have merged the code changes that provide compatibility with Drupal 10, 11, and future releases. Thanks.

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

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

Hi @ok4p1,

Hi,

Thanks for the patch! I tested this on a local Drupal 11 site with Preview Link v2.2.0-alpha2, but unfortunately, it’s not working as expected.

Steps to replicate:
Added an Entity Reference field to a content type.

Set "Number of values" to 1 (single entity reference).

Applied the patch from this MR and cleared cache.

Edited a node of that content type.

Expected: "Save" and "Save and regenerate preview link" buttons should be hidden.
Actual: Both buttons are still visible.

Hi @dmarcana,

Tested on a Drupal 11 site with the TB Mega Menu module.
Replicated the issue by creating an icon-only menu — screen readers announced buttons with no accessible name.
Inspected the HTML and confirmed missing aria-label attributes.
After applying the MR, re-tested using WAVE — no more accessibility errors related to missing labels.
Menu items are now properly announced with context (e.g., “Open main submenu”).

Thanks.

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

@claudiu.cristea, Thanks for the update.

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

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

Hi,
I have installed this module and applied the changes on Drupal 11.1.7. It is compatible with Drupal 11. Thanks.

I have tested this module locally on Drupal 10.4.8, and after applying the changes, it installed without any issues. Thanks!

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

Hi @webflo, I have merged the code and confirmed that it is compatible with Drupal 10 and 11. I have also tested it with Drupal 10.4.8.

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

Hi @
I reproduced this issue locally using Drupal 11.1.7, and after applying the changes, Working fine. Thanks!

Hello,
To address this issue, I recommend updating the project description to explicitly state that this module extends the Default Content module.

Suggested text for the project page:

This module extends the Default Content module and is part of its ecosystem.

This addition will help ensure the module appears appropriately on the Default Content ecosystem page.

Thank you.

Hi @grimreaper,
I have fixed some deprecated functions to support Drupal 11 compatibility. Please review the changes when you get a chance.