This thread is resolved. Here is a description of the problem and solution.
Problem:
How to add a filter to show only future events from the Events Calendar plugin in a View?
Solution:
The start date is stored as in the field "_EventStartDateUTC" but it is not stored in the timestamp format used by Types date fields, and to filter by this field you will need to use the wpv_filter_query hook.
Here is an example of such code (the View ID would need editing):
/**
* Filter event query to show future events
*/
function tssupp_filter_event_query($view_args, $view_settings, $view_id) {
if ( in_array( $view_id, array( 123 ) ) ) { // Edit View ID(s)
if (!isset($view_args['meta_query'])) {
$view_args['meta_query'] = array();
}
$meta_query = array(
'key' => '_EventStartDateUTC',
'value' => date("Y-m-d H:i:s"),
'type' => 'DATETIME',
'compare' => '>',
);
$view_args['meta_query'][] = $meta_query;
}
return $view_args;
}
add_filter('wpv_filter_query', 'tssupp_filter_event_query', 101, 3);
The thread also includes an example of code that would be used to filter between a range of dates.
Relevant Documentation:
https://toolset.com/documentation/programmer-reference/views-filters/#wpv_filter_query
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 |
|---|---|---|---|---|---|---|
| - | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | - |
| - | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | - |
Supporter timezone: Europe/London (GMT+00:00)
This topic contains 11 replies, has 2 voices.
Last updated by 6 years, 1 month ago.
Assisted by: Nigel.
I looked in wp_postmeta and see that the dates are not stored as timestamps (which is how Types date fields are stored, which is why the comparison should be number), but what looks like datetime (see screenshot).
Remove the Query Filter you added in the Views GUI and add one programmatically using the wpv_filter_query hook like so:
/**
* Filter event query to show future events
*/
function tssupp_filter_event_query($view_args, $view_settings, $view_id) {
if ( in_array( $view_id, array( 123 ) ) ) { // Edit View ID(s)
if (!isset($view_args['meta_query'])) {
$view_args['meta_query'] = array();
}
$meta_query = array(
'key' => '_EventStartDateUTC',
'value' => date("Y-m-d H:i:s"),
'type' => 'DATETIME',
'compare' => '>',
);
$view_args['meta_query'][] = $meta_query;
}
return $view_args;
}
add_filter('wpv_filter_query', 'tssupp_filter_event_query', 101, 3);
You'll need to edit the ID(s) of the View(s) you want this to operate on.
I'm surprised it doesn't work, it works correctly on my test site, so I'm not sure what to suggest aside from make sure you edited the ID of the View, and if you are still having problems, go to Toolset > Settings > Front-end content and turn on the debug mode for Views. Then reload the page with the View and in the pop-up check the wpv_query_filter arguments have been applied, as shown in the screenshot.
In that case I'm applying some modified code where I updated the code for a date range.
That code would look like this:
/**
* Filter event query to show future events
*/
function tssupp_filter_event_query($view_args, $view_settings, $view_id) {
if (in_array($view_id, array(189))) {
if (!isset($view_args['meta_query'])) {
$view_args['meta_query'] = array();
}
$meta_query = array(
'relation' => 'AND',
array(
'key' => '_EventStartDateUTC',
'value' => date("Y-m-d H:i:s"),
'type' => 'DATETIME',
'compare' => '>',
),
array(
'key' => '_EventStartDateUTC',
'value' => date("Y-m-d H:i:s", time() + 30 * 24 * 60 * 60),
'type' => 'DATETIME',
'compare' => '<',
),
);
$view_args['meta_query'][] = $meta_query;
}
return $view_args;
}
add_filter('wpv_filter_query', 'tssupp_filter_event_query', 101, 3);
If your View is showing two post types and one of the post types doesn't have the _EventStartDateUTC custom field then those posts will necessarily be excluded from the results.
