mirror of
https://github.com/opensolutions/ViMbAdmin.git
synced 2026-04-26 00:36:00 +03:00
[GH-ISSUE #252] access_restriction is too short #204
Labels
No labels
bug
feature
feature
improvement
improvement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ViMbAdmin-opensolutions#204
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @andyboeh on GitHub (Aug 30, 2018).
Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/252
I use the Access Restriction plugin a lot and ran out of space for the access_restriction field. For now, I manually changed the database, but IMHO it would make sense, to increase the column length from 100 to a higher number (I use 512 for now).
Further, if you run out of space for the access_restriction field, you do not get any warning. Setting the permission simply doesn't stick.
@barryo commented on GitHub (Aug 31, 2018):
Hi @andyboeh - 100 is a lot. Are you using stuff outside the standard:
@andyboeh commented on GitHub (Aug 31, 2018):
Yes, I have about 20 different permissions defined as I built our entire authentication and authorization system around ViMbAdmin's database. I understand that that's not the primary intention of ViMbAdmin, so I'm fine with a custom solution as well.
@barryo commented on GitHub (Aug 31, 2018):
Thanks @andyboeh - I think the customer work around is best here 😉