The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Hi,
Pardon me if this is not the right queue for this, but it's a problem between several modules, and I couldn't find this issue summarized anywhere else: this module seems like the linchpin, so I'm posting it here. Basically, I'm using Search API views, and while I can retrieve filter and retrieve dates, there's some sort of metadata or schema mismatch which causes certain displays not to work. I've tried both the Calendar and FullCalendar modules, and neither seems to detect date fields from the search index.
For FullCalendar, I get the helpful message: 'Display "Page" requires at least one date field.', regardless of whether I use a built-in date field, such as created date, or a custom field of date type. I've attached a screenshot demonstrating what I mean.
I'd really like using Search API for faceted browsing, and the ability to use multiple displays, including ones which need heavy interaction with Dates, would be great.
I'd be willing to try to create a patch, but don't understand the interaction well enough to know where to start. Can anyone offer some advice on how I might track this down?
| Comment | File | Size | Author |
|---|---|---|---|
| Screen Shot 2013-04-24 at 11.07.04 AM.png | 104.27 KB | noahadler |
Comments
Comment #1
gmclelland commentedMultivalued date fields won't work for SearchApi with Solr. It does work with Single valued date fields, but you need to use the latest version of Search Api.
There is an issue somewhere for SearchApi about this.
Hope that helps.
Comment #2
torgospizzaI am experiencing this issue as well.
I created a new Date field, which only accepts 1 value maximum for the field instance - making the Cardinality on the field "1" - however the type is still "list" and therefore incompatible with Search API Sorts and sorting in a Search API-based View. This appears to be a bug either in how Search API interprets multi-value fields, or a bug in Date API that does not provide the correct field data type consistently.
Ideas and suggestions are appreciated.
UPDATE: It appears this is possibly related to Commerce and how its Product reference field handles its referenced products' single-value Date (and other) fields. We are also indexing through Search API the product displays, rather than their products, which would make sense as to why the dates are then considered multi-value. (Because we allow >1 products to be added to the Display node's product reference field.)