Is above still your mission? I really love this module, don't get me wrong, but the latest 6X version is from 2009... And there are quite some things that could be done differant. Placing this module in a fieldset for example.

Comments

Michsk’s picture

Michsk commented

Quote is from the nodeaccess demo site.

mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
commented

subscribe. Is this still actively maintained? Any plans for Drupal 7?

frob’s picture

frob
Primary language English
commented

There was a new taxonomy term added a few weeks ago but that is all the update. It would be nice if they told us the status on this. I want to use this module but do not want to put it into a production site if it is not going to be updated.

Anonymous’s picture

Anonymous (not verified) commented

I've started work on the 7.0 version now that 7 looks stable. One of my goals is to get the grants on the edit tab, as well as clean up the UI. I hope to have a test release for 7 ready to go within a few weeks.

frob’s picture

frob
Primary language English
commented
Status: Active » Fixed

I was mainly concerned by the lack of a dev head and the fact that there has been a 2.0 release just around the corner for over a year. I know cvs is a pain, but devs and betas let us know that development is on going and allow us to help with qa before a major release. I am glad to hear that this project has not been abandoned.

mherchel’s picture

mherchel
he/him
Primary language English
Location Gainesville, FL, US
commented

Great news! This is a great module. Glad to hear it's still under development.

:)

Anonymous’s picture

Anonymous (not verified) commented

Yep it's coming along. At this point I've mostly got the UI knocked out, I'm hoping to have an alpha release for 7 in a week or two. This is by and large a complete rewrite and not an update however so may need some good testing before a stable release... So far things in store are:

1) All settings per node type

This will make it a bit more of a pain to configure (if you have numerous node types especially) but gives a lot more flexibility. For example, it will allow you to do something like configure Pages to only allow people to set View permissions but News articles can be set to view or edit. It's also a bit cleaner I think to have the settings per content type, rather than a bunch of content types on one admin page as it is now.

2) The permissions will be configured in the node/add edit form, no more grants tab.

3) The admin configuration will let you set permissions by user as well as role (currently the admin pages only let you set permission by role)

4) I'm ditching the priority setting, as it's confusing and really the only purpose of it would be to use more than one access control module, which I don't support and don't recommend doing anyway.

5) I'm also ditching the Role aliases and weights added by someone else previously. I personally don't think they're all that useful and it mucks up the code. But if there was demand I would consider adding it back in.

Once complete I plan to try and backport some of it to drupal 6. And after that if I'm feeling ambitious I'm considering adding plugin support. Not sure how feasible that is but I currently support 3 different methods of access control (users, roles and user reference) and I have a one off version I did which includes support for buddy lists. It would make sense to break each of those out into a plugin and would make it easier for folks to morph this to support more access methods in the future.

Anyway if you want to follow along, the repo is at http://github.com/chadcf/nodeaccess/commits/master

DO NOT attempt to install it... I'll post an alpha when it's ready, right now it's certainly not even close, the repo at this point is just useful for tracking the progress.

Michsk’s picture

Michsk commented

chadcf:
1: i like
2: i like that very much
3: interasting, don't know how much it will be used but heck it sounds good
4: i agree
5: i very much disagree. Believe me they are usefull. It makes the communication from 'us' to the enduser much stronger. We can use role names that we understand but end-users do not always have to understand. I would really love to keep this option, it is also one of the things why i chose nodeaccess instead of content access and others. So please, leave it.

Keep us updated!

frob’s picture

frob
Primary language English
commented
Version: 6.x-1.3 » master
Component: Code » Documentation
Status: Fixed » Needs work

I changed it to needs work and to Documentation because I think that the link to github (if you are using that for your repository) should be posted on the main page. Maybe just a blurb at the bottom saying something like.
Module posted here for convenience. To keep up with the current state of development please visit my project page on github. http://github.com/chadcf/nodeaccess/commits/master

Michsk’s picture

Michsk commented

Any progress on this one?

Anonymous’s picture

Anonymous (not verified) commented
Status: Needs work » Closed (fixed)

7x-dev is released, plans for v2.0 are in the works.