Using an older version of DEV release to avoid problems with sorting, but now I find I have another issue. Authenticated users are given permission to edit/delete any File Browser node on the admin permissions setting page, but they are still unable to edit. They are able to upload files, download archives, and such, just unable to edit or delete.
I am not using any other node access control modules, but I do have content permissions enabled (part of CCK), though I don't see that this has any relation with a custom content type such as that provided by Filebrowser, and disabling it temporarily has no effect on this issue. The input format filter for the folder description is one that is available to authenticated users, so that isn't causing the conflict either.
Can anyone else replicate this and confirm? I have tried disabling and re-enabling the module, as well as running updates, and I have too much existing content to risk completely uninstalling and starting over.
Comments
Comment #1
HippoOnDiet commentedHi Glottus,
I am using the Old RC11 with Taxonomy Access Control on my site as well and I am having the same issue as yours.
I have ticked all (create, edit, delete and download access) from the permission for private group, but still if I login as Tom - a member of private group - I can't create, edit node or delete the node.
What I found out that when I changed that node author to Tom, then he can see the edit button but no delete button at the bottom.
But then I tried to remove edit any and delete any... TOM can't see the edit button - so it's depend on edit any permission instead of edit own directory permission.
Just to check with you, in your permission can you see Content Type Directory Listing? As I can only see page, story and other stuffs.
If I can get this to show up then Tom will be able to create content, by using node permission.
Otherwise only admin can created, modify and delete the node.
Comment #2
Yoran commentedCan you give a try with the last dev version in order to be sure this is still an active bug ?
Comment #3
HippoOnDiet commentedHi Yoran,
I have tried the new dev and I am still experiencing with access issue.
I am using Taxonomy Access Control and Core-User Permission.
Scenario:
I have created a new content and updated the author name to one of user.
I have uploaded some files.
User have uploaded some files.
Basically I have given user access permission to:
create directory listings
delete any directory listings
delete files
delete own directory listings
download archive files
download files
edit any directory listings
edit own directory listings
upload files
view directory listings
But the user can't do this things:
User can't see Create a new directory listing under create content
User can't delete the file - access is denied.
User can't delete the directory (no option)
What user can do:
User can download
User can see file listing
User can upload file
Thanks again :)
Comment #4
kvoltz commentedI am having this same issue.
Everything works as expected with the top level user, however I cannot delete files when assigning these abilities to a given role.
Has any progress been made on this?
Comment #5
kvoltz commentedBump.
Comment #6
Yoran commentedComment #7
Nicolas Georget commentedMaybe it comes from this: #1188858: Create dir_list and Permissions
Try to grant the permission "administer nodes" to the user roles.
Comment #8
Yoran commentedNormally fixed, please check.