- Issue created by @heddn
- Status changed to Postponed: needs info
over 1 year ago 9:23pm 15 August 2023 - 🇺🇸United States jrockowitz Brooklyn, NY
LOL, @Heddn, I was about to immediately close this ticket because I think having individual tickets for deprecations that will most likely be fixed via automation is unnecessary. I am starting to see people looking for some commit credit from these types of one-off fixes. I know you are not looking for commit credit. Do you think a dedicated ticket is needed?
- heddn Nicaragua
I opened this because I wondered how you wanted to handle things. I personally prefer to incrementally keep up w/ deprecations so it isn't a huge rush at the end. I enabled tests on my client sites and they all surface these deprecations. So I either have to ignore them or open an issue so incrementally the site becomes less deprecated over time.
- 🇺🇸United States jrockowitz Brooklyn, NY
@heddn Since we are both aware that people are creating a lot of MRs to fix deprecated code for individual issues. How about we change this ticket and MR to address all Drupal 10.1 deprecating notices?
- Status changed to Active
over 1 year ago 2:24pm 21 August 2023 - heddn Nicaragua
The concern w/ making is a 10.1 grouped item, how do we know what parts of 10.1 are affected? I guess we can add a test run on 10.1 and see what complains. Works for me. Back to active waiting on a patch.
- 🇪🇨Ecuador afsch Otavalo
I've been doing a review of deprecated code by using the Upgrade Status module report. I got around 47 issues for Webform (beta6), here I'm leaving some fixes hoping this will be reviewed and tested. It remains 13 issues that need review.
- 🇺🇸United States jrockowitz Brooklyn, NY
@afsch I appreciate the patch, but I think it is doing too many undocumented changes.
I am pretty sure the below code will break CAPTCHA support.
- $element['#captcha_type'] = 'image_captcha/Image'; + $element['#captcha_type'] = '/image_captcha/Image';
- last update
over 1 year ago 513 pass, 37 fail - 🇺🇸United States jrockowitz Brooklyn, NY
What might help is exporting and attaching the report.
BTW, I haven't used the Upgrade Status module report in a while so I am not sure how the report is structured.
- 🇪🇨Ecuador afsch Otavalo
@jrockowitz you are right, most of the updated lines where libraries are being loaded are incorrect.
Anyway, I'm hiding the patch file for now and attaching the report generated by Upgrade Status. - Merge request !436Issue #3381257 by afsch: [Drupal 10.1] Deprecated code → (Merged) created by jrockowitz
- Status changed to RTBC
about 1 year ago 12:13pm 5 April 2024 - last update
about 1 year ago 536 pass - last update
about 1 year ago 536 pass - last update
about 1 year ago 536 pass -
jrockowitz →
committed d78c4258 on 6.2.x
Issue #3381257 by jrockowitz, afsch, heddn: [Drupal 10.1] Deprecated...
-
jrockowitz →
committed d78c4258 on 6.2.x
-
jrockowitz →
committed d78c4258 on 6.x
Issue #3381257 by jrockowitz, afsch, heddn: [Drupal 10.1] Deprecated...
-
jrockowitz →
committed d78c4258 on 6.x
- Status changed to Fixed
10 months ago 7:09pm 24 June 2024 -
Liam Morland →
committed c485d9c6 on 6.2.x
Issue #3381257: Require minimum of Drupal 10.1 in...
-
Liam Morland →
committed c485d9c6 on 6.2.x
-
Liam Morland →
committed c485d9c6 on 6.x
Issue #3381257: Require minimum of Drupal 10.1 in...
-
Liam Morland →
committed c485d9c6 on 6.x
- 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
This change necessitates setting a minimum of Drupal 10.1.
Automatically closed - issue fixed for 2 weeks with no activity.