The value I type into an exposed date filter textfield is sent to date_views_filter_handler with $value set to the text I've entered, e.g. 'Nov 6 2007 - 9:13pm' and $type set to 'DATE'.

As there's no switch case to handle type 'DATE', it's passed to the default: code which rejects it as it's not a valid Unix timestamp or an ISO date.

If I add

    case 'DATE':
      break;

to the switch statement (OK, some validation would be good, but I needed this to work quickly) everything works perfectly; otherwise the 'WHERE...' clause doesn't get added to the SQL and the filter has no effect.

I'm using Content 5.x-1.6-1 and Views 5.x-1.6

Comments

diricia’s picture

diricia commented

Work around:

Install the daterange module. This works well and is more useful. Dates have minutes and seconds thus it is better to search for a range.

karens’s picture

karens commented
Status: Active » Closed (won't fix)

I'm not making changes to the 5.1 version. I'm officially recommending you move to the 5.2 version now. If you have problems in that version you can check for existing issues or add new ones. Feature requests are now getting posted to the D6 version to be back-ported to 5.2.

There have been lots of improvements to Views handling in 5.2.