🇮🇳India @vinodhini.e

Hi @macpati, Can you try solution 2?

@deepak tomar, I tested this module on Drupal 10.5.1.

Encountered a couple of errors on the configuration page.

While testing with Merge Request #13, I have attached the results for reference.

Hi, Tested with Drupal 10.5.1

Installed the module and ran phpcs.
Encountered the same errors and warnings as reported.
Applied Merge Request #5.
After applying, all errors and warnings were resolved.
Confirmed this patch fixes the issues.
Thanks.

Hi @ali rizvi,

Tried to reproduce the issue by following the steps mentioned, but I was not able to replicate the fatal error.

Tested with:
Drupal core: 11.2.3
Profile module: 8.x-1.12
Views Entity Form Field module: 8.x-1.0-beta12

After installing the Profile module (without creating any Profile types/fields) and enabling Views Entity Form Field, the site worked as expected without crashing.

Could you please share the specific module versions and environment details where you encountered the error? That will help in reproducing it more accurately. Thanks.

Hi, Tested with the latest releases of Extension Reference Field and Theme Switcher by User modules.

All available themes are correctly listed.
Able to save the selected theme successfully. Thanks.

Hi @benstallings,
Fixed the PHPCS issues and submitted a Merge Request. Please review. Thanks.

Hi, Tested this module on Drupal 10.5.1.

Encountered the same error: Call to undefined method Drupal\Core\Asset\LibraryDiscoveryCollector::getLibraryByName().

Due to this, the Language Dropdown block could not be placed.

Issue occurs immediately after enabling the module and attempting to add the block.

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

Hi, Tested the module on Drupal 11.2.3 and confirmed it is compatible with D11. Thanks.

Hi, I also reviewed the updated project page and can confirm it looks good and up to date. Thanks.

Hi @benstallings,

Thanks for checking. When I run phpcs locally on Drupal 11.2.3, I’m seeing multiple issues not reflected in the pipeline, for example:

End of line character is invalid (\n expected, \r\n found) across many files.

Unused variables (e.g., $machine_name, $default_value, $errors, $key, $cert_field, $acsUrl).

Use of t() in classes instead of $this->t().

User::loadMultiple should be replaced with dependency injection.

#options values should run through t() for translation.

In idp_form.js, true/false should be uppercase TRUE/FALSE.

These are the kinds of errors/warnings I’m still encountering locally.

Hi, Tested this module on Drupal 10.5.1 and encountered the compatibility issue. After applying patch from MR #8, the module works as expected and is compatible with Drupal 10. Thanks.

Hi, Tested this on Drupal 11.2.3 with the Gin theme and Gin login enabled and /user/login set as the 403 page. As mentioned in the @wilson3 comment, after testing, the issue could not be reproduced — the login form rendered correctly and no broken layout was observed.

Could you provide more detailed steps to reproduce the issue?

@ushma, Yes, its working fine. Moving RTBC. Thanks.

Hi @jwilson3,

Steps to Reproduce

Installed Drupal 11.2.3 with the standard profile.

Verified that anonymous user registration is disabled by default (/admin/config/people/accounts → Who can register accounts? = Administrators only).

Enabled Gin theme and set it as the default theme.

Installed and enabled the Gin Login module.

As an anonymous user, visited /user/register.

Encountered the same and the The page was unstyled — the page--user--register.html.twig template from Gin Login was used, but stylesheets were missing and the gin-login body class was not present.

Applied patch #48.

Retested /user/register as anonymous.

The issue was resolved — page styles loaded correctly, and the gin-login body class appeared as expected.

Thanks.

Hi, Steps to Reproduce

Installed and tested this module on Drupal 11.2.3

Create a View of content (nodes) and configure it to display Fields.

Add the NodeHtmlTitle field (Content: Title).

Toggle the “Link to the Content” option:

Disable it → Save → title is not linked.

Enable it again → Save → previously, the title would not appear as a link (bug).

After applying Merge #28, re-enabling the option now correctly shows the title as a link. Thanks.

Hi, Installed this module on Drupal 11.2.3 and encountered compatibility issues with Drupal 11. After applying Patch #3, the module is compatible. Thanks.

Hi, Steps to Reproduce

Installed the module on Drupal 11.2.3.

While importing a CSV for meta tags, encountered the same issue as mentioned in this issue queue—import failed due to missing file validation plugin for extensions.

After applying Merge #11, the CSV could be uploaded successfully without any errors.

Merge #45 resolves the compatibility issues. Thanks.

Hi, Tested this module on Drupal 11.2.3 and encountered compatibility issues.
After applying patch #5, it worked fine and is now compatible with Drupal 11. Thanks.

Hi, I installed this module on Drupal 11.2.3 and tested with phpcs. I encountered the same warnings and errors as previously reported.

I also applied Merge Request #67, but I am still seeing some warnings and errors related to phpcs.

Would you be okay if I prepare and provide a patch to address these remaining warnings and errors for the phpcs issues?

Hi @natefollmer,

Thanks for the clarification. In my earlier setup I only added prefixes for some languages without filling in the domain field. After updating the configuration so that every language (including prefix-only ones) has both a domain and a prefix defined, the warnings are gone and everything is working fine now.

Hi @macpati,

This error happens because Drupal’s JavaScript aggregation uses the mck89/peast library (a PHP-based JS parser) to optimize JavaScript. Older versions of Peast sometimes enter an infinite loop when parsing certain JS strings, which triggers the Xdebug “possible infinite loop” error.

Solution 1 (recommended):

Update Peast to the latest version and clear caches: Run below command

1. composer update mck89/peast --with-dependencies
2. drush cr

This resolves the issue in most cases.

Solution 2 (workaround):

If the error still occurs after updating, disable Aggregate JavaScript at:
/admin/config/development/performance.
The site will continue to work normally (just slightly slower). The error usually means one of your custom JavaScript files has invalid syntax. You can find it by running your custom JS files through a linter (e.g. https://jshint.com or ESLint) to find and fix invalid syntax.

Try this out and let us know the status. Thanks.

Hi, Installed this module on Drupal 11.2.3 and encountered the same compatibility issue.

After applying the Merge #19, the module is compatible with Drupal 11 and working fine. Thanks.

Hi @macpati,
Steps I followed to reproduce
Tested on Drupal 11.2.3.
Enabled Claro as the admin theme.
Navigated to Configuration → Development → Performance.
Enabled “Aggregate JavaScript files”.
Refreshed multiple pages.
Checked Recent log messages.

Result
Tried the same steps mentioned in the issue to reproduce, but I was not able to replicate the error.
No errors were logged. The site works fine even with JavaScript aggregation enabled.

Hi, I installed this module on Drupal 11.2.3 along with the Paragraphs module (same version mentioned in the issue), but I was not able to reproduce the reported problem.

Could you please provide more details or exact steps to help replicate the issue?

Hi,
I tested this module on Drupal 11.2.3.
Faced the same issue on the configuration page (TypeError: Cannot access offset of type string on string).

After applied Merge Request #38. Uninstalled and reinstalled the module so the updated config was imported.

After reinstall, the configuration page is accessible and working as expected. Thanks.

Hi, Module was installed on Drupal 11.2.3.
Observed an issue where the theme select box on /available-theme/add was empty, preventing selection of available themes.
After applying the Merge #4 , all available themes are correctly listed, and the functionality works as expected.
Thanks.

Hi, I have followed all the steps you mentioned, but I am still getting warnings when saving the configuration.

Here is what I tried:
Installed and enabled Advanced Language Negotiation module
Installed and enabled the Domain module as suggested.
Added domain URLs/prefixes for each language under /admin/config/regional/language/detection/url.
Verified that every enabled language has a domain mapping.
Cleared all caches using drush cr after configuration changes.
⚠️ Even after completing the above steps, I am still getting warnings when saving the configuration.

Please advise if I missed any additional configuration or if the patch is required to suppress these warnings. Thanks.

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

Hi, Steps to reproduce

Installed the Taxonomy Menu module on Drupal 11.2.x.
Created a vocabulary and added terms.
Built a menu from the vocabulary.
Tried to disable a menu link from the Menu UI while keeping the related taxonomy term published.
Issue: The menu link could not be disabled unless the taxonomy term itself was unpublished.

After applying Merge Request #16
Able to disable the specific menu link directly from the Menu UI.
Functionality is working fine as expected. ✅

Thanks!

Hi, Tested this on Drupal 11.2.x and confirmed that the changes are working as expected after applying Merge #190. The prefix removal is reflected correctly, and the prefixed classes are no longer present.
Thanks.

Hi @intrafusion,
Installed the module on Drupal 11.2.3.
Encountered compatibility issues with Drupal 11.
Applied the provided Merge #9 to fix the issues.
Verified that the module is now compatible with Drupal 11. Thanks.

Hi @shubhamgoel,
Installed this module on Drupal 11.2.3 and encountered the same issue.
Applied the patch, but the issue was not fixed.
Still facing the same issue reported by @sandeep_k.
Thanks.

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

Hi @fago, Installed this module on Drupal 11.2.x. I have applied merge #132, and the renaming has been completed successfully. The “Canvas” is now correctly renamed instead of “Experience Builder.” Thanks.

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

Uploaded correct screenshot.

Hi, I tested this module on Drupal 11.2.x and encountered the same issue. After applying Merge Request #31, the caption is now wrapped in a semantic / structure as expected.

Attached the screenshot for reference. Thanks.

Hi, I tested this module on Drupal 11.2.x and encountered a compatibility issue. After applying Merge Request #6, it is working correctly and is now compatible with Drupal 11.
Thanks!

Hi, I tested this module and noticed a grammatical mistake in the README.md file. After applying MR #12, it is now showing correctly. Thanks.

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

Hi, Installed this module on Drupal 11.2.3.
Applied Merge Request 13. After applying the patch, the module is now compatible with Drupal 11. Thanks.

Hi, Installed this module on Drupal 11.2.3.
Faced the same compatibility issue initially.
Applied Merge Request 7.
After applying the patch, the module is now compatible with Drupal 11 and working fine. Thanks.

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

Hi, Could you please provide more details to replicate this issue?
Currently, the issue only includes the error message, and I’m unable to reproduce it on my local. Thanks.

Hi, I encountered this issue on Drupal 10.5.1.

Steps I followed:

Installed the module on Drupal 10.5.1.
Created a new image style and added the Add Watermark effect.
Encountered the warning message when trying to save the effect.
Applied Merge Request #4.
Repeated the same steps to add the watermark effect.

The warning message still appears, and the issue is not resolved by this patch.

vinodhini.e → changed the visibility of the branch 3544754-drupal-11-compatible to hidden.

Hi, Tested this on Drupal 11.2.3 and encountered the same issue.

Applied Patch #2, and it seems to be working fine.

Thank you!

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

vinodhini.e → changed the visibility of the branch 3544754-drupal-11-compatibility to hidden.

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

Hi, I tested this issue on Drupal 10.5.1 with the specified theme and observed the following:

Before applying the patch:

When hovering over the search block, it was overlapping the main navigation menus.

After applying Merge Request #8: The overlapping issue is resolved.

The search block no longer overlaps the main navigation menus. The layout and UI look fine. Thanks.

Hi,
I have provided a Merge Request. Please review it once. Thanks.

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

Hi, Steps to Reproduce the Issue and Verify the Fix

Tested on Drupal 11.2.3.
Installed and enabled Replicate and Replicate Actions modules.
Created two users:
User A → can create content
User B → can replicate content

Logged in as User A and created a Page (/node/add/page).
Logged in as User B, went to the Page created by User A, clicked Replicate, and saved the replicated page.

Before applying the patch: The replicated page author was User A (original author).

Applied MR !12, cleared cache with drush cr, and repeated the same steps.

After applying the patch: The replicated page author is now User B (replicating user).

Its working fine. Thanks.

Hi,
Tested the module on Drupal 10.5.1.
Followed the steps mentioned in the issue but could not reproduce the problem.
The JS Cookie dependency added in 4.0.1 was installed and enabled successfully after running update.php (or drush updb) without applying the merge request.

Steps followed:

composer require drupal/fpa:4.0.0
drush pm:enable fpa -y
composer require drupal/fpa:4.0.1
drush updb -y
drush pm:list --filter js_cookie

Thanks.

Hi, Installed the module in Drupal 11.2.3.
Applied Merge Request #8, Cleared caches and verified the changes.
version: VERSION lines were removed from libraries.yml.
Checked page source: core version query strings are no longer present.
Thanks.

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

Hi, Installed the module on Drupal 11.2.3.
Encountered the same error after installing the module.
Applied Merge Request #34 and the issue was fixed.
Verified that it is now working fine. Thanks.

@rohit rana, Thanks for the update.

Hi, Installed the module on Drupal 11.2.3.
Applied Merge Request #45.
Tested the compatibility after applying the patch and its working fine.

Hi @rohit rana,
Just wanted to confirm, I am facing this issue on Drupal 11.2.3. Did you check it on the Drupal 11.2.x version?

Hi @rohit rana,

Tested on Drupal 11.2.3.
Applied Merge Request #3, which fixed some coding standards issues.
After applying the merge, the module still shows some coding standards issues on Drupal 11.2.x. Need to check.

FILE: /var/www/html/web/modules/contrib/blog-3544130/src/BlogListerInterface.php
----------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
----------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/src/BlogUninstallValidator.php
-----------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
-----------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
-----------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
-----------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/src/Controller/BlogController.php
--------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
--------------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
--------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--------------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/src/BlogLister.php
----------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
----------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/src/BlogBreadcrumbBuilder.php
----------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
----------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/src/Plugin/Menu/MyBlogLink.php
-----------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
-----------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
-----------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
-----------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/tests/src/Functional/BlogTestBase.php
------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
------------------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
------------------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/tests/src/Functional/MyBlogLinkTest.php
--------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
--------------------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
--------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--------------------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/tests/src/Functional/InstallUninstallTest.php
--------------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
--------------------------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
--------------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--------------------------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/tests/src/Functional/BreadcrumbTest.php
--------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
--------------------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
--------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--------------------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/tests/src/Functional/BasicBlogTest.php
-------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
-------------------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
-------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
-------------------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/tests/src/Functional/GenericTest.php
-----------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
-----------------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
-----------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
-----------------------------------------------------------------------------------------

FILE: /var/www/html/web/modules/contrib/blog-3544130/tests/src/Functional/EmptyBlogTest.php
-------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
-------------------------------------------------------------------------------------------
1 | ERROR | [x] End of line character is invalid; expected "\n" but found "\r\n"
-------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
-------------------------------------------------------------------------------------------

Hi, Tested on Drupal 11.2.3 with the Preview Link module:

Installed and enabled the module.
Updated configuration for the Article content type.
Visited the preview link for an Article node.
Cleared caches and reviewed reports/debug logs.

Result: Unable to reproduce the reported issue. Node preview works as expected, and no errors were encountered after module installation or when visiting node pages.

Hi, Steps to Reproduce

Installed this module on Drupal 11.2.3.
Checked /admin/appearance/styleguide.

In the Form elements section, observe that:

Radio buttons have multiple options, but none are selected by default.
Checkboxes have multiple options, but none are selected by default.

After applying the Merge #32, one radio button and one checkbox option are selected by default. Its working fine. Thanks.

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

@anirudhsingh19, Thanks for the update. I verified this after clearing the cache, and its working fine for me. Thanks..

Hi,
Steps to reproduce the issue
Installed the Smart Date module in Drupal 11.2.3. Tried to set the Smart Date Duration (smartdate_duration) field formatter in the Manage Display for the Article content type.
Encountered InvalidArgumentException and was unable to set the formatter. Applied Merge Request #182. Cleared caches and reopened Manage Display.

Successfully set the Smart Date Duration formatter without issues.
Verified that the field works correctly in display view mode. Thanks..

@eric.vvf, Thank you for the update! I’ll work on fixing the PHPCS issues and provide a merge request. Thanks.

Hi, Installed the module on Drupal 11.2.3 and verified compatibility with Drupal 11 after applying Merge Request #2. Its working fine. Thanks.

Hi @rudolfbyker,
I have tested the Time Field module on Drupal 11.2.3.

All features mentioned in the issue description are present and working correctly:

Optional Start time and Optional End time checkboxes are available in the field instance configuration.

Both Start time and End time can be set as optional when specifying default values.

Additional formatter options for only Start time or only End time are available in the field formatter configuration.

Screenshot attached for reference. Thanks.

Hi, I am using the Gin theme and encountered the same issue on Drupal 11.2.3. The problem occurred while creating content that includes a link field.

Even after applying Merge Request #666, the issue still persists and was not resolved.

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?