I've created a new user in Drupal and attached it to a person record.
I've given all authenticated users access to:

Storm person: view own
and also
Storm person: access (although I have my own views created)

but the user cannot see his own person record listed (they see none listed).

Is this a bug?

Comments

Mark_Watson27’s picture

Mark_Watson27 CreditAttribution: Mark_Watson27 commented

Well technically I wouldn't call it a bug, but it's probably misleading.
I believe the storm permissions for 'own' refer to items created by that user.
As this user didn't create his person record he can't see it.

So technically the code is working, but I can understand that in this case you'd presume they could see their own person.

tchurch’s picture

tchurch CreditAttribution: tchurch commented
Category: bug » support

I understand.

If I wanted to manually (i.e. in the database) change who created the record (so that it showed that the user created his own record) where would I do it?

Thanks.

Mark_Watson27’s picture

Mark_Watson27 CreditAttribution: Mark_Watson27 commented

I believe this is done via the author field, which I believe was resolved in #572358: Use a better way than CSS to hide node fields, but that's in latest dev.

Magnity’s picture

Magnity CreditAttribution: Magnity commented

Sounds like the permission names (or descriptions) need to be more helpful.

How about
- Storm Person: view when author ; and also changes for other modules. Simply a name change from the current view own.
- Storm Person: view when self; new permission for case described in this issue. I'm sure it is a common one.

There are probably better ways of expressing the names than that though.

Mark_Watson27’s picture

Mark_Watson27 CreditAttribution: Mark_Watson27 commented

@Magnity: Sounds good to me. The other approach would be to default the author of a person to the user referenced. I think this approach is used in other user modules such as content profile. It may help reduce the growing list of permissions.

Magnity’s picture

Magnity CreditAttribution: Magnity commented

I'll take a look at content profile to see how its done there.

Alternatively, would it work to simply always grant the user access to their own record?

tchurch’s picture

tchurch CreditAttribution: tchurch commented

I would suggest using new permissions. You might not want them to have access to view/edit their own record.

Magnity’s picture

Magnity CreditAttribution: Magnity commented

@tchurch, what did you think of Mark's suggestion in #5 too? How would that fit with your install as an example?

tchurch’s picture

tchurch CreditAttribution: tchurch commented

I can see it working but it would mean that we no longer know who actually created the record.

We have multiple users who are allowed to create new people (under their own organisations) and I would prefer to keep the true author ID.

Mark_Watson27’s picture

Mark_Watson27 CreditAttribution: Mark_Watson27 commented

Thinking about it, I agree that keeping the two distinct is the logical route.

Magnity’s picture

Magnity CreditAttribution: Magnity commented
Title: Cannot view own person record » Permissions for person linked to own user account
Category: support » feature
Status: Active » Fixed

Committed

deggertsen’s picture

deggertsen CreditAttribution: deggertsen commented

I realize that there is quite a growing list of permissions for storm but I personally feel that this module needs a very diverse set of permissions so that the administrators have the maximum control possible. Yes, it's annoying to have so many permissions but it's even more annoying to not have the permissions for what you want to allow/restrict.

Magnity’s picture

Magnity CreditAttribution: Magnity commented

Yes - it degrades the experience for the new user (more settings to be confused by), but once set, they're set, so shouldn't affect normal use.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.