Drupal 6 port ?

I second that question. I'd be very interested into a port, too.
Thanks,

Thank you for your reactions, I've been on holiday for the last 3 weeks. A port to 6 will be started after the 5 version has a initial version 1.0 release. At the moment there is still an issue open so first have to work that out.

My aim is to get this ported in a timeline of 2 weeks from now.

The initial port has been done. If you can give me some help in getting this in a branch on CVS please do.
I'm used to subversion and Mercurial. No idea how to do this on CVS. Next thursday I'll look into it though.

It won't be a release yet because the simpletest tests have not been finished yet. But I'll release a dev version thursday.

Hey, four months (again) since the last update. Did this ever make it to testing?

Any idea when this will be ready for Drupal 6 ?

In looking at the files, there doesn't seem to be too much there, only need to modify things for Drupal 6 if anyone knows what items to update.

Update:

I was looking into these modules to see if I could automaticallly convert it from Drupal 5 to Drupal 6, there are some items apparently not correct, I was able to activate the module though but no interface showing up.

You can take a look at these to see if you can convert it.

http://drupal.org/project/schema
http://drupal.org/project/coder
http://drupal.org/project/deadwood

Some instructions here too http://www.webmasterworld.com/content_management/3767426.htm

R.Muilwijk, any chance you could just attach a patch to this thread? I'd be happy to do some testing, and give feedback...

I would love to upgrade to drupal 6 for soem other features but am unable to because this has not d6 version, and I loose all of the permissions.

When should we see atleast a devel ver?

thanks

subscribing

Devel module has been available for D6 for quite some time, but I'm sure that's not what you meant. The maintainer isn't comfortable with CVS, so he hasn't made the D6 version public. If you want it for D6, help him with CVS. Otherwise, stop complaining.

I wouldn't use this, anyway, because I could use role permissions for node access. What's wrong with using roles? They are very useful.

It's easy just upload the D6 version to drupal or right here in the threads, zip it and upload, what's so hard about that ? All he would have to do is ask someone on Drupal to help him with the CVS.

Maybe he's lazy, maybe he's too busy with his paid work, maybe he's just bored of Drupal. (LOL, why?)

This module will be deprecated in favour of Content Access. If anybody wants to take over Maintainership let me know.

NAC is better than Content Access and more intuitive, if I had to choose an access module, Simple Access module would be it, it's the best so far next to this module. I hope someone takes over this, would be a shame to pull the plug.

hmmz.. I thought everyone was starting to use content access so I stopped maintaining this. If more people are interested I might think about it.

Probably a good idea to get up a feature/interface comparison between the modules, and see if it's worth it, or if missing features can be added to other modules to bring them up to scratch.

This write up here says it all
http://drupal.org/node/268100#comment-875260

I know for myself, I've found this module easier to use than all the others, setup a permission and it's done easy. For membership organizations this model is very intuitive when wanting to assign more than one role to access.

Also this one is less likely to get accidentally hosed during upgrades. Some of the others when you set a node to a certain access during an upgrade can get reset. Node Access Control is my preferred approach.