Fatal error: Unsupported operand types in /hsphere/local/home/...../profiles/recruiter/modules/date/date_all_day/date_all_day.module on line 386
Fatal error: Unsupported operand types in /hsphere/local/home/...../profiles/recruiter/modules/date/date_all_day/date_all_day.module on line 386
Comments
Comment #1
karens commentedUnable to replicate this. I need more information about what you were doing when you got the message. Also, did you run update.php? And did you clear the caches?
Comment #2
vikingew commentedI also get this, after updating the module to latest dev and run update.php sucessfully, no matter returning to Admin or Frontpage results in a blank page and the above print in apache error log, except I get line 388 instead of 386 - and it's odd because that line just contains
and line 386 contains nothing unusual either, so it's all very strange...
Comment #3
kaizerking commentedJust installed and ran update.php got this error core is fresh install
Comment #4
drzraf commentedComment #5
drzraf commentedwith
var_dump($info['date_select']['settings']);die();at the beginning ofdate_all_day_field_widget_info_alter:Comment #6
drzraf commentedthe above comment is dumb, I should have said that
$info['date_popup']is NULLComment #7
vikingew commentedThis si a strange error indeed and although $info['date_popup'] is NULL due to this code in date.field.inc
I cannot see any syntactic problem with the error producing code as the array elements should simply be created, afaik but I'm no php guru so maybe I have got it wrong.
I noted something else though experimenting by simply remove obstructive code bit and I still got a blank page, but this time nothing was added to the error log and access log just produced 1 line as
[15/Dec/2011:17:36:22 +0000] "GET /?q=admin HTTP/1.1" 500 -This indicates to me that the actual error is elsewhere and more something in style with white space after a closing ?>
I rolled back to a previous snapshot and got it working again, then reapplied all module updates except date and all still working, so it must be with one of the new date files I assume. I will experiment further from there and see what i can find.
Comment #8
vikingew commentedI reapplied the latest dev but removed the 7002 update function that activates the date_all_day module and the site loads fine. But as soon as the module is activated it's back to blank page.
Comment #9
vikingew commentedOk so if Date Popup module is enabled it works to also enable Date All day, which means as code is now that the latter one depends on the former, and this is probably why some can't reproduce this.
EDIT: Unfortunately it appears as I was wrong, back to blank again and it doesn't even help to restore db backup with module disabled, a db that site worked when dumped.
Comment #10
rickmanelius commentedI commented out lines 386-388. Refreshed the page, then uncommented... all works!
Odd. It seems that something isn't set the first time this function is loaded/called.
Comment #11
rickmanelius commentedI spoke to soon. It came back upon flushing the cache system through the admin menu.
Comment #12
SirFiChi commentedSame here.
Update with drush up and i get a blank site with:
Fatal error: Unsupported operand types in /sites/all/modules/date/date_all_day/date_all_day.module on line 386Commenting out 386-388 brings the page back, so you are able to disable Date All Day...
Comment #13
karens commentedNo one actually said this, but does everyone having this problem have the Date Popup module disabled?
Comment #14
karens commentedI'm assuming that was the problem, committed a fix.
http://drupalcode.org/project/date.git/commit/8be3713
Comment #15
kaizerking commented@#13, In my case the date pop up was in disabled condition.
Comment #16
kaizerking commentedFixed error with the latest commit thanx