[DUG-TO] A problem to contemplate

[Alex De Winne]

That's a good question :)

In general, many of the "standard" form elements in a 'node add page'
visibility is dictated by the permissions granted to the user who is
creating the node. So I'd recommend you have a look at creating roles for
these types of users and then assigning only the permissions required for
them to do what they need to do on the site and see how many field elements
are left in the content types at that point.

To remove additional fields, I believe would require custom module coding
with overrides, but I could be wrong.


ALEX DE WINNE 
THEREFORE INTERACTIVE INC.
T: 905 918 2690  |  F: 416 913 1953  |  W: THEREFORE.CA
INTERACTIVE  |  EMARKETING  |  WEB HOSTING

This message is intended for the addressees only and may contain
confidential or privileged information. Any use of this information
by persons other than addressees is prohibited. If you have received
this message in error, please reply to the sender and delete or
destroy all copies




On 14/04/09 1:32 PM, "Evan Leibovitch" <evan at telly.org> wrote:

> Alex De Winne wrote:
>> I would recommend only using contemplate if you need to. Things like hiding
>> comments for particular content types can easily be done with template file
>> overrides (node-type.tpl.php). For display forms, CSS and hook_form_alter
>> have served me well in the past.
>>   
> 
> Thanks to Alex and others for your helpful replies.
> 
> The more I read, the more I seem to find similar advice; that the
> Contemplate module is useful for identifying the
> fields to display, but that I should be using node-type.tpl.php and not
> Contemplate to do the actual display.
> 
> On trying that, I notice that it only affects the display form and not
> the data-entry one, and that's not quite what I want.
> 
> What I really want to do is disable certain "standard" content-creation
> fields (ie, menus, revision information, URL path, publishing options)
> for non-admin users, having them use their current defaults for most
> content types. In a perfect world I'd be able to customize this per
> content-type. CCK gives me sufficient permissions control over user
> ability to edit my custom fields, but no control over the "standard" ones.
> 
> Does there exist a module that would allow me to set permissions of
> whether certain users are allowed to edit menu, publishing or other such
> info? Or am I missing some existing settings?
> 
> Thanks!
> 
> - Evan
> 
> _______________________________________________
> DUG-TO mailing list
> DUG-TO at lists.openject.com
> http://lists.openject.com/listinfo/dug-to