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.
[php]
[wpv-conditional if="( '[types field='date-aa' format='Y m j'][/types]' eq '[types field='date-bb' format='Y m j'][/types]' )"]
[/wpv-conditional]
[php]
This will do a comparison based on the human readable date only.
Problem:
Nested shortcode does not work inside elementor modules
Solution:
It seems the Elementor shortcode module you are using is not able to parse the nested shortcode.
Can you please try to follow the following steps:
- Create a new content template using Toolset (in classic mode, do not use block mode) and add the views shortcode to this content templates
- Save the content template and then try to add this content template shortcode to your Elementor's shortcode widget and check if that help you to resolve your issue.
The customer asked how the 'wpt_field_options' filter can be used to dynamically generate a long and alphabetically ordered list of options for a select type field.
Solution:
Shared some details and a code snippet example to show how this filter can be used to generate options from a custom post type:
add_filter( 'wpt_field_options', 'func_to_dynamically_populate_shop_locations', 10, 3);
function func_to_dynamically_populate_shop_locations( $options, $title, $type ){
switch( $title ){
case 'Book Shop Locations':
$options = array();
// add first empty value
$options[] = array('#value' => '', '#title' => '---');
// get all tmna-location post items
$args = array( 'post_type' => 'shop-location', 'posts_per_page' => -1, 'post_status' => 'publish','orderby' => 'title' );
$results = get_posts( $args );
if ( $results ) {
foreach ( $results as $post ) {
$options[] = array('#value' => $post->ID, '#title' => $post->post_title);
}
}
break;
}
return $options;
}
Problem: I would like to display a View only on non-mobile browsers. I tried using conditionals with wp_is_mobile in GP Hooks to display the View above the main content, but the View shortcode is just written out to the page. The View shortcode works without the Toolset conditionals.
Solution: Toolset's conditionals don't seem to function well in GP Hooks. Instead, you can use PHP conditionals directly.
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
