- 🇵🇹Portugal joum Porto
Can confirm the patch on #1 works correctly using Drupal Core version 9.5.2 and this module's version 5.1.0.
When the module is first installed and there's no configuration available, a _lot_ of warnings are throw for each field access hook call. If, for example, a content type's entity form has any Ajax calls (for instance, autocomplete entity reference widgets) those don't work anymore because of the warnings reaching the Ajax response as well), so this is rather critical.
The patch correctly introduces simple sanity checks when loading the module's configuration objects to check if those actually exist before proceeding to make changes.
Changed priority to critical and moved the status to RTBC.