Fatal error: Type of Drupal\geocoder\Form\SettingsForm::$typedConfigManager

Created on 23 November 2023, 10 months ago
Updated 24 November 2023, 10 months ago

With Drupal 10.2.x I can see following error
Fatal error: Type of Drupal\geocoder\Form\SettingsForm::$typedConfigManager must be ?Drupal\Core\Config\TypedConfigManagerInterface (as in class Drupal\Core\Form\ConfigFormBase) in docroot/modules/contrib/geocoder/src/Form/SettingsForm.php on line 14

Steps to reproduce:

  • Create new project using composer create-project drupal/recommended-project:10.2.0-beta1@beta geocoder-3403728&& cd geocoder-3403728
  • Require drush using composer require drush/drush
  • Require geocoder using composer require drupal/geocoder geocoder-php/google-maps-provider
  • Install site using ./vendor/bin/drush si minimal
  • Install geocoder using ./vendor/bin/drush in geocoder -y
  • Welcome the above error
💬 Support request
Status

Closed: duplicate

Version

4.10

Component

Code

Created by

🇮🇳India chandu7929 Pune

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

Comments & Activities

  • Issue created by @chandu7929
  • Status changed to Closed: cannot reproduce 10 months ago
  • 🇮🇹Italy itamair

    Ahhrrghh ... openly speaking this is a kind of those issue that I really don't like to look at, comment and care of, in general,
    as it shows so much lack of commitment from the author in contribution to the project itself, even professionalism.

    Bugs tasks cannot be opened and dropped here just copy-pasting the error you experience, and on such a basic functionality of a module that is registering thousands of adoptions, and no body there already reporting any blocker issue like this one ...

    A Bug Task needs to be documented to be reported as such, with appropriate details on how to reproduce it, some specific info in the specific use case, even some screenshots from the own dev environment outcome.

    Nothing of that instead in this opened issue, that I would rather mark as Support Request, of something that is not clearly reproducble.

    Every makes me think here that you didn't probably used:
    - composer to require / install the geocoder module
    - composer to require the specific geocoder provider that you want to set up and use with the module

    Please review you local dev setup and approach, and make sure you are properly matching the Geocoder instructions on how to properly require, enable and use it, with its geocoder/providers (https://git.drupalcode.org/project/geocoder/-/blob/8.x-4.x/README.md?ref...)

    And reopen this, and mark this as a Bug ONLY if you indeed find a general use case for your bug, that affects the module itself, and very other user on it (you indeed look would be the first), and please document it appropriately, otherwise I indeed doubt anybody will spend some time on this, rather then you.

  • 🇮🇳India rajeshreeputra Pune

    Added steps to reproduce the issue with Drupal 10.2.0-beta1.

  • Status changed to Active 10 months ago
  • Status changed to Closed: duplicate 10 months ago
Production build 0.71.5 2024