@uttam

Drupal version: 10.3.13
php version: 8.3.14
Module version: 1.0.2

I tested this on my local Lando environment and did not encounter the memory exhaustion issue, which could be due to differences in PHP memory limits between my setup and your test environment. I have also tested by decreasing the memory_limit to 512M, but I think since I do not have very large entries in the Delay Submit form, I was unable to reproduce the issue. The error likely occurs when handling large form submissions with deeply nested arrays, causing excessive memory usage, especially with

print_r($form_values, TRUE)

, which attempts to log the entire dataset. In this case, the form values are stored as a nested array, where each entry contains an associative array with form_id and delay_time. When tracking a large number of forms, this structure can grow significantly, and logging the entire dataset using print_r() can result in excessive memory consumption, leading to fatal errors. While increasing the PHP memory_limit can help as a temporary workaround, it does not address the root cause, which is inefficient logging of large data structures. This patch resolves the issue by replacing print_r() with

json_encode(array_slice($form_values, 0, 5

), JSON_PARTIAL_OUTPUT_ON_ERROR), limiting the logged data to only the first five entries and ensuring non-array values are properly handled, thereby reducing the risk of excessive memory usage and preventing crashes in environments with strict memory constraints. Even though I haven't personally encountered the issue, I recognize the value of this fix in making logging safer and more efficient. I support this patch and this issue can be move to RTBC.

Drupal version: 10.3.13
Php version: 8.3.14
Module version: 3.0.2
I have reviewed and tested the patch → , and it correctly addresses PHP 8.3 compatibility issues by explicitly declaring the $config property in both ContentNotifyManager and NotifyExtendForm. This prevents runtime errors due to undefined properties and ensures compliance with stricter initialization rules in PHP 8.3. The changes are also align with Drupal’s coding standards. The patch is working as expected, and I am moving the issue status to RTBC

This patch resolves a TypeError in Quicktabs::getSetMapping() by changing the return type from bool to array, ensuring it accurately reflects the actual return value ($this->setMapping), which is always an array; this prevents runtime error which was occuring by type mismatch, enforces strict type safety as required in PHP 7+ and PHP 8+
Hence, Moving the state of the issue to RTBC.

Can you provide steps on how I can replicate this issue on my local? I am using Webform version 6.2.5 and Drupal version 10.3.13, but I haven't encountered this error on the Submissions tab or the Submissions list.
I think this error occurs when Drupal tries to generate a Webform submission view URL without the required "webform" parameter, which might due to a missing or deleted Webform.

The patch successfully deprecates typedConfigManager() in ConfigFormBase, ensuring that it is no longer used in Drupal core while maintaining backward compatibility until its removal in Drupal 12. After applying the patch, analysis tools like Intelephense correctly recognize the deprecation, highlighting it in the codebase. However, no warnings appear in the Drupal logs (dblog), suggesting that core no longer calls this method at runtime. To further verify this, I also created a custom module with a configuration form that explicitly called typedConfigManager() inside validateForm(). While the function was executed, no deprecation warnings were logged, reinforcing the conclusion that this method is no longer triggered within Drupal core itself but depreciation message was triggered in codebase. Overall, the patch achieves its goal without introducing regressions, and developers should ensure they update their custom code accordingly before Drupal 12.
Hence Moving the issue to RTBC.

I have reviewed the changes and confirmed that it correctly replaces the deprecated $.trim() function with JavaScript’s native .trim(), which is fully compatible with jQuery 3.5+ and the modern browser environment used in Drupal 11. The change does not alter the core functionality, as .trim() provides the same behavior as $.trim(), ensuring that the text value is properly trimmed before processing.

After testing from the branch 3510732-.trim-is-not, I tested the character counting functionality in text fields, and everything works as expected without any errors. The update does not introduce any regressions, as .trim() is widely supported in modern JavaScript. Since the fix is correct and verified, I am moving this issue to RTBC.

The mentioned warnings were occuring because in PHP 8.4, the practice of allowing parameters to be null without explicitly declaring them as nullable has been deprecated. This means that if a function parameter has a default value of null, it must be explicitly marked as nullable using ?
The MR addresses the issue correctly and I have tested the MR and those are resolved now. hence moving the issue to RTBC.

I have reviewed the changes made in the 3127124-t-calls-should branch, and the reported "t() calls should be avoided in classes" warnings have been successfully resolved using $this->t() and new TranslatableMarkup().

Additionally, I ran PHPCS on the affected files, and no related errors or warnings were found. I also tested the module's functionality, and everything is working as expected.

Since the issue has been reviewed and tested, I am moving it to the RTBC state.

Drupal automatically uses the current user if none is explicitly provided. So we can simplify the code by removing the $user variable and updating the access check like this $check = $entity->access('update'); as mentioned in the MR.
I have tested the patch as well and it's worked fine, moving this to RTBC.

I attempted to replicate the issue on version 2.0.3 of the module and found that it still occurs. However, after cloning the module's 2.0.x dev version for testing, I noticed the error had already been resolved in a previous commit. I found this related issue: #3395325 🐛 Deprecated function: Creation of dynamic property (with php 8.2) Fixed . A version release should resolve it.

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

I have tried to raise the MR for in my case also the pipeline is failed and the below are the failed jobs:

composer (max PHP version)
      .git/**/*: excluded 75 files                       
Uploading artifacts as "archive" to coordinator... 201 Created  id=4263642 responseStatus=201 Created token=glcbt-64
Uploading artifacts...
build.env: found 1 matching artifact files and directories 
Uploading artifacts as "dotenv" to coordinator... 201 Created  id=4263642 responseStatus=201 Created token=glcbt-64

Cleaning up project directory and file based variables

ERROR: Job failed: command terminated with exit code 1


    
composer
 .git/**/*: excluded 75 files                       
Uploading artifacts as "archive" to coordinator... 201 Created  id=4263534 responseStatus=201 Created token=glcbt-64
Uploading artifacts...
build.env: found 1 matching artifact files and directories 
Uploading artifacts as "dotenv" to coordinator... 201 Created  id=4263534 responseStatus=201 Created token=glcbt-64

Cleaning up project directory and file based variables

ERROR: Job failed: command terminated with exit code 1


    
composer (next minor)
  .git/**/*: excluded 75 files                       
Uploading artifacts as "archive" to coordinator... 201 Created  id=4263533 responseStatus=201 Created token=glcbt-64
Uploading artifacts...
build.env: found 1 matching artifact files and directories 
Uploading artifacts as "dotenv" to coordinator... 201 Created  id=4263533 responseStatus=201 Created token=glcbt-64

Cleaning up project directory and file based variables

ERROR: Job failed: command terminated with exit code 1


    
composer (previous minor)
      .git/**/*: excluded 75 files                       
Uploading artifacts as "archive" to coordinator... 201 Created  id=4263523 responseStatus=201 Created token=glcbt-64
Uploading artifacts...
build.env: found 1 matching artifact files and directories 
Uploading artifacts as "dotenv" to coordinator... 201 Created  id=4263523 responseStatus=201 Created token=glcbt-64

Cleaning up project directory and file based variables

ERROR: Job failed: command terminated with exit code 1

I was able to reproduce the following error using the given setup:
Drupal version: 10.3.2
PHP version: 8.3.14
Error:
Deprecated function: Creation of dynamic property Drupal\user_email_verification\Plugin\views\filter\EmailVerification::$value_value is deprecated in EmailVerification->init() (line 110 of EmailVerification.php).

The issue was caused by the use of a dynamic property, which is deprecated in PHP 8.2 and later. Applying the patch from MR 7 resolved the error by explicitly defining the missing property $valueOptions as a protected class property. Since this fixes the issue, I am updating the issue status to RTBC.

I installed the development version 2.0.x-dev and attempted to apply this merge request. However, upon installing the project_browser module, I encountered a WSOD error.

After investigating, I found a related issue that is currently postponed: Issue #3501254 🐛 Some mandatory parameters are missing ("source") to generate a URL for route "project_browser.browse". Active .

I also reviewed the source code for the changes made in the MR, and it looks good to me.

Drupal version: 10.3.2
Php version: 8.2
Module version: redirect 8.x-1.x-dev
I have tried to replicate the issue but not able to reproduce the same. I have enabled "Automatically create redirects when URL aliases are changed." in the redirect settings. Created a content with url alias /TEST and then updated the url to /TEst, after this the redirects from /TEST to /TEst and it's working properly without any redirect loop.

Drupal version : 11.0.1
PHP version : 8.3.6
Module version : 2.0.x-dev

I have tested the patch from the MR !14, it resolves the error which is occuring in config form (admin/config/alr-configuration).
Moving the issue to RTBC!

I have tested the MR !28 given by r@aveen_thakur51, it resolves the argument count error which was occuring while visting the form at "/admin/config/reading-time"
Moving this to RTBC!

Hello @jminarick, I have tested the patch from MR !8, the "Create new account" tab present in the login page is enabling/disabling as per the settings provided in the "/admin/config/people/hybrid_login" form.

@sourav_paul Hello I have resolved the fatal error and tested the same in d10 and d11, the circular redirects are successfully purging. Please review this once.
Moving this to Needs Review

Hello @Berdir, I hope you're doing well. This issue has remained unresolved for a few days, can this be fixed now?

Hello @kuzyawkk, I have applied the patch from MR !7, it's looking fine for me. Now we can configure the cancel button only to appear in node creation form and that will not appear in the content edit form.
Moving this issue to RTBC.
Thanks!

@sourav_paul Added the access check condition in the code, now the fatal error is not showing while merging terms.

@shelane Thanks for fixing the issue!

Hello,I have tested the MR 13 and haven't found any depreciated function using the upgrade status module. The MR is working fine in Drupal 11,I think it's now ready for Drupal 11 release, moving this ticket to RTBC.
Thank you

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

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

Hello everyone, I have created this Drupal Drush command which facilitates the management of circular redirects using Drush as mentioned in the issue. Firstly, It retrieves all redirect entities from the database using EntityTypeManagerInterface, constructs a map linking source URLs to their corresponding destinations, identifies circular redirect relationships where a redirect points back to its own source. I have also logged each detected circular redirect using Psr\Log\LoggerInterface and provides a user prompt to confirm the delete operation. Upon confirmation, it deletes all identified circular redirect records.

Drush command for the purging circular redirects: drush redirect:purge-circular-redirects

Please review this.

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

Hello everyone,

I have cloned the branch 3250412-new-action-needed and tested the functionality. A new action, "Generate One Time Login Links," has been created for users. This action allows us to generate one-time login links for multiple users in bulk, as described in the issue. The functionality works fine for me!

Moving this to RTBC.

The changes I have made in the controller includes, edit and delete URLs are generated using Url::fromRoute() and corresponding Link objects are created, and these links are included in an $actions array which is then rendered and included in the table rows for display. additionally, I have also included injecting the database connection via dependency injection by using use Drupal\Core\Database\Connection and Symfony\Component\DependencyInjection\ContainerInterface, rather than directly using Database::getConnection()
Please review the MR.

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

I updated the validateForm method by adding a check to ensure that the redirect_url starts with '/', '?', or '#'. If it doesn't, an error message is set for the corresponding form element, indicating that the redirect URL for the specified role must begin with one of these characters. The other existing code logic remain unchanged.
Please review this.

have applied patch #7, but the error persists: "InvalidArgumentException: The user-entered string 'node/2' must begin with a '/', '?', or '#'. in Drupal\Core\Url::fromUserInput() (line 216 of core/lib/Drupal/Core/Url.php)." I believe we need to add validation in RedirectUrlSettingsForm.php. Moving this to NW and assigning it to myself.

Hello @samit.310@gmail.com,
I have reviewed the patch from the MR !18 again, now the configurable logout message is visible after disconnecting a particular session. This works fine now.
Thanks!
Moving this to RTBC

I've created a custom permission called 'Bypass entity view redirect' and implemented it in an event subscriber to check with $this->currentUser->hasPermission('bypass entity view redirect'). If the user possesses this permission, the redirection logic is bypassed. I've also included the current user service in the event subscriber and updated the services.yml accordingly. This successfully bypasses redirection for all roles except administrators, who have this permission assigned by default
Please review this

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

Hi @samit.310@gmail.com, applied the patch from the MR, the textarea for configurable logout message is visible at "/admin/config/people/session-limit", but when disconnencting a particular session from the session limit form (/session-limit), the configured logout message is not showing for this particular disconnect session.please check this once, thank you.

Hello @KuzyaWkk, I have tested the latest commit as given in #5 on local, it's working as expected now. Not getting the console error. Thanks!
Moving this to RTBC.

I have tested MR #2 and confirmed that the auto login functionality for users is working as described in the issue. Users can be auto-logged into their desired accounts as intended. However, I encountered a console error when selecting a user from the autocomplete form and saving the configuration for the first time. Despite the error, the configuration saves correctly on a subsequent attempt, and the auto login works as expected.

After investigating the issue, it appears that the problem is related to the ajaxCallback function in the form. By returning $form['container'] from the ajaxCallback function, we can resolve this issue. Here’s the updated function:

public function ajaxCallback(array &$form, FormStateInterface $form_state): array {
  return $form['container'];
}

This change ensures that the correct part of the form is returned, preventing the console error and allowing the form to work correctly on the first save attempt.

I am attaching a screencast to demonstrate the issue and moving this to NW.

Tested the enable/disable feature provided in @KevinVb's MR. It works well for me. We can now enable or disable this functionality for menus, terms, and media as needed. Moving this to RTBC. Thanks!

The error is not showing after attaching the patch from the MR of @abhishek_gupta, LGTM
Moving it to RTBC

Yes @debra-v, Iater I have noticed that warning of undefined $row variable, which was resolved after attaching the patch from the MR of @abhisek_gupta1.
Moving this to RTBC
Thanks!

I was going through the same issue, I think the redirection for path aliases is not working with this module, so i guess when you are trying to redirect from an aliased path, let assume from /a to /b it will not work but if try to add the redirect with the node ids like from /node/1 to /node/2 the redirection will heppen and your unpublished content can be redirected to a published content as per your requirement.
But if you want to add the redirections from alias to alias then you can try the patch given in comment number #142 → of this → issue.
I think this will resolve the problem you are facing now Please let us know whether it's working for you or not.
Thanks

Drupal version: 10.2.7
PHP version: 8.1.28
Installed the module version 2.0.2, but not able to reproduce the error on my local and the logging functionality is also working fine.

@aaron.ferris Yes, later I have gone through that issue too, Thanks.

On visiting the route /admin/group/groupmenu, previously it was showing a Argument count error due to not passing any argument to the parent constructor of GroupMenuSettingsForm.php, after after the patch from this MR the error was resolved, Moving this to RTBC
Thanks!

hi @aaron.ferris,
I have tested the MR from here the fatal errors relarted to "Type of Drupal\groupmenu\Controller\GroupMenuController" are not showing now one module installations and while performing group related task, but on /admin/group/groupmenu route it's showing a Argument count error, is related to this issue or we need to create a separate issue for this and solve there.
Thanks!

Faced this problem while using views_ajax_history in a view of D11 setup, applied the MR patch from here that resolved the problem by replacing the array call.
Moving this to RTBC.

Hello all,
I have applied the MR from here and followed the mentioned steps of this issue, now it's look like the problem is fixed now, moving is to RTBC. I am attaching the screencast also.

Hi @maintainers,
Any updates on this. Can this is fixed now?

uttam → created an issue.

Tested the patch from this MR, when the checkbox is set by default i.e false user will be able to change the username and when the checkbox set as true i.e checked the username can not be edited.

Was going through this same problem, the module wasn't working with path aliases for the redirection. The patch #142 → works for me.
Thanks @Rajab Natshah

Hello @cweiske,
I have tested your MR from here and it's looks fine, rendering the html webform html correctly, moving this to RTBC.
Thank you

Hello all,
Couldn't reproduce the error, no entity query error are showing after installing the module and creating new webform, I think it was fixed in later commits as mentioned by @Nigel.
Thank you.

Hello @dabley I have tested your patch as mentioned by you in the issue #3311345 and that works fine for me, updated the status of that issue.
Thank you

I have tested the patch https://git.drupalcode.org/project/term_merge/-/merge_requests/7.diff and it's look good for me. Beside the term name term id's are added with a link reference to that particular term which will surely provide better user experience to select term from the checkbox if those terms has similar kind of name.

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

Please review the Merge request.

This issue is in same state for last few months could anyone please changed the status and make this issue fixed(closed) if everything works well.

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

@maintainers Can this issue be closed(fixed) now ?
please check

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

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