Protect Fields: Allow AUTHORS

Hello Community. I have managed to change the plugin so it allow me to protect more than 4 fields. That improves it´s utilization a lot. Now what i need is to allow AUTHORS to modify the protected fields, just like the administrators.

Please, if you know where in the code is that line i´ll really apreciate that help.

Thank you!

ventasman wrote:

Hello Community. I have managed to change the plugin so it allow me to protect more than 4 fields. That improves it´s utilization a lot. Now what i need is to allow AUTHORS to modify the protected fields, just like the administrators.

Please, if you know where in the code is that line i´ll really apreciate that help.

Thank you!

First of all, I honestly believe that with cb 1.2 there is no need for the protect fields plugin.

You can make any field read only - which means that the user cannot modify it after registration.

That's exactly what the protect fields plugin does.

Am I wrong?

Hello Nick. Thank you for your answer. This plugin protect fields from being modified by user, but allows administrator to modify them. Yes it is similar to that CB core function you mention.

But

Then when users intents to modify or fill a field that is protected, the plugin gives them a JS notice that can indicate that they are not on the user group that is allowed to modify that field.

So if i have authors, for example, and the protect fields plugin can do it´s work only on the registered users, they can expose tabs and fields with more information about themselves, than registered users, enhancing they presence on the website.

I don´t need to protect fields from being filled or modified on my website, what i need is to protect fields from being filled or modified by certain user groups, just as this plugin does, except i need to lower the access level to authors.

That is the general idea.

By now, CB have to options: All users can modify a field on their profile or No one can do that, except by administrators. That setting must be refined since authors may need special identifications and credentials to be more credible.

Probably the upcoming privacy plugin could solve a part of your problem on a per-field basis ?

Or a slightly modified version of it.

Sorry no time at this time to help on particular code, specially when you are not sharing your current version so that others could help ?

Just attach your current version to a post, maybe a community member will be interested and join your effort ?

Post edited by: ventasman, at: 2008/12/14 21:58

Sorry Beat, this forum didn´t allowed me to upload files or paste code.