This module over core [#290769]

The core drupal installation has, per role, per content type, update and delete permissions that you can change. (refering to 6.x)

Am I correct to believe that the only functionality this module provides in addition to the core is, per role, per content type, view permission versus a blanket, as in for all content or no content, "access nodes" permission in the core? That and the optional per node permissions.

Is my asumption correct? If yes, doesn't it seem redundant to define update and delete permissions for each content type for each role in the core and then define the edit and delete permissions for each role for each content type in the content access module. Or am I missing somethign?

I hope I am not coming off as an ungrateful ___, I really I appreciate the work. I just can't seem to grasp the concepts.

Thanks!
-Nick

Comments

Comment #1

good_man commented 8 July 2011 at 12:35

Version:	5.x-1.x-dev	» 7.x-1.x-dev
Component:	Miscellaneous	» Code
Category:	support	» task

Your point is right, however the edit/delete grants per-node is an added-value in content access. For content type it's kinda redundant, so IMO we have three options:
- Remove them from content access, and let user define them in Drupal's permissions page (however I prefer settings all the permissions from single page, i.e. content access page for this content type).
- Leave them, but if checked they also checked the core's permissions. i.e. not using content access grants but the core grants, so two access pages, same effect. Right now if you enable it from content access page it would not appear check in Drupal's access page and vice versa.
- Leave it as it's now.

What do you think?

Comment #2

BenK commented 8 July 2011 at 23:09

I think it's probably best to leave it as it is now. Having one configuration page is a big advantage of Content Access. And the core permissions page is extremely slow loading if you have a lot of permissions. Plus, if you have a lot of content types, the core permissions page is really hard to use.

Khaled, I'm not sure I understand your option #2. Isn't that what Content Access does already? Doesn't it already keep things synced up between the content access content type settings and the core permissions page?

--Ben