I get this error message on a blank white page when trying to expose a grouped filter with checkboxes.
Fatal error: Cannot create references to/from string offsets nor overloaded objects in path/includes/common.inc on line 6548
I am trying to display a database table with some exposed filters. If I try to use a filter with checkboxes, it displays properly the first time I load the page. If I check off one of the boxes,it still works, but once I uncheck the box and click apply, the error message is generated on a blank page. Once the error message appears, it continues to appear 100% of the time when I go to that page.
If I add enough items to the filter, the filter becomes a scrollbox and the problem disappears.
Alternatively, if I manually enter a parameter in the url ( eg instead of http://domain.com/page, I type http://domain.com/page?items_per_page=50 or add any other valid parameter ) the page displays properly even if I'm still using checkboxes.
I've installed a clean drupal 7.22 core and added the views, data, ctools, schema, and entity modules. I've tried installing 3 times and I get the same results every time.
The function throwing the error is:
function drupal_array_set_nested_value(array &$array, array $parents, $value, $force = FALSE) {
$ref = &$array;
foreach ($parents as $parent) {
// PHP auto-creates container arrays and NULL entries without error if $ref
// is NULL, but throws an error if $ref is set, but not an array.
if ($force && isset($ref) && !is_array($ref)) {
$ref = array();
}
$ref = &$ref[$parent]; <--- this is line 6548
}
$ref = $value;
}
Any thoughts on what's going on?
I've only started using drupal a few days ago so don't know very much at this point. Any help appreciated.
Comment | File | Size | Author |
---|---|---|---|
#25 | 1995056-Fatal-error-4_0.patch | 517 bytes | bpleduc |
| |||
#23 | 1995056-Fatal-error-4_0.patch | 527 bytes | bpleduc |
| |||
#6 | 1995056-Fatal-error-4.patch | 517 bytes | marvin_B8 |
#4 | 1995056-Fatal-error-4.patch | 644 bytes | marvin_B8 |
Comments
Comment #1
marcingy CreditAttribution: marcingy commentedComment #2
wiherek CreditAttribution: wiherek commented+1
I dpmed $ref and the grouped filters differ from the others in that they include nested arrays.
Comment #3
nothinghere CreditAttribution: nothinghere commented+1
I have this problem too.
Any solutions ?
Comment #4
marvin_B8 CreditAttribution: marvin_B8 commentedA small patch to fix the problem.
The problem is $this->exposed_data contains the raw data for example the time and not the seperated values like month and year.
$this->exposed_input contains the right values for the SESSION.
Comment #6
marvin_B8 CreditAttribution: marvin_B8 commentedComment #7
kari.kaariainen CreditAttribution: kari.kaariainen commentedThis patch worked for me. No more WSOD. Just had to logout first.
Comment #8
kari.kaariainen CreditAttribution: kari.kaariainen commentedComment #9
dawehner@kari.kaariainen
You talk about no WSOD but do exposed filters still work for you?
Comment #10
kari.kaariainen CreditAttribution: kari.kaariainen commentedYes. I created a view with exposed filters (user could select days and months), got a WSOD and this error message at the log. Every other page worked fine, only the view page was crashing. I then found this issue, changed that one row, and no more WSOD and the exposed filters work fine.
Comment #11
redsky CreditAttribution: redsky commentedI had a similar problem using multiple checkboxes in an exposed filter. (Same error). I applied patch #6 against Views-7.x-3.7.
Initially it did not appear to solve my problem. I logged out as suggested in comment #7 and then it worked only once before I got the error. This got me to thinking it might be related to the "Remember" checkbox. (Remember the last setting the user gave this filter.)Everything worked fine after I turned that off. I removed the patch and everything continued to work fine.
Comment #12
kari.kaariainen CreditAttribution: kari.kaariainen commentedI have applied the patch and I have the "remember" checkbox on and it's working fine.
Comment #13
workplaysleep CreditAttribution: workplaysleep commentedConfirm that patch #6 solved the same problem with views 7.x-3.8
Comment #14
jelo CreditAttribution: jelo commentedI had this issue with an exposed date field and operator "in between". Start date was set relative to now and end date relative to now +1 year. In the settings the allowed starting year was 0 and the end year +1 year. In theory this should work fine and it did if a user just used the exposed UI options. It would show Feb 2015 as start and Feb 2016 as end with the ability to change the months values, but in year it would only show 2015 and 2016.
However, as soon as someone manipulated the URL pattern to a year outside the allowed range, the error would be thrown. For now I simply changed the setting to allow values +/- 5 years and the error went away. However, now the dropdowns show the extended year range which is not great, but acceptable.
Comment #15
vaza18 CreditAttribution: vaza18 commentedThe patch attached to this topic resolves the issue for me: https://www.drupal.org/node/2313517
Comment #16
merauluka CreditAttribution: merauluka commentedI had this error and updated Date module to 7.x-2.9-rc1 and the error was resolved.
Comment #17
bjcooper CreditAttribution: bjcooper commentedThe patch in #6 seems to have done the trick for me.
Comment #18
drenton CreditAttribution: drenton commentedThe patch in #6 worked for me.
Comment #19
geek-merlinComment #20
lias CreditAttribution: lias commentedWill this be committed? I verified on my site as @kari.kaariainen #12 stated - my view was outputting this when I had the Remember box checked. Unchecked it no longer produced these errors.
Comment #21
kari.kaariainen CreditAttribution: kari.kaariainen commentedI bumped into this error and found my own messages here. I had patched Views and since updated and forgotten the patch. So now patched again and problem went away again.
Comment #22
colanWe've recently switched our testing from the old qa.drupal.org to DrupalCI. Because of a bug in the new system, #2623840: Views (D7) patches not being tested, older patches must be re-uploaded. On re-uploading the patch, please set the status to "Needs Review" so that the test bot will add it to its queue.
If all tests pass, change the Status back to "Reviewed & tested by the community". We'll most likely commit the patch immediately without having to go through another round of peer review.
We apologize for the trouble, and appreciate your patience.
Comment #23
bpleduc CreditAttribution: bpleduc as a volunteer commentedPatch solves issue for me as well.
Re-uploading patch as requested.
Comment #25
bpleduc CreditAttribution: bpleduc as a volunteer commentedFailed due to white space. Re-uploading.
Comment #26
bpleduc CreditAttribution: bpleduc as a volunteer commentedComment #27
joelpittetBack to RTBC as per #21 patch is identical.
Comment #28
peterlolty CreditAttribution: peterlolty commentedRTBC +1 for #25 patch
Comment #29
dready2011 CreditAttribution: dready2011 commentedThe patch #25 solved the issue for me too.
Comment #30
dang42 CreditAttribution: dang42 as a volunteer commentedJust had the same issue, #25 worked for me.
Comment #31
mvdve CreditAttribution: mvdve commentedTested patch #25 can't find any issues. Please commit.
Comment #32
Jorge Navarro CreditAttribution: Jorge Navarro commented#25 worked for me too.
Comment #33
attiks CreditAttribution: attiks at Attiks commented#25 Works like a charm
Comment #34
DamienMcKennaCommitted. Thank you.
Comment #37
joseph.olstadThis commit caused a regression
see: #2961962: Reset of Exposed Published Status filter with "Remember last selection" results in: Undefined index: status in views_handler_filter->store_exposed_input()