Posted by Anonymous on May 19, 2008 at 5:53pm
Hi folks,
I'd like to make a couple of fields that I added to the user profile view only. Only the admin will be able to enter new users. Users can update their profiles but I want to prevent them from changing a couple of fields. I'm using Drupal 5.7 with the profiletabs module.
I realise this is probably obvious but I'm stuck as I am still pretty new to Drupal. I've searched and searched for the answer and also posted it on the support forum with no response.
Can you please stir me in the right direction? I'm prepared to buy you a beer! :)
Thanks!
-Francisco
Comments
These might be
These might be useful:
http://drupal.org/project/userprotect -- seems to be more current; I'd probably try this first.
http://drupal.org/project/user_readonly -- an older module, seems to be less actively maintained --
I'd set up a test site to experiment with this -- I haven't used either of these module personally, so I can't vouch for their effectiveness/stability firsthand.
Another more complicated (but more flexible route) would be to use the Bio module with cck field permissions.
Cheers,
Bill
FunnyMonkey
Tools for Teachers
FunnyMonkey
Thanks!
Thanks Bill! I think user_readonly is exactly what I need. It allows you to specify which fields from the user account and profile to make read-only to the user. I am experiencing a hickup when the user goes to edit their profile: I'm getting an error. I can see that they marked the same as fixed a while back but apparently it is not really fixed. If I can not get it sorted out I might try the Bio and CCK route.
In any case, thank you!!! I owe you a beer.
Francisco
Mmmm. Beer.
Drupal is tasty :)
Bio and CCK is what we use on a pretty regular basis as well -- it's relatively simple, and opens up a plethora of options -- one of my personal favorites is freetag vocabularies to hold user interests.
Cheers,
Bill
FunnyMonkey
Tools for Teachers
FunnyMonkey
+1 Bio and CCK Field Perms
That is exactly how I handle a number of situations for different profile requirements. Also, works very well for using email field in the bio/profile, but with a little hook_user (sometimes hook_nodeapi as well) magic, the email field on the profile is automatically set from the user account, and the user never sees the profile email field.
Lots of cool options here. I also sometimes use hidden CCK fields to control sorting the profiles with Views, since Views 1 is not user aware. This allows sorting profile nodes by role. (Often times very handy).
Thanks Bill F and Mikey P!
To close the loop, I ended up using: Bio, CCK (including CCK Field Permissions), Profile Tabs, Automatic Nodetitles and ProfilePlus. Good stuff!
Your input was very helpful and much appreciated!
Francisco