I'm calling this a bug, but it might be a feature :). It also seems to have a lot to do with the audio module.
The situation: I have disallowed anonymous users from accessing any content nodes. I then log in as a registered user and start to stream an mp3 via a m3u playlist. However, the mp3 file cannot be accessed by my mp3 player due to insufficient permissions.
Is there an easy way to simultaneously let registered users stream mp3's to their desktop while disallowing anonymous users from viewing any audio nodes? I hope this is not an issue with my setup.
--Neil
Note: I've fixed the problem with streaming mp3 playlists using firefox (see my other issue). Hooray!
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | playlist.module_permissions.patch | 2.83 KB | zirafa |
Comments
Comment #1
ohzbees commentedWhat if there were more "access control" options associated with both the audio and playlist modules. Ror example, letting users: (1) CREATE audio and/or playlists, or (2) VIEW/DOWNLOAD/STREAM audio and playlist nodes, or (3) EDIT THEIR OWN audio nodes and playlists, or (4) ADMINISTER all audio and playlists, etc.
Comment #2
zirafa commentedexcellent suggestion....currently there is only create/edit playlists/audio.
you suggest:
1) edit/create own playlists (same as it is)
2) view playlists
3) administer playlists (means that person can edit all of them)
so if we add 2 that would open up the flexibility as you describe. but number 3 is a bit of a special case. can you describe a use case for number 3?
Comment #3
ohzbees commentedI guess you might want to let a special user (who is not the site administrator) edit any given playlist or audio node but not necessarily have free access to edit all instances of other node types, e.g., they would fulfill the "audio editor" role.
Comment #4
zirafa commentedOk, here is a patch that implements the proposed changes. Should work. And actually fixes a problem previously where users were able to manage other users playlists if they had 'create' access. it now checks to make sure they can only manage their own (unless they have 'administer playlists' permission).
Colin please double check the menu hook access check for 'manage playlist files' tab. i had to load the node object to be validated against because it wasn't working otherwise.
Comment #5
zirafa commentedpatch committed. colin if you see/encounter problems, please submit a patch.