There are following errors displayed on search api views with exposed date filters on indexed dates:
Warning: Illegal string offset 'date' in drupal_array_set_nested_value() (line 6837 of /app/docroot/includes/common.inc).
Error: Cannot create references to/from string offsets in drupal_array_set_nested_value() (line 6837 of /app/docroot/includes/common.inc).This is because of changes introduced date module: #2449261: expects an array, not a scalar - Fatal error: Cannot create references to/from string offsets
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | search_api-search_api_views-exposed-date-3132404-9.patch | 1.69 KB | pobster |
| #2 | search_api-search_api_views-exposed-date-3132404-2.patch | 939 bytes | janadam |
Comments
Comment #2
janadamFollowing patch fixes this for date_popup exposed filters by setting
$form['value']['#id'],same as it is done in:
date_views/includes/date_views_filter_handler_simple.inc:320Comment #3
klausiMakes sense, thanks!
Comment #4
joseph.olstad@klausi the approach in number 5 of the related date module change is maybe better than random generating a form id but I could be wrong, could you test that please?
Comment #5
klausiAs said in the other issue: but this has now been released in date module (although just as beta), so I think we cannot change this to not break existing sites that rely on it. Should we still do the approach in #5? Probably best if you create a new issue and describe what the remaining fix should be and why.
Otherwise this change here is simple enough to keep I think.
Comment #6
drunken monkeyThanks for reporting this problem and providing a patch!
I’m not using the Date module, so have to trust you that this does what it should, but from looking at the code it seems fine. I just expanded the comment a bit and committed.
Thanks again, everyone!
Comment #9
pobster commentedBefore I open a new ticket ... should this (attached) not also have happened for this issue?