By dkreviews on

I am pretty new to Drupal, but I don't get it, why such an important feature is missing from default Drupal 6.2 installation. All I am trying to do is hide menu/pages/stories from anonymous (or some users).

I had module installed privacy by role, but that one has major bug where it screws up the sorting. So why there is no such built in option for Drupal 6.2? Or am I missing something? Any help would be appreciated!

⋅ Categories: Drupal 6.x

Comments

vm’s picture

vm commented

So why there is no such built in option for Drupal 6.2?

because not everyone needs that kind of funtionality.
because no one has provided a patch, or a suitable patch to do what you ask.

what you can do though is investigate the downloads area where there is a user access / authentication section.
Understand you are using the latest release of Drupal and many of the contributed modules have yet to catch up to that version.

I'd suggest starting to build your site with Drupal 5.x where you have the access to many more modules and when all such moduels that you design your site with are ported to Drupal 6.x move to Drupal 6.x at that time.

_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )

Moonshine’s picture

Moonshine commented

I'm using "Node Privacy By Role" on a 6.2 site currently and it's working well for me. No sorting or sticky issues with the site. So you may have to poke around a bit more to find the cause.

Although I do agree. Drupal really shouldn't group the "access content" permission for all content types. Especially when every other node permission (create, delete, edit,etc) *is* broken out by content type.

xmacinfo’s picture

xmacinfo
he/him
Primary language French
Location Canada
commented

Drupal really shouldn't group the "access content" permission for all content types. Especially when every other node permission (create, delete, edit,etc) *is* broken out by content type.

Well, I do agree with you on this point.

It's too late for Drupal 6.2, though. However, for Drupal 7 it would make sense.

That said, we should look at the list of issues for Drupal 7 (or older) and see if someone else came up with the same idea. If not, we should open a feature request (or bug) issue and try to convince a core developer to create a patch.

Unfortunatly, I'm not good enough to create that kind of patch.

/*_*/
http://www.xmacinfo.com