@naresh Vachhani
I have a patch for this but waiting on another user to confirm a different issue. should be released this coming weekend.
interesting note here on your comment
“Getting this error on the front end even if WP_DEBUG set to false.” this is not something controlled by Simply-Exclude. I know you know this so my comment is more for other users. If your hosting is displaying these PHP Warnings I would have them turn off PHP error_reporting as this can expose information about your hosting which can be used by others.
Another interesting issue on this reported fix. Per your correct suggestion the second function argument is optional and needs a default valid. What I find confusing is within the WordPress core there is only one call to the filter ‘get archives_where’. This is from wp-includes/general-template.php line 1374. It is this filter there Simply-Exclude hooks into and connects to the plugin function se_widget_getarchives_where().
If you view this this hook call (see below) you will see there is a second argument passed ‘$r’. So it is confusing as to why there is a need to have this set to a default value within the plugin code.
$where = apply_filters( ‘getarchives_where’, “WHERE post_type = ‘post’ AND post_status = ‘publish'”, $r );
P-