mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-26 03:25:48 +03:00
[GH-ISSUE #83] Support for images when using CardDAV #980
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#980
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @thomaswoeckinger on GitHub (Dec 1, 2015).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/83
Currently VCard's with images causing an error during synchronization.
So it would be great if images would not result in an error, and all other informations are transferred.
In general the support of images would be great!
Anyway thx for your great work!
@aluxnimm commented on GitHub (Dec 1, 2015):
What server? Images work for sogo,horde,owncloud etc. Please provide the log with the error and an vcf file from the server with the image that doesn't work.
@thomaswoeckinger commented on GitHub (Dec 1, 2015):
Zarafa Sabre DAV
@aluxnimm commented on GitHub (Dec 1, 2015):
Never tested with Zarafa, we don't have a test account atm. Log and vcf file should help to find the issues.
@thomaswoeckinger commented on GitHub (Dec 2, 2015):
Isolated log when trying to transfer one Vcard entry with an image.
Log:
log.txt
Created VCard by sabre-zarafa
sabrezarafa.txt
@aluxnimm commented on GitHub (Dec 3, 2015):
So you have problems syncing vcards with images from the server to Outlook? that vcard in your server debug log is not base64 encoded.
@thomaswoeckinger commented on GitHub (Dec 3, 2015):
I tracked it down to an bug in sabre-zarafa wich allows to send vcard 4.0 but the used sabredav version 2.1.7 does not support it fully, so i changed the configuration to 3.0 and all is working now.
Thx for your time