also very interested in this so that I can upgrade to Drupal 11!
Just hit this after a site upgrade... not sure I understand all that's going on, but if an update to this module causes an error screen, it would seem that update should be rolled back.
Sounds important!
Patch seems to work for me!
You'd think that, instead of displaying this message to end users who cannot do anything about it, that a Rebuild Permissions would just be triggered, period. No?
Any word on official D10 support?
A bit confused, as I seem to be blocked from upgrading. How is this marked as compatible with D10 if I cannot effectively install it's dependencies using composer?
Actually it seems like this logic was previously in
bootstrap_barrio_preprocess_input() and if I move the code from bootstrap_barrio_preprocess() into it, the error goes away. I'd want a maintainer with an understanding of why this code was moved to let me know if that is a safe change to make, and maybe why it works in the former and not the newer function.
Thanks!
alienzed → created an issue.
My client was quite vexed by this, thinking their site was being spammed! I have to undo this change locally. Might I suggest that we should never under any circumstances send emails that we know for sure will fail? I imagine some hosting/email providers who block websites for doing this...
this feature would be amazing... kinda nuts that it doesn't already exist!