Views 3 support

In the Views argument options when you set the 'Validator' to 'Privacy Per User' it will add an additional select menu below it labeled 'Privacy Type'. If you have previously defined a privacy type it will appear in the menu and you can choose it.

Use the UI at 'admin/build/privacypu' to create, edit, and manage your privacy types.

Can you clarify what is happening? When you select 'Privacy Per User' as the validator does a 'Privacy type' select element appear? If it does is there anything in that menu? Which version of Views are you using?

That sounds like the issue then. I have only tested this with Views 2. I changed the title of this issue to better reflect the problem.

Someone, probably me, needs to update Privacy Per User to work properly with Views 3.

Give this a try.

Technically it should be marked 'reviewed & tested by the community' if it works. It should only be marked 'fixed' when it has been committed.

I have applied the patch and it does not appear to be working for me. Prior to patching, the 'Privacy Per User' validator option was appearing but it did not have a privacy type selection per this issue thread. After patching, the 'Privacy Per User' validator option is not a visible option in the select list. Both instances were using a User: UID argument on Views 6.x-3.0+50-dev from 02-22-12.

I'm not very familiar with the Views API and am not sure where to start, but I do see that there appears to be some fundamental changes to the approach between the Views 2 and 3 integration.

Vishun, yea we are seeing the same result here as well.. wonder why its not working, maybe something in views changed a bit..

Hmm, I'm not able to replicate the issue that you are both seeing with the patch. Are there any more details that either of you can provide that might shed more light on this?

Not entirely sure what else to check that may shed some light, but will try increasing the error reporting and checking the logs to see if there are any notices or anything that might give insight. Will also try to get setup on a fresh install to make sure that there isn't something else at play, which is likely the case if you've got it working elsewhere.

While this would still be a great option to have, realized that this sort of views integration isn't exactly what we're looking for. It appears that the present views integration might be used to hide a whole view, while we're looking to hide only individual row results from a view. For instance, a list of users where one of the users has a privacy setting that should make them not appear in this list. I'm still trying to figure out what my question is and how to best go about it, but if you have any suggestions or recommendations, all ears and would love to contribute back anything that gets figured out on this goal.

Let's open a separate issue for filtering users from a list based on privacy settings. I think it is probably a good idea, but will distract from the original issue if we start discussing it here.