In #3816, we are working towards reducing confusion by clarifying terminology used in the labels of radios/checkboxes (i.e. "who is considered an administrator?"). I took a look at the help text that we are adding and it occurred to me that: - things already seem to revolve around existing permissions ("Administer user accounts", "Select method of canceling account") - the "who can register accounts?" setting already sounds like a permission - as it is, we need extensive help text in order to explain how things work - perhaps things would be clearer if we had separate permissions for each action(?)
So I would like to explore the idea of switching to injecting a permission matrix in that form instead (#3332), and introducing new permissions to handle these things.
mockup upcoming...
Recent comments
Thanks!! Easiest for me to just give permission for anon users to see the admin theme. That worked. It's just for this one page.
Link field in a Content Type is malformed for annonymous user- Permission issue?
It looks like the screenshot of what you show it should look like is the admin theme whereas what they see is the front end theme. By default, such users won't have permissions to see the...
Link field in a Content Type is malformed for annonymous user- Permission issue?
I've added a new recipe. The recipe has no PHP code. It has two module dependencies (one of those depends on another contrib module and both depend on core modules that are normally enabled)...
The Future of Configuration Recipes for Backdrop CMS