- Issue created by @hamzadwaya
- Merge request !660Issue #3431852: When a Webform is loaded on a 404 page: [PHP 8.1] Deprecated... → (Open) created by hamzadwaya
- 🇯🇴Jordan hamzadwaya
hamzadwaya → changed the visibility of the branch 3537579-drushcommandssqlsanitizesanitizeplugininterface-not-found to hidden.
- 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
What version of Drush are you using? I think you are using an old version.
The merge request reverses a change made in 📌 Fix phpstan errors Active .
- 🇬🇧United Kingdom grzesag
I had the same error after upgrading webform to 6.c and running drush updb:
1. Drupal 10.5
2. drush version 12Fix for me:
1. upgrade drush to version 13with drush v13 drush updb worked for me
Hope it is useful
- 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
I think the solution is to use a newer version of Drush or an older version of Webform.
- 🇩🇪Germany hosterholz
This is a breaking change. If Webform is incompatbile with Drush 12, it should add the conflict property to composer.json to prevent the error.
{ "conflict": { "drush/drush": "<13.0" } }
- Merge request !662Issue #3537579: Drush\Commands\sql\sanitize\SanitizePluginInterface not found → (Open) created by hosterholz
- 🇬🇧United Kingdom MrDaleSmith
Hit this same issue and would agree that whilst Drupal 10 and Drush 12 are still supported, this is a breaking change and either needs reflecting as such in a new D11 only release or reverting in the 6.3 releases.
Update to Drush 13 does fix the issue, if that's something you can do.
- 🇬🇧United Kingdom MrDaleSmith
I'm knocking this back to Needs review as no approach has been agreed, or any confirmation that either patch fixes the issue. I think the test fails are unrelated but it might be worth looking into them as well.
- 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
It looks to me like declaring the conflict, as described in #12, is a good approach.