Skip Navigation

[Resolved] Views Query Filter based on Access Post Group

This support ticket is created 7 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 23 replies, has 4 voices.

Last updated by Team DNK 6 years, 11 months ago.

Assisted by: Shane.

Author
Posts
#517471

Quick Final Question... And happy to finalize all this in the other thread if that is where you would like to do it. Also you may want to rename the other thread so it is of more help to others.

So by closing this thread, as this is quite a different approach from what you are proposing in the other thread, are you saying that these methods won't actually control posts from being displayed in a View based on their Access Post Group settings?

Thanks Beda,
Dave

#517630

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Dave,

Please ask this follow-up question in the ongoing thread with you and Beda as I will be closing this ticket.

Thanks,
Shane

#517634

Actually... This question should be answered here as it pertains to a much different approach to using Access Post Groups. Lets address the question so others can benefit from the answer then we can close the thread.

Sincerely,
Dave

#518012

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Dave,

Taking a look at the other thread the answer would be Yes, Access does not control the output of views so the access group setting is not respected.

Thanks,
Shane

#518026

Trying so hard to be patient here... The entire purpose for this thread is because of what you just stated. The below are the two Toolset suggested approaches I have been trying to implement and were the bases behind this thread. As for the other thread it was not intended for unpacking the solution to the need but non the less what is being explored as it pertains to Conditionals is promising but requires some further explanation as well.

Please, please, please put this thread in the hands of someone who can address the specific Toolset Recommendations represented here.

REFERENCE 1
Here is links to similar requests.
https://toolset.com/forums/topic/how-to-limit-display-of-posts-to-users-within-the-current-access-group/

REFERENCE 2
Below is a link to a rather lengthy thread where Toolset support person "Christian" addresses a similar need as part of a much larger request. For your convenience I also provided an excerpt from the specific section of that thread which pertains to my request.
https://toolset.com/forums/topic/using-access-user-fields-to-filter-views-for-logged-in-users/

INQUIRY: These private "project posts" should only be visible to the staff who are members of that specific project group. Members of Project A should not be able to see documents or posts about Project B. Some staff may be members of both A and B. There may be lots of project groups, so with all the various possible combinations of membership, it would be silly to try to create separate Roles for these? A simple user group called Groups, with the tick box for each group will suffice, yes?

CHRISTIAN: Toolset Access limitations can be based on user role, or on the individual user - but not on a user group. This means that you would need separate user roles for each combination of project groups to be able to fully manage this from the WordPress admin area and take full advantage of Access's restrictions interface. If you are able to write custom PHP, it's possible to use the wpv_filter_query function to modify your WordPress queries and restrict the responses to those post groups to which a user has access. More information about that function can be found here:
https://toolset.com/documentation/user-guides/views-filters/wpv_filter_query/

#519083

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Dave,

As I gather the issue in this thread is already being handled by Beda since it was being referenced in the thread below.
https://toolset.com/forums/topic/important-need-senior-level-assistance/

So essentially it is a duplicate being handled by our 2nd tier supporter.

Please raise any concerns that you may have in this thread to the one here
https://toolset.com/forums/topic/important-need-senior-level-assistance/

This is because a senior level supporter is already on the case.

Thanks,
Shane

#519084

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Beda will be able to address any concerns you may have.

#519116

Not resolved but yes as of a couple days ago, Beda is now addressing the original inquiry April 19, 2017 at 7:37 pm in another thread.

#519121

I am closing the thread.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.