By PeterLucas on

I probably put this question in the wrong place.

Content on my site is for registered users. The Events module still allows access no matter what I do. I don't see Events show up under Access Control. Is there a way to close off Events for non-registered users?

Comments

Anonymous’s picture

Anonymous (not verified) commented

The access control modules should allow you to do this. Simple access specifically, or taxonomy access, or one of the others. I don't believe there is a simple way to restrict access to content by node type. Node access in drupal is kind of hit or miss...

PeterLucas’s picture

PeterLucas commented

As I said, basic Access Control does not allow to do this for the Event module. I haven't tried Taxonomy Access, but I'm a bit weary of adding more stuff that could create new problems. I'm trying to keep my website simple and transparant.

So is this a problem in the Event module then? Will it be fixed in a new version? Are there pieces of code I could add to it or is it more fundamental than that?

Anonymous’s picture

Anonymous (not verified) commented

No, basic access doesn't, and I think you should file an issue for the event module to add an access control for 'access events', seems like it would be a good idea. Right now the event module does no access control of it's own, but it does respect any access put in place by modules (taxonomy access, simple access, organic groups, etc). So one of those modules would probably be the way to go.

The other option would be to go ahead and implement better access control in the event module. Then you could submit a patch for that. Of course, that requires a bit of time and knowledge of drupal and the event module...

PeterLucas’s picture

PeterLucas commented

I found this in Event Module's readme file:

- Drupal has poor support for running more than one node_access type module at one. That means that you can't run og with
taxonomy_access, nodeperm_by_role, nodeaccess, or any other node access control module. This is a core Drupal issue, not an og issue. Developers - feel free
to propose a soultion for this. See http://drupal.org/node/23193

Anonymous’s picture

Anonymous (not verified) commented

There's no clash between access modules and the event module. There's a clash between og (organic groups) and other access control modules. Are you planning on using organic groups along with another access module? If not, it's not an issue. If so, there's a patch around here somewhere to help the two work together.