web: fix outpost edit/delete buttons
This commit is contained in:
parent
42feb54d80
commit
1649c478b6
|
@ -52,13 +52,13 @@ export class OutpostListPage extends TablePage<Outpost> {
|
|||
})}</ul>`,
|
||||
html`<ak-outpost-health outpostId=${item.pk}></ak-outpost-health>`,
|
||||
html`
|
||||
<ak-modal-button href="${Outpost.adminUrl(`${item.pk}/update`)}">
|
||||
<ak-modal-button href="${Outpost.adminUrl(`${item.pk}/update/`)}">
|
||||
<ak-spinner-button slot="trigger" class="pf-m-secondary">
|
||||
${gettext("Edit")}
|
||||
</ak-spinner-button>
|
||||
<div slot="modal"></div>
|
||||
</ak-modal-button>
|
||||
<ak-modal-button href="${Outpost.adminUrl(`${item.pk}/delete`)}">
|
||||
<ak-modal-button href="${Outpost.adminUrl(`${item.pk}/delete/`)}">
|
||||
<ak-spinner-button slot="trigger" class="pf-m-danger">
|
||||
${gettext("Delete")}
|
||||
</ak-spinner-button>
|
||||
|
|
|
@ -21,15 +21,6 @@ title: Release 2021.1.2
|
|||
|
||||
- Add test view to debug property-mappings.
|
||||
|
||||
- Simplify role-based access
|
||||
|
||||
Instead of having to create a Group Membership policy for every group you want to use, you can now select a Group and even a User directly in a binding.
|
||||
|
||||
When a group is selected, the binding behaves the same as if a Group Membership policy exists.
|
||||
|
||||
When a user is selected, the binding checks the user of the request, and denies the request when the user doesn't match.
|
||||
|
||||
|
||||
## Fixes
|
||||
|
||||
- admin: add test view for property mappings
|
||||
|
|
14
website/docs/releases/next.md
Normal file
14
website/docs/releases/next.md
Normal file
|
@ -0,0 +1,14 @@
|
|||
---
|
||||
title: Next release
|
||||
---
|
||||
|
||||
## Headline Changes
|
||||
|
||||
- Simplify role-based access
|
||||
|
||||
Instead of having to create a Group Membership policy for every group you want to use, you can now select a Group and even a User directly in a binding.
|
||||
|
||||
When a group is selected, the binding behaves the same as if a Group Membership policy exists.
|
||||
|
||||
When a user is selected, the binding checks the user of the request, and denies the request when the user doesn't match.
|
||||
|
Reference in a new issue