Problem:

How to use Toolset conditional block?

Solution:

You can follow our document to setup the conditional block:

Relevant Documentation:

https://toolset.com/course-lesson/using-toolset-conditional-block/

Problem:
Setting up a filter for a custom user role field - how to filer and display WooCommerce orders based on different role

Solution:
You can pass the role name as view's shortcode argument and then use the 'wpv_filter_query' filter to filter the orders based on the passed role.

You can find the proposed solution in this case with the following reply:
https://toolset.com/forums/topic/setting-up-a-filter-for-a-custom-user-role-field/#post-2258051

Relevant Documentation:
- https://toolset.com/documentation/programmer-reference/views-filters/#wpv_filter_query

Problem:

Checking fields and other elements for Empty/Non-empty Values

Solution:

You can follow our document to setup the wpv-conditional shortcodes, check the custom field value isn't empty, then display the result:

Relevant Documentation:

https://toolset.com/documentation/legacy-features/views-plugin/checking-fields-and-other-elements-for-emptynon-empty-values/

Problem:
The issue here is that the user wanted assistance to compare 2 Toolset Types date fields and hide a section of their content if both date fields are equal.

Solution:

It should be noted that Toolset date fields are stored as timestamps so this will be an exact comparison depending on the precision of the date field. What I mean is that if you set the field to datetime then the dates and the times of both fields must match exactly.

Once you can confirm this then you will be able to compare them below using the timestamp.

[wpv-conditional if="( $(date-aa) eq $(date-bb) )"]
<!-- content to conditionally show goes here -->
[/wpv-conditional]

Should it be a case where the fields have the same date but different times then you can use the format below.

This will do a comparison based on the human readable date only.