6.0.0-beta1
7/11/25

[#7907] assignee parameter in task (nag) raises php-error on task objects create with former nag versions
Summary assignee parameter in task (nag) raises php-error on task objects create with former nag versions
Queue Kolab
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester m.gabriel (at) das-netzwerkteam (dot) de
Created 01/27/2009 (6009 days ago)
Due
Updated 01/28/2009 (6008 days ago)
Assigned
Resolved 01/28/2009 (6008 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
01/28/2009 12:51:47 AM Chuck Hagenbuch Comment #3
State ⇒ Not A Bug
Reply to this comment
Grrr.
01/27/2009 11:01:32 PM m (dot) gabriel (at) das-netzwerkteam (dot) de Comment #2 Reply to this comment
forget this one, my prefs.php in NAG was not up-to-date... SORRY!
01/27/2009 10:40:09 PM m (dot) gabriel (at) das-netzwerkteam (dot) de Comment #1
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kolab
Summary ⇒ assignee parameter in task (nag) raises php-error on task objects create with former nag versions
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
i upgraded a kolab driven nag version without support for the 
,,assignee'' field (it has been recently added, hasn't it?) to a nag 
version that implements the ,,assignee''-field (cvs checkout from 
20081223).



when opening the task list with the cvs-20081223 nag version i get the 
following php-error:



Warning: in_array() [function.in-array]: Wrong datatype for second 
argument in 
/usr/local/share/_horde-versions_/horde4-cvs+git-20081223/horde/nag/templates/list/task_headers.inc on line 
33



i have looked at the code a bit and it looks like the Nag_Task object 
construction completely relies on the fields in the storage backend. 
in my case i have ,,old'' kolab task objects that miss the 
,,assignee''-field. if only the fields of my old kolab task object 
form the properties of my horde Nag_Task object then of course the 
,,assignee''-field is missing in the Nag_Task object that ends up with 
the above php-error.



to my point of view a Nag_Task object construction should setup the 
properties from backend, if missing there null properties should be 
created in the Nag_Task. currently, something similar seems to be done 
when saving the Nag_Task object back to the kolab backend (it is done 
in the kolab backend, i think...).

Saved Queries