Fix generating POOMCAL_RESPONSETYPE for series exceptions.

horde · Nov 28, 2013 · e5a0412 · e5a0412
1 parent 2bc729e
commit e5a0412
Showing 1 changed file with 8 additions and 9 deletions.
diff --git a/kronolith/lib/Event.php b/kronolith/lib/Event.php
@@ -1706,19 +1706,18 @@ public function toASAppointment(array $options = array())
                         $e->setDTStamp($_SERVER['REQUEST_TIME']);
 
                         switch ($exception->status) {
-                        case Kronolith::STATUS_CANCELLED:
-                            $status = 'declined';
+                        case Kronolith::STATUS_TENTATIVE;
+                            $e->responsetype = Horde_ActiveSync_Message_Appointment::RESPONSE_TENTATIVE;
+                            break;
+                        case Kronolith::STATUS_NONE:
+                            $e->responsetype = Horde_ActiveSync_Message_Appointment::RESPONSE_NORESPONSE;
                             break;
                         case Kronolith::STATUS_CONFIRMED:
-                            $status = 'accepted';
+                            $e->responsetype = Horde_ActiveSync_Message_Appointment::RESPONSE_ACCEPTED;
                             break;
-                        case Kronolith::STATUS_TENTATIVE:
-                            $status = 'tentative';
-                        case Kronolith::STATUS_FREE:
-                        case Kronolith::STATUS_NONE:
-                            $status = 'none';
+                        default:
+                            $e->responsetype = Horde_ActiveSync_Message_Appointment::RESPONSE_NONE;
                         }
-                        $e->setResponseType($status);
 
                         // Tags/Categories
                         if (!$exception->isPrivate()) {