- Issue created by @Project Update Bot
- Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
3 months 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.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, 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-120024This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
3 months ago Waiting for branch to pass - Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
3 months ago Waiting for branch to pass This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.
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-137198These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.10
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
3 months ago Waiting for branch to pass - Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
26 days 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.2, 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-188138These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.2
- Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
26 days 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.3, 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-199781These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- π΅πΉPortugal jcnventura
jcnventura β changed the visibility of the branch 3428283-automated-drupal-11 to hidden.
- π΅πΉPortugal jcnventura
jcnventura β changed the visibility of the branch 3428283-automated-drupal-11 to hidden.
- Status changed to Postponed
4 days ago 10:47pm 23 June 2024 - π΅πΉPortugal jcnventura
This makes the theme work under Drupal 11, but then comes the next problem:
Error: Bootstrap's JavaScript requires jQuery version 1.9.1 or higher, but lower than version 4
Drupal 11 has upgraded jQuery to 4.0.0-beta, and Bootstrap 3 doesn't support this version. This is effectively the end-of-line for Bootstrap 3, and if this theme doesn't find a way to support Bootstrap 5, then it is else the end-of-line for the theme.
- πΊπΈUnited States shelane
This theme is not going to support Bootstrap 5. There are other themes that do.
- π΅πΉPortugal jcnventura
Understood, and totally respect your decision. Everyone has now 2 years to migrate away from this theme, as it will be EoL at the same time as Drupal 10.
Any tips on which of the existing Bootstrap 5 themes is the easiest to upgrade to?
- πΊπΈUnited States shelane
Other themes are listed on the project page. We are currently working on getting our theme updated to use Radix as a base theme. Version 6 makes use of core SDC, which really works for us.