- Issue created by @catapipper
- last update
over 1 year ago 67 pass, 1 fail - @catapipper opened merge request.
Ignore this. It turned out to be related to a missing configuration in CAPTCHA 2.0 which we were updating manually, which got caught in the Features page due to it searching for that particular configuration which was missing.
- Status changed to Closed: cannot reproduce
over 1 year ago 4:46pm 16 June 2023 - ๐จ๐ดColombia oneliner
Found this error, while the ticket is closed because OP took the Blame, this event and error happened to me.
I fixed it by adding an check in the Loop of contributed feature manager class method initConfigCollection
line 2040
if(!$data){ \Drupal::messenger()->addError($this->t('Configuration item @name could not be read from storage.', ['@name' => $name])); continue; }
This will let the features page load and point you to the corrupted configuration.