The view at user/%/status is using the permission "view all statuses". I would like to change this to something more granular or possibly hook into the code to provide a list of permissions. the problem is I cannot find the right instance of user_access anywhere in the module directory. I have even gone so far as to eliminate all "view all statuses" code calls in hopes of finding the right one by error. They do not effect the modules permissions though. The toggle still works without them even after emptying the cache.

Where is this hiding?

Comments

carlmcdade’s picture

Hmm,

Found a list of rights management in views admin. The problem is this does not allow for on the fly comparisons to account uid and user uid. Once you have set this permission variable the user gains constant static access to the view. Does anyone have a solution to this? It seems like a common problem with views integration.

icecreamyou’s picture

Status: Active » Fixed

To change the permissions for a view, edit the view and click on the existing permission next to the heading "Access:" under the "Basic settings" section. Permissions are defined in hook_perm() in the .module file. If you want permissions dependent on, say, an argument--like you want to check that the current user (user 12) is a friend of the user whose statuses appear at user/17/status--then you can click on the argument in question ("User: Name" in this case) and edit the validation code in PHP.

Your question is not directly related to FBSS, but rather to Views and module construction in general. In the future, please direct this kind of question to the relevant support queues.

carlmcdade’s picture

Sorry about that. But in asking questions about views access I was referred to using views within nodes and then given advice on finding out how the view was implemented within FBSS. Though not a direct topic it goes to not knowing or finding how access is implemented in FBSS views. You answered my question perfectly.

icecreamyou’s picture

Happy to help.

Status: Fixed » Closed (fixed)

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