- Issue created by @cdesautels
- πΊπΈUnited States swirt Florida
Thanks for reporting this. Taking a look.
- πΊπΈUnited States swirt Florida
I am not seeing this on simplytest.me running Drupal 11.4 and release 1.0.5.
Is it possible you are applying the patch to 1.0.5 which might cause that use to be duplicated?
- πΊπΈUnited States swirt Florida
@cdesautels I confirmed that the error you are seeing does not seem to match the current code for 1.0.5
As you can see, line 13 of src/Form/CoditBatchOperationsConfigForm.php does not reference TypedConfigManagerInterface
https://git.drupalcode.org/project/codit_batch_operations/-/blob/1.0.x/s...This encourages me to think that your code is in some odd partially patched state.
- πΊπΈUnited States cdesautels
"Is it possible you are applying the patch to 1.0.5 which might cause that use to be duplicated?"
I don't think so, I manage this all with Composer and cweagans/composer-patches. When I installed v.1.0.5, Composer installed it without a hitch AND reported that the patch could NOT be applied.
I could try try removing the patch and doing this again but I don't think it'll make a difference. Composer did not report any errors. Just that the patch couldn't be applied. Which is what it's supposed to do.
- πΊπΈUnited States swirt Florida
I'd remove the patch and update to 1.0.6
- πΊπΈUnited States swirt Florida
I think for clarity on this, If the patch has a few hunks and and the first one applies, but the second fails, composer will alarm that the patch failed to apply, but it does not roll-back any hunks that did apply.
- πΊπΈUnited States cdesautels
I uninstalled 1.0.4, deleted the patch and installed 1.0.6. The config page now loads with out errror.
Thanks.