Closed (fixed)
Project:
Date
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Mar 2008 at 03:11 UTC
Updated:
23 May 2008 at 12:21 UTC
Jump to comment: Most recent file
I get the following error when enabling Date-6.x-dev (HEAD) and CCK 6.x-1.x-dev
Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of [runtime function name](). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in C:\wamp\www\D6\sites\all\modules\date\date\date_elements.inc on line 118
Comments
Comment #1
skor commentedOh, running D6.1 on php 5.2.5 and mysql 5.0.51a
Comment #2
kriskd commentedhttp://drupal.org/node/242787
Comment #3
karens commentedI can't replicate this with latest HEAD. The HEAD tarball is out of date, you have to get the code directly from cvs to get the latest code. I'm going to try to create a beta release soon that you can use instead of that bad tarball.
Comment #4
yhager commentedI don't think this is fixed for HEAD - I think it depends on PHP configuration. This error is not displayed on my local install, but is displayed when used on my shared hosting account.
The attached patch follows the suggestion from http://drupal.org/node/242787#comment-815205 - it seems to be working fine, but I haven't tested functionality in full.
Comment #5
karens commentedFixed in latest commit. Thanks!
Comment #6
kriskd commentedI just downloaded and installed date-6.x-1.x-dev.tar.gz with a last update date of 5/8/08 and the field for Date is still not showing up. I ran update.php and that didn't remedy it either. Maybe I'm still doing something wrong?
Comment #7
karens commentedThe issue is about an error message and the error message should be gone. I have no idea what you mean when you say 'the field for Date is still not showing up.' That has nothing to do with this issue that I can see, and I have no idea what you mean. If you're reporting a different error, open a new issue and provide more information.
Comment #8
kriskd commentedSorry about that, Karen, I got a little ahead of myself! I had already participated in the appropriate issue queue about that one here:
http://drupal.org/node/246244
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.