- Issue created by @project update bot
This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- First commit to issue fork.
Applying this patch causes this issue:
Fatal error: Type of Drupal\inactive_autologout\Form\SettingsForm::$typedConfigManager must not be defined (as in class Drupal\Core\Form\ConfigFormBase) in /var/www/html/web/modules/contrib/inactive_autologout/src/Form/SettingsForm.php on line 15
- 🇺🇦Ukraine abramm Lutsk
I can confirm the issue with the latest state of the 3431055-Drupal-11-Support branch. The $typedConfigManager property of the class shouldn't be overridden or set as it's already defined and set in the parent ConfigFormBase class constructor.
D10: https://git.drupalcode.org/project/drupal/-/blob/10.4.x/core/lib/Drupal/...
D11: https://git.drupalcode.org/project/drupal/-/blob/11.x/core/lib/Drupal/Co... - 🇺🇦Ukraine abramm Lutsk
Pushed the fix to the 3431055-Drupal-11-Support branch (MR !10). I can confirm the settings form works as expected now.
Attaching a patch to ease applying via Composer.