Adam
Those warnings about Nominatim should be fixed in all circumstances as of #143, which I committed today.
I'm okay with hiding these from the Page and Event content types for now, since they are, as you point out, not used.
I agree with you, @boulaffasae. I sort of doubt that these fields are causing enough clutter to be worth hiding.
Yeah, this would be a cool idea, with a link in the main menu! Tagging as a good first issue if anyone has the time.
The only reason I wanted to do this is because we don't have thorough test coverage of the current permissions, so we don't know if the content editors actually have...
Can you reproduce this with plain core? If so, this isn't in Starshot's scope...it doesn't look, on its face, like a bug in the prototype, but if you can't reproduce...
Interesting - thanks for the clear steps to reproduce! That's quite curious indeed.
> drush config:set system.theme admin claro -y @gitressa, question: did you run `drush then claro` (or otherwise install Claro at `/admin/appearance`) before this?
I think this is a bug and should be addressed as a bug. I think the prototype should use Gin, that's a good, strong opinion for us to have. If...
I'm not entirely certain the bug is in any of the recipes. It might be in core somewhere. Hard to say without me actually sitting down and tracing into this...