Hi guys,

i am new to Drupal, but i find it awesome!!!
I've installed the Storm module with following setup (made it as simple as possible):
- i have created an organization and added a person to it (user is linked with a drupal account)
- i've set following permissions for authenticated users:(Storm:access dashboard, Storm organization: access, Storm organization: view belonged)
The Problem: logging with the person's account i can view a list of the organizations, but if i try to access the organization info (the node itself) i don't have the rights (Access denied You are not authorized to access this page.)
When i set the permissions to "view all", then i'm able to access the node with the org. info. The same is with storm editing permissions.

I've tried installing Storm on another Drupal installation i have with fewer modules and i reaplied the same scenario and i had no such problems, so it seems to me, that this is either a permission to be set from another module or i have somewhere a module conflict with the persmissions ...

Thanks in advance!

Comments

juliangb’s picture

juliangb commented
Category: task » support

Which other modules are you using on the site with problems?

Or alternatively, which additional modules are used on that site compared to the one where you don't have problems?

nibo’s picture

nibo commented

Thanks for the quick reply!

The additional modules in the "problem child"-site:
- Advanced Help
- Calendar
- CCK
- Colorpicker
- Custom Links
- Date
- Homebox
- JQuery UI
- Me
- Token
- User Relationships

tchurch’s picture

tchurch commented

+1 (interested)

juliangb’s picture

juliangb commented

Ok, I can't see any modules in there that would cause this problem (usually the conflicts are with other modules that define access restrictions).

Perhaps just double check that all settings are the same on both, and that the user is correctly linked in both cases.

juliangb’s picture

juliangb commented

tchurch, have you had this too?

tchurch’s picture

tchurch commented

I remember having an issue with the "view belonged" permission but can't remember what it was. It wasn't that important for me in the end because my customer was OK with "view all" permission for his workers and "view belonged" for his customers.

It does seem a stranger permission though.
A person can only belong to 1 org which is OK if you have a 1-to-1 relationship, person-org (like with customers).

If you have a 1-to-many, person-org (like with employees, doing work for more than one customer), then this is useless really, because there are conflicts with the team function.
i.e. a person in org1 cannot see project2 (for org2), even if the person belongs to a team allowed to see project2, because the user doesn't have "view all" permissions.
You might not want the person to see all orgs, only the orgs he should be working for.

I'm getting off topic now, as this is a different issue. Maybe we need to think about extending the team functions to allow assigning a team to see an org.

nibo’s picture

nibo commented

Hey there,

i saw another additional module, that i had just installed (but not enabled) in the working version, this is the OG. And form the organic groups comes also the problem. I don't know what or where exactly it is, but i tried disabling the OG modules and then rebuilding the permissions and suddenly the user had access to the org info page.
Have you got any idea where the problem with the OG could be? I would definetly like to keep (and need) both modules!

juliangb’s picture

juliangb commented
Title: Permissions Issue » Conflict with OG
nibo’s picture

nibo commented
Status: Active » Fixed

I had recently tackled this issue again and the solution was to change the storm module weight in the system table in the DB (in my case I set it to -1). This solution worked for me. I will mark this one as fixed :)

juliangb’s picture

juliangb commented
Title: Conflict with OG » Document conflict with OG
Category: support » task
Status: Fixed » Active

We should document this in case others have the problem.

Would you be able to confirm - so OG has a weight of 0, and Storm now has -1?

nibo’s picture

nibo commented

Would you be able to confirm - so OG has a weight of 0, and Storm now has -1?

Yes,
by default the OG module sets a module weight only for og_access = 1 and all other OG related modules (og, og_actions, og_notifications, og_views) are leaved at the default value of 0. So I only changed the Storm module weight to -1 and everything works fine now.

So as a summary:

  • OG has a weight of 0
  • OG Access has a weight of 1
  • Storm has a weight of -1
juliangb’s picture

juliangb commented
Status: Active » Closed (won't fix)

Rethinking this - generally the instruction is not to use multiple node access modules.