Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 10.

To read more about this effort by the Drupal Association, please read: The project update bot is being refreshed to support Drupal 10 readiness of contributed projects

Periodically patches will be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches from being posted simply close this issue (any status besides Active, Needs review or Needs work) or remove the "ProjectUpdateBotD10" tag from the issue.

The patches will be posted by the Project Update Bot official user account. This account will not receive any issue credit contributions for itself or any company.

Proposed resolution

You have a few options for how to use this issue:

  1. Accept automated patches until this issue is closed

    If this issue is left open (status of Active, Needs review or Needs work) and the "ProjectUpdateBotD10" tag is left on this issue, new patches will be posted periodically if new deprecation fixes are needed.

    As the Drupal Rector project improves and is able to fix more deprecated API uses, the patches posted here will cover more of the deprecated API uses in the module.

  2. Leave open but stop new automated patches.

    If you want to use this issue as a starting point to remove deprecated API uses but don't want new automated patches simply leave this issue open but remove the "ProjectUpdateBotD10" tag from the issue.

    You can use Drupal Rector yourself to make these patches.

    If you want to receive automated patches again, add back the "ProjectUpdateBotD10" tag.

  3. Close it and don't use it

    If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review or Needs work) and no more automated patches will be posted here.

    If the issue is reopened, then new automated patches will be posted.

    If you are using another issue(s) to work on Drupal 10 compatibility it may be useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

  1. Apply the patch in the comment by Project Update Bot.
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.

Providing feedback

If there are problems with one of the patches posted by the Project Update Bot, such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue. For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Infrastructure project issue queue using the component “Bot: Drupal Rector”.

Issue fork google_tag-3287784

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Project Update Bot created an issue. See original summary.

project update bot’s picture

Status: Active » Needs review
StatusFileSize
new846 bytes

This is an automated patch generated by Drupal Rector. Please see the issue summary for more details.

It is important that any automated tests available are run with this patch and that you manually test this patch.

Drupal 10 Compatibility

According to the Upgrade Status module, even with this patch, this module is not yet compatible with Drupal 10.

Currently Drupal Rector, version 0.12.0, cannot fix all Drupal 10 compatibility problems.

This patch does not update the info.yml file for Drupal 10 compatibility.

Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.

Debug info

Bot run #127

This patch was created using these packages:

  1. mglaman/phpstan-drupal: 1.1.9
  2. palantirnet/drupal-rector: 0.12.0

Lal_ made their first commit to this issue’s fork.

Lal_’s picture

Issue summary: View changes
StatusFileSize
new21.01 KB
shamir.vs’s picture

Patched #5 applied successfully, and all issues were fixed.

shamir.vs’s picture

project update bot’s picture

This is an automated patch generated by Drupal Rector. Please see the issue summary for more details.

It is important that any automated tests available are run with this patch and that you manually test this patch.

Drupal 10 Compatibility

According to the Upgrade Status module this patch makes this module compatible with Drupal 10! 🎉
This patch updates the info.yml file for Drupal 10 compatibility.

Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.

Debug info

Bot run #139

This patch was created using these packages:

  1. mglaman/phpstan-drupal: 1.1.24
  2. palantirnet/drupal-rector: 0.13.0
dishakatariya’s picture

Assigned: Unassigned » dishakatariya
dishakatariya’s picture

Assigned: dishakatariya » Unassigned
StatusFileSize
new74.21 KB
new79.63 KB

Verified patch #8 on Drupal 10.0.x and 10.1.x. Patch applied successfully and looks good to me.
Module can be installed after applying the patch.
Screenshots are attached for reference:
Can be move to RTBC
RTBC+1

project update bot’s picture

StatusFileSize
new768 bytes
new1.67 KB

This is an automated patch generated by Drupal Rector. Please see the issue summary for more details.

It is important that any automated tests available are run with this patch and that you manually test this patch.

Drupal 10 Compatibility

According to the Upgrade Status module, even with this patch, this module is not yet compatible with Drupal 10.

Currently Drupal Rector, version 0.13.0, cannot fix all Drupal 10 compatibility problems.

This patch does not update the info.yml file for Drupal 10 compatibility.

Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.

Debug info

Bot run #143

This patch was created using these packages:

  1. mglaman/phpstan-drupal: 1.1.25
  2. palantirnet/drupal-rector: 0.13.0

nkoporec made their first commit to this issue’s fork.

nkoporec’s picture

Updated the PR and removed all the not needed changes per @mglaman suggestions, all the phpcs/phpstan issues should be handled separately in a new issue or even in multiple ones, so its easier to track changes.

mglaman’s picture

Status: Needs review » Reviewed & tested by the community

Thanks @nkoporec. Looks good. Moving to RTBC to prevent Update Bot from sending in new patches until this gets merged or asked for more changes.

jcnventura’s picture

Issue tags: -ProjectUpdateBotD10

Removing the ProjectUpdateBotD10 is the best way to prevent the update bot.

chris matthews’s picture

Ready to commit? Would be great to have a D10 compatible tagged release.

grevil’s picture

+1, D10 compatibility needed for automated testing in https://www.drupal.org/project/cookies! Would really appreciate this release! :)

grevil’s picture

I contacted the maintainer directly, let's wait for an answer!

anybody’s picture

@solotandem any updates?

vipin.mittal18’s picture

@solotandem: Would you be able to release a version that is compatible with D10?

chris matthews’s picture

It would be ideal if google_tag had a co-maintainer, but unfortunately the offer was not accepted. #3317621: Offering to co-maintain Google Tag Manager

kevinquillen’s picture

The patch looks pretty straightforward, what is the status on this?

vipin.mittal18’s picture

@solotandem This is awaiting your action.

kevinquillen’s picture

In order to update project(s) to Drupal 10 in lieu of a new release here, I had to do the following:

Add this as the first entry under 'repositories' in composer.json:

"repositories": [
        {
            "type": "package",
            "package": {
                "name": "drupal/google_tag",
                "type": "drupal-module",
                "version": "1.5",
                "dist": {
                    "url": "https://ftp.drupal.org/files/projects/google_tag-8.x-1.5.zip",
                    "type": "zip"
                },
                "require": {
                    "drupal/core": "^8.8 || ^9 || ^10"
                }
            }
        },

and still keep the patch:

            "drupal/google_tag": {
                "Drupal 10 compatibility": "https://www.drupal.org/files/issues/2022-07-23/google_tag.1.x-dev.rector.patch"
            },

Otherwise, Composer will refuse to download Drupal 10.

  • solotandem committed 4e322077 on 8.x-1.x
    Issue #3287784 Drupal 10 compatibility changes.
    
solotandem’s picture

Status: Reviewed & tested by the community » Active
Issue tags: +ProjectUpdateBotD10

Relevant changes included in commit in #25. Reopen and restore tag. Thanks to all.

anybody’s picture

Thanks @solotandem!

Is this fixed then? The bot won't provide further patches for D10, so we could close this.

solotandem’s picture

Status: Active » Fixed

Changing status as suggested in #27.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

merilainen’s picture

What about problems like
Call to deprecated function file_create_url(). Deprecated in drupal:9.3.0 and is removed from drupal:10.0.0. Use the appropriate method on \Drupal\Core\File\FileUrlGeneratorInterface instead.

solotandem’s picture

What code (core, this module) are you running that generated this 'problem'? The code in 8.x-1.6 release of this module checks for the 'file_url_generator' service available in drupal 10. if present it uses that, otherwise it calls file_create_url() which exists prior to 10. How can the 'problem' you mention exist if you are using compatible code?

merilainen’s picture

Yep, I didn't check the code, I just saw the problem reported by upgrade_status, sorry. This makes it harder to see which projects are actually ready for D10 because I need to manually go through each problem reported by upgrade_status and see if they are false negatives or real problems.