Problem:
Font Awesome icons are not working, because of a version clash between Toolset (v4) and the theme (v5).
Solution:
We haven't updated our plugins yet, but you should be able to use the following code to resolve the problem.
It dequeues/deregisters the existing font awesome stylesheets (where both Toolset and another plugin or theme have registered different versions with the same handle), so that you can re-register the stylesheet for Font Awesome version 5.
You'll need to locate the source of the font awesome stylesheet you want to use (e.g. from your theme) and edit the code below to use that source.
function fix_different_version_same_handle_script() {
//Dequeue/Deregister any conflicting script
wp_dequeue_style( 'font-awesome' );
wp_deregister_style( 'font-awesome' );
//Re-enqueue the desired script with a different handle - change $src adequately)
wp_enqueue_style('font-awesome-compatible', get_template_directory_uri() . '/assets/font-awesome-v5/css/fontawesome-all' . $min . '.css');
}
add_action( 'wp_enqueue_scripts', 'fix_different_version_same_handle_script', 20 );
Problem:
Views by default disables the Avada CSS and JS compilers to create files for dynamic theme styles (they are inlined instead), but the client doesn't want that.
Solution:
When Avada is active we have now added a setting for this at Toolset > Settings.
I crafted some Custom JS Code and added it to the Custom Filter JS Section.
It works fine, but as soon I either paginate or update my search results with AJAX, the Custom JS Code does not work anymore.
What can I do?
Solution
You can add your code at specific moments of the AJAX process.
When you open the JS Section of the Custom Filter Editor you will see a „Front-end Filter“ button.
When you click it you see several options, each representing a moment of the AJAX process.
Choose the moment you desire to re-fire your Custom JS Code, and insert.
After, insert your custom function to be called within the just added JS Filter.
Problem: I would like to filter a View of Locations using start and end date custom fields in a child Event post, so that the View shows only Locations having Events that overlap with today's date. In other words, show only Events occurring today.
Solution: There's not an easy way to filter a View of post type A by custom fields in post type B, even if a parent/child relationship exists. I can offer some assistance with a View showing Events whose start and end dates intersect with a User-selected date. Then I can explain your options for getting Location information from those matching Events.
- First, create a View of Events. In the Filter editor panel, insert a filter on your start date custom field. If you cannot see the filter editor panel, scroll to the top of the View editor screen in wp-admin and click "Screen Options" in the top right corner. Check the box to display the Filter Editor panel. Configure the filter to show all Events with start dates greater than or equal to TODAY(), comparing values as numbers. The resulting shortcode will look something like this:
- In the Loop Output area, display the title, start, and end date of each matching Event for testing purposes.
- Next, add some custom code to your child theme's functions.php file:
add_filter( 'wpv_filter_query', 'default_today_inclusive', 10, 3 );
function default_today_inclusive ( $query, $view_settings, $view_id ) {
if( $view_id == 12345 ) {
// defaults
$selected_start = strtotime('0:00:00');
$selected_end = strtotime('23:59:59');
// if user selected a start date, update the default selected values accordingly, and unset existing start meta query
if ( isset($query['meta_query']) ) {
foreach($query['meta_query'] as $key => $meta) {
if(isset($meta['key']) && $meta['key'] == 'wpcf-start'){
// get timestamps that represents 12:00 am and 11:59:59 pm on the event start date
$selected_start = strtotime(date('m/d/Y', $meta['value']) . ' 0:00:00');
$selected_end = strtotime(date('m/d/Y', $meta['value']) . ' 23:59:59');
unset($query['meta_query'][$key]);
}
}
}
// find events with start date less than or equal to selected date
// and end date greater than or equal to selected date
$args = array(
'relation' => 'AND',
array(
'key' => 'wpcf-start',
'value' => $selected_end,
'compare' => '<=',
'type' => 'numeric'
),
array(
'key' => 'wpcf-end',
'value' => $selected_start,
'compare' => '>=',
'type' => 'numeric'
)
);
// add these arguments to your meta query
$query['meta_query'] = isset($query['meta_query']) ? $query['meta_query'] : [];
$query['meta_query'][] = $args;
}
return $query;
}
- Replace 12345 with the numeric ID of this View. If your field slugs are not "start" and "end", then the keys "wpcf-start" and "wpcf-end" should be updated as well. Add the "wpcf-" prefixes here.
- Show the parent Location information in the View.
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.
