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 |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 12 replies, has 3 voices.
Last updated by 4 years, 2 months ago.
Assisted by: Christian Cox.
Okay I apologize for the confusion. I misunderstood how you have this set up. First, the system needs to know which terms are assigned to the current post. A View is the best way to handle this. You should create a View of the taxonomy that includes the roles-permitidos field. In your description, it sounds like this is the Category taxonomy. Add a Query Filter by term, where the term is set by the post where the View is shown (see the screenshot here for an example of this Query Filter). In the loop of this View, add your conditional to test the roles-permitidos termmeta value against the current User's role:
[wpv-conditional if="( '[wpv-current-user info="role"]' eq '[types termmeta="roles-permitidos"][/types]' )" debug="true"]I have the role [wpv-current-user info="role"], and the term [wpv-taxonomy-slug] has the same roles-permitidos value of [types termmeta="roles-permitidos"][/types][/wpv-conditional]
Then place this View in the Content Template assigned to this post.
Is it possible that multiple terms can be assigned to one post? If so, then this solution may produce duplicate post content. For example, if term A and term B both have the roles-permitidos field value "administrator", and both terms are applied to the same post, then the post content will be displayed twice for administrators because the View loops over all terms assigned to the current post. In this case, you need some more complex logic. What if term C has the roles-permitidos field value "basic" and terms A, B and C are all applied to the same post? What will an administrator see? What will a basic User see? Multiple terms assigned to the same post could make things very confusing here.
If you only care about the role "administrator", then you can use a View with a Query Filter on the roles-permitidos term meta field, with a limit of 1 post, as shown in this screenshot. You can place a conditional that only tests the User role inside the wpv-items-found section of the View, outside the wpv-loop tags.
[wpv-conditional if="( '[wpv-current-user info="role"]' eq 'administrator' )" debug="true"]I have the role [wpv-current-user info="role"], and the term [wpv-taxonomy-slug] has the same roles-permitidos value of [types termmeta="roles-permitidos"][/types][/wpv-conditional]
Okay, we must expand the solution to work for users with roles basic and premium, as well as administrator. In this case, you will configure the Query Filter I mentioned in my last comment to respond to a shortcode attribute like role. This will limit the terms in the View to those with the same roles-permitidos field value as the current logged-in User's role. You should also include a term filter set by the post where the View is shown. This will further limit the terms to only those associated with the current post. The combination of these Query Filters will have the effect that you desire. Content will only be displayed if one of the terms applied to the current post has the roles-permitidos field value identical to the current User's role slug. See the updated screenshot here for an example of both Query Filters you should apply to this View of taxonomy terms.
In the View's Content Selection panel, be sure to include each of the 3 taxonomies that contain the roles-permitidos field. Based on your description, this includes the world, food, and music taxonomies.
Next, in the loop editor, you should add the content you wish to display anywhere inside the wpv-items-found section. If you set the View's Limit to 1, only one result will ever be returned so you can add the content inside the wpv-loop tags. You may remove the "no items found" message if you'd like, or change it appropriately.
Next, insert this View in the post or the Content Template applied to the post type where you want to display the conditional content. You must pass the current logged-in User's role information into the Query Filter using a nested shortcode in the "role" attribute. Here is an example shortcode:
[wpv-view name="Your taxonomy term View" role="[wpv-current-user format='meta' info='role']"]
Replace Your taxonomy term View with the name or slug of the View of taxonomy terms you have created.
If you want to hide the content from all other User roles, including guests, you should add a conditional around that View shortcode to prevent content display for an edge case when the roles-permitidos term field of all applied terms is empty:
[wpv-conditional if="( '[wpv-current-user info="role"]' ne '')"] [wpv-view name="book-taxes" role="[wpv-current-user format='meta' info='role']"] [/wpv-conditional]
This solution assumes:
1. A single User will only ever have one role.
2. Users with none of those three roles should see no content.
The topic ‘[Closed] types termmeta comparison in conditional output’ is closed to new replies.
