Resolve "Manage permissions for persons (users) and groups (Django groups) in frontend" #2178
No reviewers
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-Core!2178
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "285-manage-permissions-for-persons-users-and-groups-django-groups-in-frontend"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #285
List view
Select modal
Assign permission form
added 4 commits
masteraf90190f- Add support for managing permissions in the frontendCompare with previous version
assigned to @fph and unassigned @hansegucker
assigned to @nik and unassigned @fph
requested review from @ZugBahnHof
added 94 commits
master930f3723- Merge branch 'master' into...Compare with previous version
added 3 commits
master034b17dd- Merge branch 'master' into...Compare with previous version
added 1 commit
78920a4b- Refactor modal for assigning permissions to card to avoid JS issuesCompare with previous version
added 1 commit
a7a1f720- Fix typoCompare with previous version
added 1 commit
f4ac489e- Remove deprecated mechanism for getting count of newly created permissionsCompare with previous version
added 73 commits
masterf0e29a55- Merge branch 'master' into...Compare with previous version
added 1 commit
178df480- Add views to delete permissionsCompare with previous version
marked this merge request as ready
Does this / should this include the possibility for persons to add object permissions on themselves / groups they own?
No, it doesn't and adding this function makes things much more complicate.
I have two questions:
Please make sure the user will know, this is a form to filter, which is purely optional. You could maybe even hide and toggle it using JS, but at least a subheading like e.g. "Filter results" would be nice.
I'm not sure whether this is a permission for something, or rather a permission to do something or even a permission on a certain topic.
Examples:
added 11 commits
master915790ff- Merge branch 'master' into...Compare with previous version
There are multiple reasons. For example, after submitting the permission assignment form one should be redirected automatically to the matching table. Then, additionally, it makes things much more complex to include four different models and filter forms in one view.
To build the assignment form and show the correct entries for the objects list, we must know the content type/model before we render the form.
Ok, in this case, it is a permission on something.
resolved all threads
changed this line in version 10 of the diff
added 1 commit
17189375- Improve layout of permission management viewsCompare with previous version
@ZugBahnHof Please fix the frontend.
I see no reaction to this request.
I somehow remeber we used to translate our strings…
Please split the strings so translation will stay in sync.
What is
target="_self"suppoed to do? Thetargetattribute is forbidden, and_selfis the default anyway…Don't do that.
There should always be exactly one way of doing things, and doing text search is done using haystack in AlekSIS.
(You will remember that we already got a long-standing security issue with haystack, we don't need a second mechanism with the same security issue)
Materialize can be ugly sometimes: https://materializecss.com/tabs.html#external
We also make use of
django-filterfor filtering tables and that is the supposed use case.@ZugBahnHof Any progress on this?
marked this merge request as draft
added 675 commits
master36388114- Merge branch 'master' into...Compare with previous version
@nik Any response?
https://django-haystack.readthedocs.io/en/master/multiple_index.html
changed this line in version 12 of the diff
changed this line in version 12 of the diff
changed this line in version 12 of the diff
added 45 commits
masterf8d5017c- Simplify and rename get_search_fields to get_filter_fieldseef8c0bf- Merge branch 'master' into...f4a2e38f- Update changelogc25ade6b- Add missing trans taga38f53b5- ReformatCompare with previous version
marked this merge request as ready
resolved all threads
removed review request for @ZugBahnHof
resolved all threads
mentioned in commit
02f693133c