tools.view for the Tech Tools entry
This commit is contained in:
@@ -115,6 +115,14 @@ ADR-007 and ADR-002.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Tech Tools was invisible to anyone without an account**, even though every
|
||||
tool on the page is deliberately usable without one and Secure Send is the
|
||||
single write this product offers a guest. The nav item named no permission,
|
||||
because the plugin had none to name, so the sidebar filter dropped it. The
|
||||
plugin gained `tools.view`, and the item now names either that or
|
||||
`tools.secrets` - somebody granted only Secure Send still needs the entry
|
||||
that leads to it.
|
||||
|
||||
- **The sidebar offered pages the reader could not open, and hid ones they
|
||||
could.** A nav item is hidden from anybody who does not hold its permission,
|
||||
but only four items ever declared one - so the filter did nothing for the
|
||||
|
||||
@@ -67,6 +67,11 @@ class ToolsPlugin(BasePlugin):
|
||||
about revoking what a role does or does not hold.
|
||||
"""
|
||||
return [
|
||||
# Reaching the tools page at all. The tools themselves run in the
|
||||
# browser and touch no data, so this is about whether the entry
|
||||
# appears - which is exactly the question a site answers when it
|
||||
# decides whether people without an account may use them.
|
||||
('tools.view', 'Use the browser tools (codes, conversions)', 'tools'),
|
||||
('tools.secrets', 'Create secure send links', 'tools'),
|
||||
]
|
||||
|
||||
@@ -135,6 +140,9 @@ class ToolsPlugin(BasePlugin):
|
||||
'route': '/tools',
|
||||
'position': 47,
|
||||
'section': 'fleet',
|
||||
# Either right reaches the page: somebody granted only Secure
|
||||
# Send still needs the entry that leads to it.
|
||||
'permission': ['tools.view', 'tools.secrets'],
|
||||
},
|
||||
]
|
||||
|
||||
|
||||
Reference in New Issue
Block a user