Active
Project:
Time Tracking
Version:
6.x-1.0-alpha1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Jul 2009 at 18:47 UTC
Updated:
26 Aug 2010 at 22:03 UTC
As the title says.
Fatal error: time_form_validate() [<a href='function.time-form-validate'>function.time-form-validate</a>]: The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "time_entry" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in .../modules/time/time.module on line 251
Comments
Comment #1
allie mickaIs this still reproduceable? How?
Comment #2
zilverdistel commentedSame problem here.
I'm setting up Atrium, and want to use time tracking in the case tracker. On the node it works, but trying to save a comment, I get the following error:
PHP Version 5.2.10-2ubuntu6.4
Except for the time module, it's a clean install of Atrium.
Comment #3
askibinski commentedI got this too in Atrium. Not sure if it has something to do with Atrium though.
Seems that the Object is broken after submission, resulting in a fatal error on validation.
I only had this in comments so far.
related issue on community.openatrium.com
Comment #4
a_c_m commentedStill the case with the latest version of both Atrium and Time module.
I've tried a little debugging - but came up empty. I tried to build out the object if we couldn't find it, then use that - but the problem was the same.
http://www.crainbandy.com/programming/php/how-to-fix-the-__php_incomplet...
Seemed to say it was something to do with the session?
In any case, for the moment the validation function its calling just returns TRUE anyway. My vote would be to remove it for now.
Comment #5
schedal commentedsame issue, 100% reproducible every time. latest version of atrium and time, clean fresh system nothing else installed. submitting any time gives this same error.
Comment #6
danepowell commentedYep, same issue with OA beta8
Comment #7
danepowell commentedJust FYI, the conflict is definitely with comment_upload, which is integrated with Open Atrium