File access rights in File Entity (fieldable files) 7.3
Same name and namespace in other branches
- 7.2 file_entity.module \file_entity_access
The file access system determines who can do what to which files.
In determining access rights for a file, file_entity_access() first checks whether the user has the "bypass file access" permission. Such users have unrestricted access to all files. user 1 will always pass this check.
Next, all implementations of hook_file_entity_access() will be called. Each implementation may explicitly allow, explicitly deny, or ignore the access request. If at least one module says to deny the request, it will be rejected. If no modules deny the request and at least one says to allow it, the request will be permitted.
There is no access grant system for files.
In file listings, the process above is followed except that hook_file_entity_access() is not called on each file for performance reasons and for proper functioning of the pager system. When adding a filelisting to your module, be sure to use a dynamic query created by db_select() and add a tag of "file_entity_access". This will allow modules dealing with file access to ensure only files to which the user has access are retrieved, through the use of hook_query_TAG_alter().
Note: Even a single module returning FILE_ENTITY_ACCESS_DENY from hook_file_entity_access() will block access to the file. Therefore, implementers should take care to not deny access unless they really intend to. Unless a module wishes to actively deny access it should return FILE_ENTITY_ACCESS_IGNORE (or simply return nothing) to allow other modules to control access.
Stream wrappers that are considered private should implement a 'private' flag equal to TRUE in hook_stream_wrappers().
File
- ./
file_entity.module, line 1698 - Extends Drupal file entities to be fieldable and viewable.
