Port of Content access for D6

I also wonder about this!

Me too.

A Version for Drupal 6 would be very nice to have.

I agree, or at least some good access restriction system

Yes, with ACL and Forum Access now working with v6 it would be good to be able to permission other content too.

from the node privacy by role page:

...This module is deprecated in favor of Content Access with ACL...

So it seems as if this module is the AC future for drupal-- an update on a D6 version would be greatly appreciated. And if there's anything we can do to help, just let us know....

It would be nice if the author could let us know if there is in fact a Drupal 6 version coming. If not, we need to make other plans. Would hate to start developing something that is about to be released.

has anyone heard any news on this? I see work is still being done on 5.x, but no word on a 6.x version

:-) I have a project coming up that would find this very useful, but the plan is D6 based. I'd also like to know if there is any plans to move forward on it in the near future or if something particular is in the way.

yeah i wondered why no module is currently doin the job.
tell us what we can do!

Oh yes, I would like to get a D6 Version of content_access too. I hope the developers will publish it in a few days.

Thank you very much for developing! :-)

As droogie mentioned in #7, it would be great if someone connected to this module could give us some feedback on when (or if) we can expect a D6 version of Content Access. Any info would help. Thanks.

This naming scheme seems to be what is being used in other projects. Hopefully will make life easier in tracking the ports of multiple projects to D6. Sorry if its inappropriate for me to do this, just chastise me. :-)

yes a D6 port would be greatly appreciated, as there, as far as i know, no proper user restriction modules for D6...

I'm also waiting for this module to be ported to D6!

First of all, I'm not quiet experienced with Drupal but during my evaluation it seems like a pretty good system. Currently investigating the usability of Drupal 6, but missing one major feature: per node ACL (e.g. display only menu item x to user 2, 3 and 4 and menu item y to user 3, 6 and 9).

Instead of waiting for the Content Access Developers (It seems quiet around there?) to port their module to Drupal 6, going to try it on my own. Volunteers are welcome!

Done so far:
- Module is getting recognized by Drupal 6
- After installation menu option 'Access Control' is available at Admin section.

So: it's still not working, and you're welcome to join!

Waiting as well. Considering a downgrade to D5 :(

Updated content_access for Drupal 6. As mentioned: still not working!

To do:
- figure out howto disable cache for content_access menu
- after 'submit' has been clicked, values has to get parsed & stored.

mvdschoot, can you post your work as a patch against the branch DRUPAL-5 of content_access? See http://drupal.org/patch

watching eagerly

Subscribing

Subscribing

It would be nice if the author could let us know if there is in fact a Drupal 6 version coming.

I've asked the developer whether he continues the development of this module.

It's continued, but I'm currently busy with other things/ports. So I probably won't port it before July.

If someone is quicker, just do it and I'll commit it. Porting shouldn't be a big deal here.

ah, and yes please use patches against 5.x-dev. When there is a working patch I'd be happy to commit it.

Subscribing as well... looking forward to D6 version!

subscribing

Conntet access patch for content_access-5.x-1.x-dev

Nightly development snapshot from CVS branch: DRUPAL-5
Download: content_access-5.x-1.x-dev.tar.gz
Size: 12.57 KB
md5_file hash: 667adbdfd0f82bc6161e534b3698c7d9
First released: May 17, 2007 - 20:40
Last updated: June 11, 2008 - 00:02

Errata patch
how to set more than one user rights in hook_menu ??

Tagging this for subscribing

tagging.

question: why a patch for content_access-5.x-1.x-dev if we talk about having a dp6 version?

tagging.

question: why a patch for content_access-5.x-1.x-dev if we talk about having a dp6 version?

@mark_r, it has to do with the way projects are hosted on Drupal.org and tied in with the CVS repository. There isn't a DRUPAL-6--x branch of content_access so patches need to apply to another branch. fago removed the code from the HEAD branch of the cvs code so only the DRUPAL-5 branch is available. Patches need to be against the latest code of this branch which is why this issue is marked 5.x-1.x-dev.

Wouldn't it be possible to add xaweryz to the list on content_access developers, so he could work on the CVS-code directly (in its own D6 branch of course)? This way it should be easy to push out some dev-download for D6, as this patch works pretty well...didn't have any problems with it so far.

Just curious....

>how to set more than one user rights in hook_menu ??
you need to write your own access callback

@ddanier: the patch misses proper access checks. Furthermore there also some tabs in there - please only use spaces for indention (drupal code style!). When this is fixed, I'm happy to open a 6.x branch.

> Furthermore there also some tabs in there - please only
> use spaces for indention (drupal code style!).

Thats nothing I would really worry about as my editor is able to convert tabs to spaces (I use it the other way round). I think many other editors have similar features. So the tabs-issue should not be the show-stopper...but missing access checks are. ;-)

subscribing

Ok. conntent_access patch with own user access callback :-)

Only change function name
from content_user_access
to content_access_user_access

I have 6 content types on my testing site. The patch applied cleanly.

I installed the module and went to permissions to edit the Content Access. In this area I had two sections added "content_access module" and "content_permissions module". The first has "grant content access" (duplicate of existing permission?) and the second has "grant own content access". The content_permissions module only listed 2 items under it. both had to do with granting contest access and granting own content access of the same content type. The other 5 content types were not present.

I don't think this patch worked for me, unless I don't know what I'm looking for. For this reason, I'm marking it needs more work.

Anything specific about it you want me to look into?

1. I dont't know what is content_permissions module ??
2. in Permissions path=> (admin/user/permissions) there are only two permissions .. And is it ok!!
3. Please check path (admin/content/node-type/page) or edit other node-type page.
There is "Access control" page from conntent access module. Not in Permissions!!!

And i change status to patch (code needs reviwew)

1. I dont't know what is content_permissions module ??
2. in Permissions path=> (admin/user/permissions) there are only two permissions .. And is it ok!!
3. Please check path (admin/content/node-type/page) or edit other node-type page.
There is "Access control" page from conntent access module. Not in Permissions!!!

And i change status to patch (code needs reviwew)

On #1: Oh, I see, content permissions is a CCK thing. Nothing to do with this. Sorry for the confusion.

On #2: Yes, I see both those permissions. They appear fine.

On #3: :-) That's what I was looking for before. Thank you for the directions. It looks good, but I have a few questions.

Why doesn't the author have view, edit and delete permissions by default? In my view they are all unchecked.

The "Give Node Grant Priority" description leads me to believe that this is a module wide configuration. If that is so, shouldn't it be on a separate configuration screen specific to the module?

When giving per node control, it would seem to be more consistent with the typical drupal interface to have the controls in one of the lists at the bottom like publishing options, input format and the like. I'm thinking about this module for users to handle the security of their own blog posts and things like that so I'm interested in this being as easy as possible for them to catch on to.

I have not used the 5.x version of this module so I expect that my questions have to do with how this module is implemented in a more global sense so probably shouldn't slow down the release of this module.

In the forum content type, under access control, I'm getting this error message:

On clean install drupal 6 plus conntent_access
i don't have any warnings.

ok, I had a short look at it. Thanks for this work!

I've overhauled and cleaned some code, e.g. the menu code and committed in the new d6 branch.
--> http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/content_acc...

I've also fixed several php notices. Please develop with php notices enabled - use a development drupal 6 release as they are disabled in stable release afaik.

What needs to be done:
* test test test
* look at the ACL integration
* don't use the 'all' realm anymore: http://drupal.org/node/239139

So please file further patches again DRUPAL-6--1.
I don't close this issue as I don't consider the port as ready now. Let's have at least the basic functionality tested and verified working before doing a development release.

One small patch :-)

Thanks for this work xaweryz and fago.

xaweryz, one shouldn't use t() for the title any more, as it's now the default title callback, see http://drupal.org/node/140311

subscribing

subscribing

This is great, but what makes Content Access better than Node Privacy ByRole (http://drupal.org/project/node_privacy_byrole) ? Just curious if this upgrade is not so prioritized, why not cooperate with others when there is already a finished solution like the other module ? Which is already at version 1.3.

It's not really a matter of "better". They're different. Content Access allows for more flexibility than node_privacy_byrole. If the functionality you need is covered by node_privacy_byrole, then Content Access would probably be overkill.

drupal 6.x, v6 transparent admin
I am looking for transparent administration, open, visible and sometimes editable admin settings with security. based on permissions, locked individually (as a node?), password protected, view and/or edit choice for admin inserted at the top or bottom of all admin/settings pages. even better, password or radio button next to every settings choice as viewable and/or editable similar to form field protect. a prominent notification to the user, “you can view this page of administration settings, if they require edit, please email administration with your request link”. Possibly even attached comment or site note section, ability to insert instruction or voting widget.
I gather this is the approach taken by adding access control to the core and maybe it is similar to drupal core building. I have been looking at everything I can find and I’m not a programmer yet, so I need to pass what I’ve found on to someone else here. If someone can put these pieces together or have experience with something similar with any version 4,5,6,7. i'm listing this at all of these locations aswell. Rsvp, elisa

http://drupal.org/node/109157 access control
http://drupal.org/node/131101#comment-735943 Add disabled attribute to protected fields
http://drupal.org/node/245900 How to Protect Nodes From Editing on Demand
http://drupal.org/node/31143#comment-796152 Node Privacy by Role not working
http://drupal.org/project/nodeaccess nodeaccess
http://drupal.org/node/126129#comment-703933 password protect a page
http://drupal.org/node/222263#comment-902378 Port of Content access for D6
http://drupal.org/node/29991#comment-51352 Protected content
http://drupal.org/node/13266 Show block to certain users or roles only- Drupal 4.6
http://drupal.org/project/simple_access simple access
http://drupal.org/node/118404#comment-735895 View, but not edit, field at node/xxx/edit

I’m not a programmer yet

Then do not change the settings of an existing issue. Please open a new issue.

subscribing

subscribing

subscribing

subscribing

The above comments suggest the D6 port is under way. That's great ! What is the reason there is no D6 development snapshot (yet) ? Having that may help others experiment and test.
Thanks !

Subscribing

subscribing

So I ported content access over to Drupal 6.3 but decided to call it nodeaccess (much to my surprise) there is already a module called that in the repository. So I reviewed the code for nodeaccess, yuck. Regardless neither of the existing modules provided the level of sophistication I needed for my clients. And I found the interface ergonomics of content access are far superior to the node access module. I also didn't like the ACL module so I rewrote my code to exclude it.

So either my code can be useful for the team or not. I have no interest in going through the code review, posting via cvs stuff. so I am willing to post the code here is someone else would like to manage it.

Hi Emptyvoid,

Could you provide it as a dev for testing ?

Thank you

Subscribing

Unfortunately I don't have a location to host the build.. I can provide the source as it is and everyone is welcome to review, fix, or otherwise bitch me out for my poor coding ;P.

Update!! - Employer requested I remove source until formalized policies are defined for distributing company/client source code.

This isn't the right place for a new or modified module. This is an issue for Content Access.

Please open a new issue, assign the issue to yourself and post your code for review.
Just my two cents.

Hi Bennysoft,

It seems to be about content access port. Isn't it ?

It's not.

@everyone waiting for the port: I'll have a look at it on Thursday!

That's great! Been using the cvs version for quite some time. Seems to be working well... at least we haven't had any problems with it.

subscribe

I've just created the first dev release. It basically works, but needs some polishing. I have to look at the ACL integration it seems to somehow fail. Furthermore workflow-ng integration still needs to be ported to rules.

Please open separate 6.x issues for 6.x related stuff.

I am sorry, but am I too stupid, or is there no 6.x(-dev) release yet? At least I didn't find it ...

There is now-- it takes 12 hours for the packaging script to do it's business.

Hi,

I've downloaded the 6.x version and it seems to be working fine. Can you provide details on any specific issues to be concerned about for use in a production site? I'm using it to restrict content by content-type, and don't need any particular workflow related functionality.

Thanks.

Probably this information could help you:

http://drupal.org/handbook/modules/node_privacy_byrole#comment-993875

Automatically closed -- issue fixed for two weeks with no activity.