[support] Role unable to post a content type

[Shai Gluskin]

Luis,

Make sure the vocabulary that you are using for access control is enabled
for that second content type.

Totally other thought, though this shouldn't affect creating new, I think
it's just a problem editing existing. But... make sure permissions for
various input formats are in order. For example, the most common problem
related to this is: user/x has administer node privileges --- can't get any
more privilege than that, right?. But user/x sees no "Edit" tab on node/y.
How is that possible? Node/y's input format has been set to an input format
that has been limited to a role that user/x doesn't belong to.

Many, many folks have wasted hours on this one because the connection
between input format and admin/node privileges is something that most people
don't think of. It took me running into that problem about five times before
I'd recongnize it off the bat and not have to research on drupal.org to
remember it. It seems unlikely this is your problem... but just thinkin' out
of the box to cover a base you might not have thought of.

Good luck and report back,

Shai

On Thu, Apr 2, 2009 at 9:01 AM, Earnie Boyd <earnie at users.sourceforge.net>wrote:

> Quoting Lluís <enboig at gmail.com>:
>
>  I have a drupal5 site with taxonomy access installed. I have created
>> some custom content types and a couple of administrative roles (one to
>> manage content and another to manage content, taxonomy, blocks,
>> etc...).
>>
>> Now a user of "role1" is able to post contenttype1 but unable to post
>> contenttype2
>> If I add user to "role2" he is able to post contenttype1 and contenttype2
>>
>>
> Is this the same user?   Did you log the user out, use a different session
> cookie, etc?  Make sure the role2 has the permissions you think.  Make sure
> the user doesn't have both role1 and role2.
>
>  I tried checking all permissions in "Access Control" for role1 with no
>> result, and also doing the same in all taxonomy access control for
>> role2 with no results.
>>
>> How can I guess which module is blocking create permission to role1?
>>
>>
> If you're lucky it is logged at admin/reports/dblog (for D6).
>
> --
> Earnie
> -- http://r-feed.com/           -- http://for-my-kids.com/
> -- http://www.4offer.biz/       -- http://give-me-an-offer.com/
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.drupal.org/pipermail/support/attachments/20090402/179d2378/attachment-0001.htm>