- Issue created by @project update bot
- last update
9 months ago 15 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-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
- last update
9 months ago 15 pass - last update
9 months ago 15 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
- last update
9 months ago 15 pass - last update
7 months ago 14 pass, 2 fail 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-188815These 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
- last update
7 months ago 14 pass, 2 fail The last submitted patch, 5: google_analytics.4.x-dev.rector.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- First commit to issue fork.
- last update
6 months ago 15 pass - First commit to issue fork.
- last update
6 months ago 10 pass, 4 fail - First commit to issue fork.
- 🇮🇳India chandu7929 Pune
chandu7929 → changed the visibility of the branch project-update-bot-only to hidden.
- Assigned to chandu7929
- Issue was unassigned.
- Status changed to Needs review
5 months ago 9:55am 29 July 2024 - 🇮🇳India rajeshreeputra Pune
Apart from tthis test failure, the changes look good.
Just as an FYI, this Google Analytics module is obsolete in favor of Google Tag, and it will not receive further releases from the maintainer.
- Status changed to RTBC
5 months ago 11:35am 4 August 2024 - 🇺🇸United States scott_earnest
Having trouble applying the MR, testing issue w/EOF on info.
- 🇺🇸United States scott_earnest
removed extra line EOF on the info file - this causes issues with the D.O. packing script and can lead to fail to apply patch. same MR should be all good thanks for the help!
josephgut → changed the visibility of the branch project-update-bot-only to active.
- 🇺🇦Ukraine ruslan piskarov Kyiv, Ukraine
+1 for an official release.
Thanks for working on this! - 🇸🇰Slovakia poker10
It would be great if we can get this committed and if a new D11 compatible release can be created. Thanks!
- 🇮🇳India manishvaity
MR!39 Makes this module compatible with Drupal 11. Functionality is working as expected.
RTBC +1
- 🇸🇰Slovakia poker10
google_tag module has a release compatible with D11, but this release has some issues. Therefore none of these two modules works correctly on D11. I have pinged @japerry on Slack (he is the maintainer of both modules).
- First commit to issue fork.
- 🇺🇸United States japerry KVUO
Made sure we still supported older versions of Drupal, especially since this module is EOL. Committed