[Tickets #6770] Re: Nag task lists over WebDAV don't work

bugs at horde.org bugs at horde.org
Thu Jun 26 14:37:04 UTC 2008


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6770
------------------------------------------------------------------------------
  Ticket             | 6770
  Updated By         | bb at apc.ag
  Summary            | Nag task lists over WebDAV don't work
  Queue              | Nag
  Version            | 2.2
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          | 2.2.1
  Patch              |
  Owners             | Jan Schneider, Ben Klang
------------------------------------------------------------------------------


bb at apc.ag (2008-06-26 10:36) wrote:

Thanks! This fixes loading the .ics file in Kontact for me, and also  
saving new entries onto the server. Editing existing entries and  
publishing that to the server doesn't work, I get "Access denied when  
uploading .....ics".

This is in the horde log:

DB Error: null value violates not-null constraint: UPDATE nag_tasks  
SET task_creator = 'bb',  task_assignee = 'MAILTO:bb',  task_name =  
'Teste Nag at baby',  task_desc = 'Mehrzeilige

Beschreibung

mit neuem Text',  task_start = 1214431200,  task_due = 0,   
task_priority = 5,  task_estimate = '0.00',  task_completed = 0,   
task_completed_date = 0,  task_category = '',  task_alarm = 0,   
task_parent = NULL,  task_private = 0 WHERE task_owner = 'bb' AND  
task_id = 'fe4b7e6e2d4e367ea68f036b72c1bfc0' [nativecode=ERROR:  null  
value in column "task_parent" violates not-null constraint] [pid 5176  
on line 280 of  
"/home/bb/src/groupware/horde/horde-webmail-1.1.1/nag/lib/Driver/sql.php"]

All the other entries in the DB have task_parent = '' but not NULL.

So I changed line 619 of nag/lib/api.php from

                         isset($task->parent) ? $task->parent :  
$existing->parent,
to:
                         isset($task->parent) ? $task->parent : '',

and now it seems to work.

Thank you for fixing this!





More information about the bugs mailing list