[DUG-TO] A problem to contemplate

[Ashok Modi GMAIL]

Hi Evan,

Give the node override module a try.  Otherwise, you could probably  
create module with a form alter to give default values to fields and  
sections you want to 'hide'.

-Ashok

On Apr 14, 2009, at 10:32 AM, Evan Leibovitch 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