Automated Drupal 10 compatibility fixes

Created on 16 June 2022, over 2 years ago
Updated 21 March 2024, 10 months ago

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

Patches will periodically be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD10" tag from the issue to stop the bot from posting updates.

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, Needs work or Reviewed and tested by the community) 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.

    Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot patches. The bot will still post new patches then if there is a change in the new generated patch compared to the patch that the bot posted last. Those changes are then up to humans to integrate.

  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 then don't want new automated patches, remove the "ProjectUpdateBotD10" tag from the issue and use it like any other issue (the status does not matter then). 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, Needs work and Reviewed and tested by the community) 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 would be very useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

  1. Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.

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 Project analysis issue queue .

📌 Task
Status

Fixed

Version

6.0

Component

Code

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • First commit to issue fork.
  • 🇮🇳India renukakulkarni

    Re-rolled the patch to work with 8.5.2 until the 10 compatible release of the module is out.

  • 🇺🇸United States prajeeshc New Jersey

    Hello @maintainers:

    The patch provided for D10 compatibility is working. When can we expect this update to be released ?

    Thanks.

  • Status changed to Needs review over 1 year ago
  • 🇩🇪Germany carstenG

    I had to do a small fix...

    from:

    $implements = \Drupal::moduleHandler()->getImplementations('sfweb2lead_webform_posted_data_alter');
    

    to:

    $implements = \Drupal::moduleHandler()->hasImplementations('sfweb2lead_webform_posted_data_alter');
    
  • First commit to issue fork.
  • 🇮🇳India bapi_22

    #10 doesn't apply the patch correctly. Getting below error:

    Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/2023-05-15/sfweb2lead_webform-drupal...

  • 🇮🇳India bapi_22

    I think, from the latest version of sfweb2lead_webform every thing is working fine. only we need to take care 2 things:

    1. D10 compatibility
    2. Replace Symfony\Component\EventDispatcher\Event with Symfony\Contracts\EventDispatcher\Event

    Here is a new fresh patch for the same.

  • Updating the patch for D10 compatible

  • 🇧🇾Belarus Yury N

    Had to update patch because of https://www.drupal.org/project/drupal/issues/3036459 🐛 Packaging info from .info.yml often creates conflicts when patching Active

  • 🇺🇸United States irodriguez

    Is there going to be a Drupal 10 version of this module?

  • 🇧🇪Belgium BramDriesen Belgium 🇧🇪
  • 🇮🇳India Parvateesam

    Hello @maintainers:

    Thanks for the patch, the patch provided for D10 compatibility is applied but while trying to upgrade Drupal core from 9.5.11 to 10.1.4 facing below problem. So is there any clue to move forward. Also is there any update to be released D10 compatibility?

      Problem 1
        - drupal/sfweb2lead_webform[dev-5.x, 5.2.0] require drupal/core ^8 || ^9 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev] but it conflicts with your root composer.json require (10.1.4).
        - drupal/sfweb2lead_webform 5.x-dev is an alias of drupal/sfweb2lead_webform dev-5.x and thus requires it to be installed too.
        - Root composer.json requires drupal/sfweb2lead_webform ^5.2 -> satisfiable by drupal/sfweb2lead_webform[5.2.0, 5.x-dev (alias of dev-5.x)].

    Thanks.

  • For anyone struggling,
    I know this is not the best practice but you can also do this.

    {
        ...
        "require": {
            ...
            "drupal/sfweb2lead_webform": "dev-3289580-automated-drupal-10",
            ...
        },
        "repositories": {
            ...
            "sfweb2lead_webform": {
                "type": "vcs",
                "url": "https://git.drupalcode.org/issue/sfweb2lead_webform-3289580.git"
            },
            ...
        },
        ...
    }
  • 🇷🇸Serbia milos33

    Hello maintainers,

    I have one question, since Webform 6.2.0-rc1 version supports Drupal 10 is Salesforce Web-to-Lead Webform Data Integration compatible with this version of Webform?

  • 🇮🇳India Parvateesam

    Hello maintainers,

    Drupal 9 EOL is 1 November 2023, so is there any tentaive date to release D10 compatiable version of Web-to-Lead Webform Data Integration module? However above patches are not working for me to make it done D10 upgrade. Could you please have a look.

    Thanks in Advance.

  • Status changed to Needs work about 1 year ago
  • 🇺🇸United States markdorison

    I have one question, since Webform 6.2.0-rc1 version supports Drupal 10 is Salesforce Web-to-Lead Webform Data Integration compatible with this version of Webform?

    @milos33 I am on the lookout for any reports of incompatibility, but I have not seen any.

    Drupal 9 EOL is 1 November 2023, so is there any tentaive date to release D10 compatiable version of Web-to-Lead Webform Data Integration module? However above patches are not working for me to make it done D10 upgrade. Could you please have a look.

    @Parvateesam Marking this issue as "needs work" based on your testing. I am eager to get a D10-compatible patch (or even better, a merge request) committed and a release cut, but that depends on folks submitting and testing those changes.

  • @markdorison opened merge request.
  • Status changed to Needs review about 1 year ago
  • 🇺🇸United States markdorison

    The latest patch was no longer applying cleanly. I re-rolled that into an MR that is now building successfully on Tugboat so it is at least installing as expected. Please test MR5 and provide feedback or fixes there!

  • 🇮🇳India Parvateesam

    Hi @markdorison thanks for quick workaround, please find my comments below.

    Step 1: I checked out MR5 in my local and tested, now it's D10 compatible w.r.t upgrade status module, screenshot attached for the same.
    Step 2: After that I'm trying to upgrade drupal core from 9.5.11 to 10.1.5 but getting below error while running "composer update -W" please help to have a look into.

     composer update -W
    Gathering patches for root package.
    > DrupalProject\composer\ScriptHandler::checkComposerVersion
    Loading composer repositories with package information
    Updating dependencies
    Your requirements could not be resolved to an installable set of packages.
    
      Problem 1
        - drupal/sfweb2lead_webform[dev-5.x, 5.2.0] require drupal/core ^8 || ^9 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev] but it conflicts with your root composer.json require (10.1.5).
        - drupal/sfweb2lead_webform 5.x-dev is an alias of drupal/sfweb2lead_webform dev-5.x and thus requires it to be installed too.
        - Root composer.json requires drupal/sfweb2lead_webform ^5.2 -> satisfiable by drupal/sfweb2lead_webform[5.2.0, 5.x-dev (alias of dev-5.x)].
    

    Thanks

  • 🇺🇸United States markdorison

    @Parvateesam Thanks for testing! I don't believe running the update via Composer will work until this is committed and a release is tagged.

  • 🇧🇪Belgium BramDriesen Belgium 🇧🇪

    It will only work when using the D10 lenient stuff indeed.

  • Status changed to RTBC about 1 year ago
  • heddn Nicaragua

    This looks good to go. LGTM.

  • Status changed to Fixed about 1 year ago
    • markdorison committed 4a5b1c6f on 8.x-5.x
      Revert "Issue #3289580 by Yury N: Automated Drupal 10 compatibility...
  • Automatically closed - issue fixed for 2 weeks with no activity.

  • First commit to issue fork.
Production build 0.71.5 2024