Expose Date Range Filter with missing min or max returns all results

Please find the following patch for the issue.

Patch #2 is nice. Thx for that.
It works for me.
Now, If both Min & Max date are entered, results are returned within the range selected. If either are missing, all results are returned this condition is working as expected.

Patch #2 applied cleanly on drupal 9.x.3-dev version for me and resolved the issue.
Thanks for the patch.

This is only working if we set MAX with empty MIN.
With MIN set and empty MAX, the condition is "BETWEEN MIN_DATE AND 0" so there is no result.

When only min is set, condition should be ">= $a" and not "BETWEEN $a AND $b"

The patch doesn't work if the min value exists and max is empty.

Fixed CS issues

The patch was not complete, so I added support for datetime module, and not between operations.
And added a related issue from the integer filter variant.

I removed this:

    // Although both 'min' and 'max' values are required, default empty 'min'
    // value as UNIX timestamp 0.
    $min = (!empty($this->value['min'])) ? $this->value['min'] : '@0';

As it makes no sense currently for me, in that moment and time we have a string date, and not a timestamp.
Originates from: https://www.drupal.org/project/drupal/issues/2627512

Wrong condition fix when both times set.

Yeah, works on my end. I've added the tests.

Applied patch #2 in drupal-9.3.x-dev applied successfully and fix the issue
Thanks for the patch
for ref sharing screenshot...

#18 tested and looks fine.

Thanks for fixing this.

This needs to be on 10.0.x now, changing version. The patch includes a test so removing tag.

A brief look at the patch and I notices these two items.

1. +++ b/core/modules/datetime/tests/src/Kernel/Views/FilterDateTest.php
   @@ -140,6 +140,37 @@ class FilterDateTest extends DateTimeHandlerTestBase {
   +      // Test offset for between operator when only min is set. 'Yesterday' and
   

   I think this should be max.

2. +++ b/core/modules/datetime/src/Plugin/views/filter/Date.php
   @@ -105,21 +105,33 @@ class Date extends NumericDate implements ContainerFactoryPluginInterface {
   +      // Convert to ISO format and format for query. UTC timezone is used since
   +      // dates are stored in UTC.
   

   This comment should now be above the whole if block since it applies to all 3 paths.

I applied the patch to 9.5.x and did some testing. I added a date field to the article content type and then made a view with two exposed filters, one on the added date field and the other on the authored on field. I used devel generated content with authored dates going back for a year. I added a date to two node.
I did not do exhaustive testing. The date field appeared to work with offset and date. The authored on field worked with dates but failed with just a minimum offset. And min offset of '-3 days' failed to show any nodes but a min of '-3 days' and a max of '-2 days' would show the correct nodes.

Setting to NW.

I tried to fix the changes mentioned in #24. Please have a look.

This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request as a guide.

The issue summary needs to be updated with proposed solution.
CI failures in #25

It's weird, i've tried all of the patches and none seems to works, i've tried on 9.3.22 , 9.4.11 and 9.5.3.

I'm getting the same results as @hhvardan and #Raphael Apard only max works alone, if i use only min i get no results.

This issue is also solved in https://www.drupal.org/node/2982968

Hello,

@camilo.escobar : I've try to use your patch in issue #2982968 but it's return an error.
I will add a comment on your issue in order to trace the error.

The patch #25 seems to work on Drupal 10.2.2.

Cheers.

Patch from #25 also works for me on Drupal 10.2.6

Updated patch that applies to Drupal 11.2

Created MR based on 3202489-32.patch. Re-roll for changes in 11.3.9, incorporating #3578444