This was more challenging than I expected. Working on a test site to implement this, I established that there is a problem with the legacy wpv-control shortcode which means it cannot be used for this. (That shortcode has subsequently been replaced with specific shortcodes for custom field or taxonomy filters.)
Instead of using the wpv-control shortcode it is necessary to add the markup for a form input manually.
It is possible to add the necessary markup to the View search section (via a Custom HTML block if using the block editor, or directly if using the legacy View editor), but in the solution I'll share below we will register a custom shortcode to generate the control dynamically.
Even then, there is a problem with our plugin code that effectively prevents adding custom filter controls. (We have shared solutions in the past, but they only work the first time you set a value for the filter; if you update the value and reload the page, multiple matching url parameters are added to the url and the filtering breaks. I don't know if it used to work and broke, or the users employing this solution didn't notice that it only works the first time.)
So, I am proposing to our developers a simple change in our plugin code that will enable this to work. Until such a change is made, you will need to edit the plugin code directly (I'll try to make sure the proposed changes are included in the next plugin update so that you don't have to keep editing the plugin files).
Before going any further, please edit this file: wp-content/plugins/toolset-blocks/embedded/inc/wpv-filter-embedded.php (or wp-content/plugins/wp-views/embedded/inc/wpv-filter-embedded.php if you have Views installed instead of Blocks).
Update line 1147 so that it matches this:
$query_args_remove = apply_filters( 'wpv_filter_query_args_remove', wp_list_pluck( $view_url_data, 'attribute' ), $view_id );
Now that you have made that change it is possible to add a custom filter control to your View.
There are 3 parts to the solution:
1. register a custom shortcode to generate the filter control (including maintaining the currently selected filter value) (and insert this shortcode in the Views filter control section)
2. add a filter to tell Views to strip the custom filter url parameter from the form action so that updating the filter does not append multiple versions of the parameter to the url
3. modify the query generated by the View to use the value from the custom filter
The custom code for steps 1, 2, and 3 can all go in the same code snippet, which you can add at Toolset > Settings > Custom Code, but I will share it in discrete sections below.
1. Register the shortcode
/**
* Register shortcode to generate custom filter control
* for post date
*/
add_shortcode("post-date-filter", "post_date_filter");
function post_date_filter() {
// retain which option is selected
$selection = (isset($_GET['post-date-filter']) ? $_GET['post-date-filter']: '');
$options = [
'Any date' => '',
'Today' => '1 day ago',
'Last week' => '1 week ago',
'Last month' => '1 month ago',
'Last year' => '1 year ago'
];
$out = "<select name='post-date-filter'>";
foreach( $options as $display => $value){
$out .= "<option " . selected($value, $selection, false) . " value='$value'>$display</option>";
}
$out .= "</select>";
return $out;
}
Pay careful attention to the option values, such as "1 month ago". WordPress date queries are quite flexible when it comes to interpreting date-like strings, based upon strtotime.
See hidden link and https://developer.wordpress.org/reference/classes/wp_query/#date-parameters
Insert this shortcode where you want the filter control to appear (in place of the wpv-control shortcode you have been using up until now).
2. Prevent the url parameter being added multiple times
/**
* Exclude the custom parameter from the search form action
*/
add_filter( 'wpv_filter_query_args_remove', function( $query_args_remove ){
$query_args_remove[] = 'post-date-filter';
return $query_args_remove;
}, 10, 1);
If you are modifying this code, note that 'post-date-filter' must match the same in the first section of code.
3. Modify the query to use the filter value
/**
* Modify the View query based on the custom filter value
*/
add_filter( 'wpv_filter_query', 'ts_custom_date_filter', 101, 3 );
function ts_custom_date_filter( $query_args, $view_settings, $view_id ){
if ( $view_id == 123 && isset( $_GET['post-date-filter'] ) ){
$query_args['date_query'] = array(
'after' => $_GET['post-date-filter'],
'column' => 'post_date' // or use post_modified for when post was last updated
);
}
return $query_args;
}
Again, 'post-date-filter' must match the previous code, and you will also need to edit the ID of the View this should apply to (123 in the example above).
I've tested that thoroughly and expect it should work as needed, but please let us know either way.
