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?
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.