I was trying to update my calendar module, which also required the Date module, ctools, and views to be updated. I now get this when I go to the status link (http://localhost/drupal2/admin/reports/status) This error occurs on several other screens also.
Fatal error: Call to undefined function date_field_get_sql_handler() in C:\wamp\www\drupal2\sites\all\modules\signup\includes\date.inc on line 330
Here is the call stack:
1 0.0005 368064 {main}( ) ..\index.php:0
2 0.8805 42878000 menu_execute_active_handler( ) ..\index.php:21
3 2.7808 54013424 drupal_deliver_page( ) ..\menu.inc:518
4 2.7809 54013688 drupal_deliver_html_page( ) ..\common.inc:2438
5 2.9910 60055456 drupal_page_footer( ) ..\common.inc:2550
6 2.9971 60055560 system_run_automated_cron( ) ..\common.inc:2577
7 2.9972 60055640 drupal_cron_run( ) ..\system.module:3472
8 3.6982 60716712 module_invoke( ) ..\common.inc:5050
9 3.6982 60716920 call_user_func_array ( ) ..\module.inc:794
10 3.6982 60717056 signup_cron( ) ..\module.inc:0
11 3.6993 60756512 _signup_cron_send_reminders( ) ..\signup.module:177
12 3.6994 60756952 signup_reminder_sql( ) ..\cron.inc:22
13 3.6996 60757000 _signup_date_reminder_sql( ) ..\scheduler.inc:125
Comment | File | Size | Author |
---|---|---|---|
#7 | 1452920.patch | 2.61 KB | BTMash |
#2 | signup_quick_hack.patch | 2.82 KB | pezia |
Comments
Comment #1
pezia CreditAttribution: pezia commentedAccording to date changelog: "Remove date_field_get_sql_handler() function which isn't being used anywhere."
This is causing the problem.
As a quick hack I copied the original function, so the website can function until a proper fix is done.
Comment #2
pezia CreditAttribution: pezia commentedComment #3
flightrisk CreditAttribution: flightrisk commentedWhere will the fix need to happen? In the signup module? Will it have to look through how the date module is now doing things and find an all new way to handle the timezone and date calculations to send the reminders? Who is going to have to make then change and when?
Comment #4
hyerstay CreditAttribution: hyerstay commentedI went thru the same thing. You have to update sites/all/modules/signup/includes/date.inc
Comment #5
dwwUgh. Yeah, I guess signup needs to figure out the new way to do date + timezone calculations given the latest date.module release. If anyone can do a little more Git archeology or other research in the date.module codebase to figure out how to achieve the same things, that'd be great. I'd be reluctant to just put a clone of date_field_get_sql_handler() into signup.module since perhaps date.module's underlying data representation is going to change and break us again. I'd rather just try to keep up with date.module's recommended API (if possible).
Thanks,
-Derek
Comment #6
VanD CreditAttribution: VanD commentedConfirming that this bug exists and that the patch from #2 solved the problem for me.
Comment #7
BTMash CreditAttribution: BTMash commentedI can confirm the patch works as well. The code also looks good. I am rerolling the patch so it should actually apply but am also marking it at RTBC.
Comment #8
BTMash CreditAttribution: BTMash commentedAnd I am changing to critical since it results in cron being unable to run on the server.
Comment #9
linuxbcn CreditAttribution: linuxbcn commentedI apply the patch (in local first and update by ftp) and the error don't apear in the bottom of the page.
But when I try to send an mail by Forward options apears this message:
Recoverable fatal error: Argument 1 passed to drupal_http_build_query() must be an array, string given, called in /home/MySERVER/public_html/dev/includes/common.inc on line 2192 and defined a drupal_http_build_query() (línia 477 de /home/MySERVER/public_html/dev/includes/common.inc)
.Is just another error?
Comment #10
BTMash CreditAttribution: BTMash commented@linuxbcn, sigh - seems like this is another error though, unfortunately, it is not related to this particular error :( Would you mind posting an issue for the error you get?
Comment #11
linuxbcn CreditAttribution: linuxbcn commentedNo problem, i'll create a brand new issue.
But i'm making some test and I think is just an error with forward Module, not this.
I sent-it to apropiate bug report fo this.
sorry
Comment #12
rurri CreditAttribution: rurri commentedHad same issue. Patch fixed it for me.
I think this is the best way to handle this for an immediate fix, that is pretty safe.
Comment #13
mbeenon CreditAttribution: mbeenon commentedHeres the patched version:
Comment #14
daniel-san CreditAttribution: daniel-san commentedApplied patch #2 with success. Thanks for the work on this module.
Correction, I did not get success with the patch.
Hoping the following updates can help this issue along.
I continue getting 500 errors on nodes that have signup enabled and a date field. I can create nodes with a date, enable signup on the node and everything seems fine, but then if I come back to the node, click edit and then click View tab or save the node, I get a 500 error. I applied the patch in #2 and, at first, I thought everything was working fine, but then it started happening again. I will continue testing my setup to see if I can pinpoint a bit more.
As of July 24, 2012, I'm using:
Signup 7.x-1.x-dev
Date 7.x-2.5
Views 7.x-3.3
UPDATE
Ok, I can have everything working great until I add the date field to a view that lists my events. After that, if I go to the view and click the node title I get a 500 error. I can go directly to the edit page of the node, but from there if I save or click the View tab for the node, it errors.
Hope this helps.
Comment #14.0
daniel-san CreditAttribution: daniel-san commentednoted that the error happens on page load for many admin screens
Comment #15
sgabe CreditAttribution: sgabe commentedLets just get this in to save some headache for people.