| Attribute | Average |
|---|---|
| Features | 5 / 5 |
| Reliability | 5 / 5 |
| Ease Of Use | 5 / 5 |
| Documentation | 4.6 / 5 |
| Vote Count | 5 |
The Field Permissions module allows site administrators to set field-level permissions to edit, view and create fields on any entity. Features Enable field permissions on any entity, not just nodes. Role-based field permissions allowing different viewing patterned based on what access the user has. Author-level... [More...]
| Maintainer: | markus_petrux |
| Links: |
|
| Categories: | Content Construction Kit (CCK), User management |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 7.x-1.0-beta2 | 2012-Jan-25 | Download | Recommended |
| 6.x-1.0 | 2009-Nov-14 | Download | Recommended |
| 7.x-1.x-dev | 2012-Jan-11 | Download | Development |
| 6.x-1.x-dev | 2011-Feb-25 | Download | Development |
Options: Add a review
In the configuring page of this module getting below error in commerce kickstart 2. but it was good to use in commerce kickstart 1. Will be impressed on help of anybody.
Notice: Undefined index: product in _field_ui_bundle_admin_path() (line 325 of E:\xampp\htdocs\commerce\modules\field_ui\field_ui.module).
Notice: Undefined index: product in field_permissions_overview() (line 357 of E:\xampp\htdocs\commerce\sites\all\modules\field_permissions\field_permissions.admin.inc).
Notice: Undefined index: message_type in _field_ui_bundle_admin_path() (line 325 of E:\xampp\htdocs\commerce\modules\field_ui\field_ui.module).
Notice: Undefined index: message_type in field_permissions_overview() (line 357 of E:\xampp\htdocs\commerce\sites\all\modules\field_permissions\field_permissions.admin.inc).
I'm just starting to use this, but I think it's going to really help me develop the data structure for a site where I need to keep track of user achievements but I don't want the users to edit their own achievements. Thanks! If I run into problems or discover additional feedback I'll edit this review
Needed a means of controlling access to fields in order to provide an "approved" status to a content type which can only be set by a moderator.
Took a moment or two to find the interface to the access interface, but of course it was in the most sensible place (in the "manage fields").
Did exactly what I needed. Thanks a bunch. Very impressive module.
This did the task for me, as i wanted (authenticated)users to be able to add certain content-type nodes, but only edit their own stuff, unlike CCK "Content Permissions" where "edit" field means 'create and edit anyone's stuff'.
It took me a bit of testing to find how to establish the system i wanted, but basically, after installing the module (following markus' directions):
Create * (edit on node creation).
Edit * regardless of node author.
Edit own * on node created by the user.
View *, regardless of node author.
View own * on node created by the user.
As you recognize the consequences of this fine-tuning, you'll know which Field_Permissions you should 'check' within each Content-type - you won't need such a fine-grained approach in many Content-Types, eliminating all the extra radio buttons in User Management/Permissions.
NOTE: unless you're expert, try this on just one Content-type first --- if you have lots of fields, you don't want to go back and re-edit all those fields again.
many, many, thanks markus!
This is the most comprehensive module I have come across so far for handling field permissions. I had a content type with about 15 CCK fields, I wanted to reduce the form to only about four fields during creation but display all the fields when editing an already created content. This is the only module that helped me to achieve that.
Many thanks to markus_petrux for this generous donation.
Albert
