- Issue created by @project update bot
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.19.2, cannot fix all Drupal 11 compatibility problems.
Therefore these changes did not update the
info.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-109123This patch was created using these packages:
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.19.2
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-127002These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - 🇳🇱Netherlands bbrala Netherlands
Sorry for the spam. Will be debugging a little in regards to the 0 byte file.
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore these changes did not update the
info.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-127002These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore these changes did not update the
info.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-127002These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-127002These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - Status changed to Closed: outdated
about 1 year ago 3:09pm 24 March 2024 - 🇳🇱Netherlands bbrala Netherlands
Clsoing as outdated wince this issue was spammed.
- Status changed to Needs review
about 1 year ago 3:11pm 24 March 2024 - Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-127002These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - First commit to issue fork.
-
larowlan →
committed 3a200f58 on 1.x authored by
Project Update Bot →
Issue #3425252: Automated Drupal 11 compatibility fixes for forum
-
larowlan →
committed 3a200f58 on 1.x authored by
Project Update Bot →
-
larowlan →
committed 3a200f58 on 2.x authored by
Project Update Bot →
Issue #3425252: Automated Drupal 11 compatibility fixes for forum
-
larowlan →
committed 3a200f58 on 2.x authored by
Project Update Bot →