With the recent change of Room and Timeslot fields #1668908: Replace User reference, Nodereference with References, Vertical session schedule view, the field permission are now gone for these 2 fields. To be exact:
- Edit own value for field Room
- Edit own value for field Time slot
I'm suppose to continue on #1661620: Authenticated Users Cannot Create BoFs Regardless of Permission Settings but those 2 permissions are needed in order for an authenticated user to create a bof/session.
For sessions, these fields should be only available to session organizers while in bof, these should be available for authenticated users.
So, I'm not quite sure how to handle this. My options are:
- create a new permission for each field per node type
- keep session organizers to add/edit the rooms and timeslot because there is already a permission called "Schedule a BoF Session" and "Schedule a Session". But then the bof wouldn't be self managed by users
Thoughts?
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | room-and-timeslot-permi-1698454-10.patch | 3.93 KB | twardnw |
| #7 | perms_update_cod_session.png | 85.07 KB | sheldonkreger |
| #5 | room-and-timeslot-permi-1698454-5.patch | 9.57 KB | primerg |
| #4 | room-and-timeslot-permi-1698454-4.patch | 9.58 KB | primerg |
Comments
Comment #1
primerg commentedtagging
Comment #2
twardnw commentedBoFs do not need to be moderated like sessions, set up the permissions for Authenticated users to be able to 'Create own value for field Room/Time slot'. We don't want them to be able to go back later and edit it.
Comment #3
twardnw commentedd'oh, my comment removed the tag
Comment #4
primerg commentedin this patch
- add field permission level for room and time slot
- assign appropriate permissions
- change the condition in creating sessions from "edit own field_x" to "create own field_"
Comment #5
primerg commentedthe permission "create own" is wrong. re-patch
Comment #6
saltednut#5 applies clean to the da_drupalcon sandbox and I'm seeing the permissions set on the field level that Authenticated users are able set 'Create own value' for field_session_room & field_session_slot
Comment #7
sheldonkreger commentedThis applies clean to the sandbox.
Field level permissions for field_session_slot and Room are listed on the permissions settings area. Authenticated users can create their own value and view other's values. See image below.
From left to right: Anon, Authenticated, Administrator, Conference Administrator, Session Organizer.
Comment #8
saltednutComment #9
ezra-g commentedThis still refers to a non-existent "conference administrator" role.
Comment #10
twardnw commentedHere is a patch that captures these permissions (and no conference admin)
Comment #11
twardnw commentedbah, status update
Comment #12
mrconnerton commentedI believe we are looking to pull permissions out of features and have them set either with defaultconfig or via the install profile / module enables.
Comment #13
mrconnerton commentedComment #14
mrconnerton commentedComment #15
japerryThis old issue is fixed.