Fatal error in config page

Created on 24 October 2024, 22 days ago

Problem/Motivation

I confirmed your recent patch worked and 1.0.4 was working fine, but than I downloaded v.1.0.5 and am getting this error.

Fatal error: Cannot use Drupal\Core\Config\TypedConfigManagerInterface as TypedConfigManagerInterface because the name is already in use in /app/web/modules/contrib/codit_batch_operations/src/Form/CoditBatchOperationsConfigForm.php on line 13

Steps to reproduce

Just update and load the config page.

πŸ› Bug report
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States cdesautels

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

Comments & Activities

  • Issue created by @cdesautels
  • πŸ‡ΊπŸ‡ΈUnited States 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.

  • πŸ‡ΊπŸ‡ΈUnited States swirt Florida
Production build 0.71.5 2024