[Tickets #8703] Re: %-completion on tasks submitted by Kontact/Akonadi is not accepted

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/8703
------------------------------------------------------------------------------
  Ticket             | 8703
  Updated By         | bugs.horde.org at sjau.ch
  Summary            | %-completion on tasks submitted by Kontact/Akonadi is
                     | not accepted
  Queue              | Nag
  Version            | FRAMEWORK_3
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


bugs.horde.org at sjau.ch (2009-11-12 08:10) wrote:

>> In #akonadi on freenode I was told that it's horde's fault for not
>> "accpeting" those changes.
> Only if Akonadi is correctly sending the completion state. Does the  
> console show the actually iCalendar object that is being sent to  
> Horde, or can you grab it with a network logger?

If I knew how to grab it with a network logger or is there  a way that  
the rpc.php dumps all queries into a log?

As far as I was told in the akonadi channel is, that this has been  
discussed before and that they determined that horde was the culprit.

[Wednesday, 11. November 2009] [13.51:57] <volker|office>       this  
has been discussed here before, IIRC horde ignores the percent-done  
field apparently
[Wednesday, 11. November 2009] [13.52:30] <bbroeksema|offic>     
well...... then go bug horde people =:)
[....]
[Wednesday, 11. November 2009] [14.04:14] <bbroeksema|offic>    well,  
than see volkers comments =:)
[Wednesday, 11. November 2009] [14.04:30] <bbroeksema|offic>    this  
seem to been discussed before
[Wednesday, 11. November 2009] [14.05:47] <hyper_ch>    ok
[Wednesday, 11. November 2009] [14.08:29] <bbroeksema|offic>     
hyper_ch: The best you can do is contacting horde developers and check  
if this is a known issue for your version of the horde server