Please: [Cross-posted at other Module issue page]

I seek help in deciding which module I should use,
or whether I might have occasion to need both modules.

Looking at the projects pages I cannot determine the difference between these two,
and I am additionally concerned about whether using both will cause conflicts.

My first thought is that the existence of both of these modules
in simply another example of a violation of Drupal's primary co-operation ethos
discussed in paragraph one of "Joining forces with others and co-maintaining projects"
http://drupal.org/node/23789

[Quote]
The Drupal community follows the ethos collaboration rather than competition. Too often new modules are contributed that do nothing new; instead, they only do it in a different way. We are then stuck with two modules that offer nearly similar functionality, ... This leads to confusion, clutter, and a lot of inefficiency.
[/Quote]

Assuming I am wrong and that there are notable differences,
would you please be so kind as to delineate here for me
what makes this module different from the other.

I would also appreciate, if you have the time and detachment,
your listing of any (if any) suggested additional complimentary modules
on your projects page with brief opinions/ explanations of their functionality.

Thanking you in advance, and wishing you all the very best...

-Chris

PS: Cross-posted URL to follow in comment #1.

Comments

christopher james francis rodgers’s picture

christopher james francis rodgers commented

Cross-posting: Simple Access http://drupal.org/node/1175986

dman’s picture

dman commented

Just from reading the project descriptions :
Content access provides this functionality per-content-type
while Simple access provides it per individual node.

That's a significant difference.
Though, in the long term, it would be interesting to see if the two could merge and offer both.

christopher james francis rodgers’s picture

christopher james francis rodgers commented

Thank you kindly for your clarifying response.

I will install both.

You are indeed "D' man".

:o)

Anonymous’s picture

Anonymous (not verified) commented

Content Access optionally provides per-node controls as well. The option is enabled per-content type to enable the per-node access controls.

christopher james francis rodgers’s picture

christopher james francis rodgers commented

jjs:

Thank you for your input.

Please then; am I right to conclude that "Content access"
gives me all of the control that "Simple access" does?

... and therefore I have no need to install and learn both?

-chris

All the best to all of you
and I still welcome any other (if any)
recommendations for achieving absolute
and granular control at my sites.

Anonymous’s picture

Anonymous (not verified) commented

I have not used Simple Access, but in looking at the project page I believe it does. It seems to do it in a significantly different way, particularly with respect to the methods of assigning access and the UI. I cannot tell if Simple Access uses the ACL module or not (it doesn't seem to?) -- I know Content Access does, and it, once you set the weights properly, will play nicely with other ACL modules like Forum Access.

I like and use Content Access personally, but you'd probably get the best results by testing both out and seeing which better suits your usage.

christopher james francis rodgers’s picture

christopher james francis rodgers commented

Try both, huh. Hmm. I was afraid someone would say that. :o)

I just noticed that Simple Access is co-maintained by Jeff Robbins of Lullabot;
the PodCast man. ..and I listen to those regularly.. and they are serious Drupalites
at that company.. So there must be something good about it-- for sure.

Anyway, thanks. If I learn anything note-worthy (it will likely be a-while later, though)
I will come back here and post it.

Thanks again for your time and input.

-Chris

good_man’s picture

good_man commented

First SimpleAccess does assign access by groups, you can create groups from it's settings page, then assign view/update/delete access to this group from node's edit page.

While in Content Access this approach is different, CA does rely on the already role(s) in Drupal, and on users. There is no content-type access settings in SA, but in CA there is. The node-access-settings is optional if you enable ACL. The approach to assign access to individual users is easier (at least IMO), you type the name of the user in autocomplete textbox.

My advice, try both, choose the one that suits your needs. I think SA is more oriented towards creating groups without abusing roles. so for example all users are from one role, while they belong to different groups (e.g. math, music, etc..).

Hope this answers your question :)

christopher james francis rodgers’s picture

christopher james francis rodgers commented

Does "Organic Groups" encompass and provide (or will it eventually provide)
all of the features of both "Simple access" and "Content access"

If not, what features would I lack with OG:
1.) That SimpleAccess would provides.
2.) That ContentAccess provides.

Thanking you now for your help; now. :o)

- chris

===
Cross-posting in 'Simple Access' issues-que: http://drupal.org/node/1175986

sheldonkreger’s picture

sheldonkreger commented

Hi Chris,

OG will provide control over content access based on a user's membership status within a group. Then, one or more custom content types can be created to be accessed within that group. Each group has an owner who determines who is/isn't in a group. You can create additional user roles which have this ability, too (so you aren't restrained to one group owner).

For example, I may create a group called "East Side Crew." Because I want to keep our handshake a secret, I set up a content type called "East Side Videos" which only displays withing "East Side Crew." When I post a video of our secret handshake, only members of "East Side Crew" will be able to see it - people I have approved as group members. Later, we have some sick rap battle footage in which my sideman throws out an ill verse that makes the West Side guy break down in tears. That footage I want to show the whole city, so I use the "Public Video" content type when I post. So, even when anonymous users visit our group page, they can see that video.

Here is a very well presented, free tutorial which will show you how this module works.

http://www.youtube.com/user/ModulesUnraveled/videos

Also take a look at this tutorial, which goes over a simple permissions scenario, OG setup, content type creation, and a panels based display of a content feed on the group home page.

http://www.youtube.com/watch?feature=iv&annotation_id=annotation_165376&...

-sheldon
www.sheldonkreger.com

aendra’s picture

aendra commented

@sheldonkreger -- Quite possibly the best description of an access module ever.

christopher james francis rodgers’s picture

christopher james francis rodgers commented

OG: Won't work for my situation?

I use only the core content type "Book".

I want individual books to be available
to select individuals.

But my understanding is that I can not clone the Book content type
with all of the Core Book features/ capabilities.

Since Og requires me to create a new content type,
but since the new content type
can not be like the core 'book' content type,
I can not restrict/allow access to individual books
to separate groups. Correct?

christopher james francis rodgers’s picture

christopher james francis rodgers commented

See Post Above: My Error.
-chris

dianacastillo’s picture

dianacastillo commented

but per-node doesnt work right in "Content Access", it doesnt let you choose the permissions before saving the node and the interface is totally difficult for the user to understand

dianacastillo’s picture

dianacastillo commented

WHERE is the "settings page" for simple access ?? I cant find it .

dianacastillo’s picture

dianacastillo commented

The settings page for simple access doesn't come out unless you do this : https://drupal.org/node/887108

dhalbert’s picture

dhalbert commented

You may find this helpful: Overview of Node Access modules. Also, my own Drupal StackExchange question; I ultimately chose Taxonomy Access Control.

dianacastillo’s picture

dianacastillo commented

Well I finally got it working (Simple Access), I want access control by roles, not by taxonomy. And I had read that article which was not helpful , since they don't talk about simple access which is the best one , (although the fixes to the bugs havent been committed yet)

daveonaka’s picture

daveonaka commented

Note for those using Domain Access. Only Simple Access seems to work without conflict at this time. I've tested Simple Access, Content Access, and Deny Access. I needed to restrict node access and could have used either approach: unique content type or individual node restriction.

dianacastillo’s picture

dianacastillo commented

note, the fixes to the bugs in simple access have been committed already.

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Status: Active » Closed (outdated)

This issue has not received any updates in the previous 7 years. If you believe it to still be relevant, you are encouraged to reopen the issue and update it.

If you got an email about this Issue status update, it is because you at one time (possibly a very long time ago), subscribed to it. To learn how to unsubscribe yourself, please visit: https://www.drupal.org/project/webmasters/issues/3142987