extern/egroupware_official
1
0
Fork 0
mirror of https://github.com/EGroupware/egroupware.git synced 2024-11-23 00:13:35 +01:00
Code Issues Packages Projects Releases Wiki Activity

ActiveSync/Mail/MeetingRequests: HandlingMeetingRequests on MobileDevice has serious issues within our/zpush2 implementation. thus we overwrite the globalobjId from calendar object, as: if you delete the mail, that is the meeting-request its using the globalobjid as reference and deletes both: mail AND meeting. we dont want this. since accepting meeting requests with the mobile does nothing we see no further drawbacks with that. TODO: Look into MeetingRequestHandling

Browse Source
This commit is contained in:
Klaus Leithoff 2015-12-15 13:39:10 +00:00
parent 16f835822f
commit 862a848043
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
mail/inc/class.mail_zpush.inc.php
View File

@ -1062,6 +1062,10 @@ class mail_zpush implements activesync_plugin_write, activesync_plugin_sendmail,
($attachment = $this->mail->getAttachment($id, $attach['partID'],0,false,false,$_folderName)) && ($attachment = $this->mail->getAttachment($id, $attach['partID'],0,false,false,$_folderName)) &&
($output->meetingrequest = calendar_zpush::meetingRequest($attachment['attachment']))) ($output->meetingrequest = calendar_zpush::meetingRequest($attachment['attachment'])))
{ {
//overwrite the globalobjId from calendar object, as: if you delete the mail, that is
//the meeting-request its using the globalobjid as reference and deletes both:
//mail AND meeting. we dont want this. accepting meeting requests with the mobile does nothing
$output->meetingrequest->globalobjid = activesync_backend::uid2globalObjId($id);
$output->messageclass = "IPM.Schedule.Meeting.Request"; $output->messageclass = "IPM.Schedule.Meeting.Request";
unset($attachment); unset($attachment);
continue; // do NOT add attachment as attachment continue; // do NOT add attachment as attachment