- Issue created by @Anybody
- 🇩🇪Germany Anybody Porta Westfalica
Found it:
Type of Drupal\posthog_js\Form\SettingsForm::$typedConfigManager must not be defined (as in class Drupal\Core\Form\ConfigFormBase) in /web/modules/contrib/posthog/modules/posthog_js/src/Form/SettingsForm.php on line 20
- 🇩🇪Germany Anybody Porta Westfalica
@grevil: Important, this is a risky and ugly thing... See 🐛 Fatal error: Type of Drupal\geocoder\Form\SettingsForm::$typedConfigManager must not be defined (as in class Drupal\Core\Form\ConfigFormBase) Fixed for details.
- Merge request !2Update SettingsForm.php: Untype TypedConfigManagerInterface for now → (Merged) created by Anybody
- 🇩🇪Germany Grevil
This fix caused a regression for Drupal 11. We should make separate
releases for D10 and D11:PHP Fatal error: Type of Drupal\posthog_js\Form\SettingsForm::$typedConfigManager must be Drupal\Core\Config\TypedConfigManagerInterface (as in class Drupal\Core\Form\ConfigFormBase) in /var/www/html/web/modules/custom/posthog/modules/posthog_js/src/Form/SettingsForm.php on line 0
- 🇩🇪Germany Anybody Porta Westfalica
@grevil No I think there's a pattern to solve this. Look into similar widely used modules, they surely had the same issue.
Separate releases are no good solution for such a specific issue. - 🇩🇪Germany Grevil
I think I found something. The fix will be introduced through 📌 Implement SDK base integration Active .