Bachir Soussi Chiadmi
f2b8ace9b7
FINAL suepr merge step : added all modules to this super repos
|
9 년 전 | |
|---|---|---|
| .. | ||
| images | 9 년 전 | |
| CHANGELOG.txt | 9 년 전 | |
| LICENSE.txt | 9 년 전 | |
| README.txt | 9 년 전 | |
| field_permissions.admin.css | 9 년 전 | |
| field_permissions.admin.inc | 9 년 전 | |
| field_permissions.admin.js | 9 년 전 | |
| field_permissions.info | 9 년 전 | |
| field_permissions.install | 9 년 전 | |
| field_permissions.module | 9 년 전 | |
| field_permissions.test | 9 년 전 | |
README.txt
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Field Permissions module
;;
;; Original author: markus_petrux (http://drupal.org/user/39593)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
CONTENTS OF THIS FILE
=====================
* OVERVIEW
* USAGE
* REQUIREMENTS
* INSTALLATION
OVERVIEW
========
The Field Permissions module allows site administrators to set field-level
permissions for fields that are attached to any kind of entity (such as nodes
or users).
Permissions can be set for editing or viewing the field (either in all
contexts, or only when it is attached to an entity owned by the current user).
Permissions can also be set for editing the field while creating a new entity.
Permissions for each field are not created by default. Instead, administrators
can enable these permissions explicitly for the fields where this feature is
needed.
USAGE
=====
Once Field Permissions module is installed, you need to edit the field settings
form to enable permissions for each field where you need this feature. You can
choose from three options:
* Public (author and administrators can edit, everyone can view)
* Private (only author and administrators can edit and view)
* Custom permissions
The default value ("Public") does not impose any field-level access control,
meaning that permissions are inherited from the entity view or edit
permissions. For example, users who are allowed to view a particular node that
the field is attached to will also be able to view the field.
"Private" provides quick and easy access to a commonly used form of field
access control.
Finally, if "Custom permissions" is chosen, a standard permissions matrix will
be revealed allowing you full flexibility to assign the following permissions
to any role on your site:
* Create own value for field FIELD
* Edit own value for field FIELD
* Edit anyone's value for field FIELD
* View own value for field FIELD
* View anyone's value for field FIELD
These permissions will also be available on the standard permissions page at
Administer -> People -> Permissions.
INSTALLATION
============
1) Copy all contents of this package to your modules directory preserving
subdirectory structure.
2) Go to Administer -> Modules to install module. If the (Drupal core) Field UI
module is not enabled, do so.
3) Review the settings of your fields. You will find a new option labelled
"Field visibility and permissions" that allows you to control access to the
field.
4) If you chose the setting labelled "Custom permissions", you will be able to
set this field's permissions for any role on your site directly from the
field edit form, or later on by going to the Administer -> People ->
Permissions page.
5) Get an overview of the Field Permissions at:
Administer -> Reports -> Field list -> Permissions
;; Field Permissions module
;;
;; Original author: markus_petrux (http://drupal.org/user/39593)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
CONTENTS OF THIS FILE
=====================
* OVERVIEW
* USAGE
* REQUIREMENTS
* INSTALLATION
OVERVIEW
========
The Field Permissions module allows site administrators to set field-level
permissions for fields that are attached to any kind of entity (such as nodes
or users).
Permissions can be set for editing or viewing the field (either in all
contexts, or only when it is attached to an entity owned by the current user).
Permissions can also be set for editing the field while creating a new entity.
Permissions for each field are not created by default. Instead, administrators
can enable these permissions explicitly for the fields where this feature is
needed.
USAGE
=====
Once Field Permissions module is installed, you need to edit the field settings
form to enable permissions for each field where you need this feature. You can
choose from three options:
* Public (author and administrators can edit, everyone can view)
* Private (only author and administrators can edit and view)
* Custom permissions
The default value ("Public") does not impose any field-level access control,
meaning that permissions are inherited from the entity view or edit
permissions. For example, users who are allowed to view a particular node that
the field is attached to will also be able to view the field.
"Private" provides quick and easy access to a commonly used form of field
access control.
Finally, if "Custom permissions" is chosen, a standard permissions matrix will
be revealed allowing you full flexibility to assign the following permissions
to any role on your site:
* Create own value for field FIELD
* Edit own value for field FIELD
* Edit anyone's value for field FIELD
* View own value for field FIELD
* View anyone's value for field FIELD
These permissions will also be available on the standard permissions page at
Administer -> People -> Permissions.
INSTALLATION
============
1) Copy all contents of this package to your modules directory preserving
subdirectory structure.
2) Go to Administer -> Modules to install module. If the (Drupal core) Field UI
module is not enabled, do so.
3) Review the settings of your fields. You will find a new option labelled
"Field visibility and permissions" that allows you to control access to the
field.
4) If you chose the setting labelled "Custom permissions", you will be able to
set this field's permissions for any role on your site directly from the
field edit form, or later on by going to the Administer -> People ->
Permissions page.
5) Get an overview of the Field Permissions at:
Administer -> Reports -> Field list -> Permissions