Would you please be able to explain how your module is different from the many other node access modules? Specifically the primary node access module is Content access which based on your description provides the exact same feature while being a project that has lots of existing support and history behind it.

Comments

bobooon’s picture

bobooon commented

Although very similar, they are not the same. The content access is a GREAT module for most people. There are a couple reasons why this is different enough for people to have the option to use it:

  1. Does not use the node access tables, therefore does not depend on the state of that table. I've come across many times when this table gets corrupted temporarily and causes havok with clients/visitors.
  2. It's much less complicated to use which is very beneficial for clients/users that do not wish to learn the content access ropes.

It's not here in any way to "replace" or "compete" with the content access project. It's just an option for people who aren't needing a whole lot of complexity in the system. I'm actually going to update the description to make this clear.

bobooon’s picture

bobooon commented
Status: Active » Closed (fixed)
doublejosh’s picture

doublejosh commented
Status: Closed (fixed) » Active

Curious about being a duplicate of http://drupal.org/project/premium

- - - - - - -

After installing: it looks like this module is all about enabling certain user roles to restrict their content from other roles, node by node... while Premium is more about making a global admin setting to restrict each content type from specific roles with some message options.

Interesting. Could make a wonderful "Premium Content Role Restriction Suite" :)

bobooon’s picture

bobooon commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Project has been discontinued in favor of https://www.drupal.org/project/content_access.