Status of 6.x.-1.2 please
-Anti- - July 9, 2008 - 07:34
| Project: | node privacy byrole |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
I'm getting this message in my site's update page:
node privacy byrole 6.x-1.2
Project not supported: This project is no longer supported, and is no longer available for download.
Disabling everything included by this project is strongly recommended! Includes: Node Privacy By Role
Can I just clarify that the 6.2 version has been removed only temporarily, until D6.3 is released with permission/security bug-fixes in the core? I'd like to know if possible, because I'm building a school website which requires content to be marked private or public, and 'node privacy by role' was at the center of the permissions scheme.
Thanks very much.
#1
subscribing: Would like to know if I should wait for a new release, or find another way to manage the privacy of nodes by roles...
#2
Yes, it's temporary. Drupal 6.3 will be supported, but everything is on hold until then.
#3
subscribing... (is this the only way to subscribe in Drupal.com?)
That "Disable everything" message freaked me out too!
D6.3 is now out apparently.
#4
Thanks for the update.
I'm evaluating Web management systems and this functionality was key. I installed Node_Privacy_By_Role it got it running just fine (in my relatively simple site) then got the bad "Project Not Supported" message a few days later!!! I then went an checked out several other web CMF/CMS systems and found them lacking either this capability or otherwise undesirable.
I'll try sticking with Drupal and seeing where this goes. I'm more a Java/C++ algorithms person but if necessary I'll try hacking a bit of PHP.
#5
> I installed Node_Privacy_By_Role it got it running just fine
The feature that seemed to be broken was the 'batch' feature in admin > content. You're supposed to be able to select multiple nodes, and edit their 'privacy by node' permission all at once, rather than have to do each one individually; it wasn't working. The rest of its functions seemed to be fine though.
Now that D6.3 is released, I'm sure the developer(s) of this module will be fixing it the best they can over the next couple of weeks or so, depending on how many bugs have been corrected in the core.
It is quite scary though, realising that you're entire usage of Drupal relies on two or three contributed modules.
You just have to hope that the devs don't move to Antartica to study penguins, or develop a phobia of php.
Cheers.
#6
Hi! I don't understand, why delete the 6.x-1.2 file from server.
I install the Drupal 6.2 and 6.3 without auto refresh function with this module (from node_privacy_byrole-6.x-1.2.tar.gz). My website is working fine.
If need somebody this module, visit the attachment!
Have a nice day!
#7
You're just wasting space on the server. It has always been available at http://drupal.org/node/267716. Feel free to edit your post and remove the file.
#8
I re-activated releases on 6.x. You may stop freaking out now.
#9
> Hi! I don't understand, why delete the 6.x-1.2 file from server.
The developer stated in a previous post that if he'd known that the core for Drupal 6.x-1.2 was so buggy (with regard to handling permissions), he would never have released the 'node privacy' module as a stable version, and instead kept it as a dev version until the core was fixed.
I think this is why the stable version was removed from the download list.
#10
> I re-activated releases on 6.x. You may stop freaking out now
lol.
Hey deekayen,
Do you think 6.3 fixed everything that it needed to (with regard to permissions) to allow your module to work?
Do you have anything to fix in the actual module, or is the 6.x-1.2 version working as desired now?
Cheers.
#11
Automatically closed -- issue fixed for two weeks with no activity.