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:
- 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.
- 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.
- 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
- Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
- Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
- 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.
Issue fork sfweb2lead_webform-3289580
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
Comment #2
Project Update Bot CreditAttribution: Project Update Bot commentedThis 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
This patch was created using these packages:
Comment #3
Project Update Bot CreditAttribution: Project Update Bot commentedThis 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
This patch was created using these packages:
Comment #4
BramDriesenLast patch seems ok. After commit please put the issue back to active to keep getting updates from the update bot.
Comment #5
Project Update Bot CreditAttribution: Project Update Bot commentedUpdating bot issue summary.See #3313904: Update project bot templates for RTBC status support and human interaction tips
Comment #7
renukakulkarni CreditAttribution: renukakulkarni as a volunteer commentedRe-rolled the patch to work with 8.5.2 until the 10 compatible release of the module is out.
Comment #8
renukakulkarni CreditAttribution: renukakulkarni as a volunteer commentedUpdated patch for 8.5.2.
Comment #9
prajeeshc CreditAttribution: prajeeshc commentedHello @maintainers:
The patch provided for D10 compatibility is working. When can we expect this update to be released ?
Thanks.
Comment #10
carstenG CreditAttribution: carstenG at FFW commentedI had to do a small fix...
from:
to:
Comment #12
bapi_22 CreditAttribution: bapi_22 as a volunteer and at Globant for Globant commented#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...
Comment #13
bapi_22 CreditAttribution: bapi_22 as a volunteer and at Globant for Globant commentedI think, from the latest version of sfweb2lead_webform every thing is working fine. only we need to take care 2 things:
Here is a new fresh patch for the same.
Comment #14
java008 CreditAttribution: java008 as a volunteer and at Material for Drupal India Association commentedUpdating the patch for D10 compatible
Comment #15
Yury N CreditAttribution: Yury N as a volunteer commentedComment #16
Yury N CreditAttribution: Yury N as a volunteer commentedHad to update patch because of https://www.drupal.org/project/drupal/issues/3036459
Comment #17
irodriguez CreditAttribution: irodriguez commentedIs there going to be a Drupal 10 version of this module?
Comment #18
BramDriesenI guess someone could offer to co-maintain. :-)
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...
Comment #19
Parvateesam CreditAttribution: Parvateesam commentedHello @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?
Thanks.
Comment #20
andikanio CreditAttribution: andikanio as a volunteer commentedFor anyone struggling,
I know this is not the best practice but you can also do this.
Comment #21
milos33 CreditAttribution: milos33 commentedHello 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?
Comment #22
Parvateesam CreditAttribution: Parvateesam commentedHello 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.
Comment #23
markdorison@milos33 I am on the lookout for any reports of incompatibility, but I have not seen any.
@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.
Comment #25
markdorisonThe 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!
Comment #26
Parvateesam CreditAttribution: Parvateesam commentedHi @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.
Thanks
Comment #27
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.
Comment #28
BramDriesenIt will only work when using the D10 lenient stuff indeed.
Comment #29
heddnThis looks good to go. LGTM.
Comment #31
markdorisonComment #33
markdorison