CardDav Cant Sync Field Deletion
Hello, I have hit an issue which I thought was my client but now I think it might be cPanel.
Steps to reproduce:
- Create new email account
- Connect CardDav client to new empty account
- Create contact with two phone numbers
- Sync
- Confirm all devices show correct data
- Delete one of the phone numbers from the new contact
- Sync
- Sync again, field will come back
-
- Delete one of the phone numbers from the new contact
Are you removing this from the device or from the server?0 -
Same issue here. The issue occurs when one deletes a field from an address book entry in a client (I am also using CardBook in Thunderbird and DAVx5 in Android) and then synchronizes it against the server. The synchronization refuses to delete the field from the server and instead returns the field (server side contents) back to the client. One might find this very frustrating. So far I have found one workaround: you can delete an email field - instead of actually trying to delete the field - by modifying the field contents in a client to contain a single '@' character only. Synchronizing this against the server results that the field is actually deleted from the server side and the field disappears upon next synchronization from all other clients as well. Unfortunately I have not been able to find documentation, which contents/characters in other fields would result similar behavior on the server. Further ideas? 0 -
The issue occurs when one deletes a field from an address book entry in a client ...
For the sake of clarity the this refers to deleting the contents of a field (editing a field and leaving it empty) on a client. Whatever you delete on a remote client is being restored from the server the next time you synchronize. Adding new content to a previously empty field as well as editing a field (not leaving it empty) works fine. Could this be a server configuration issue? Any assistance is highly appreciated.0 -
We are struggling the same issue, while trying to delete a field from horde's carddav, from a client. Will there be any solution or a workaround, how this can be performed? 0 -
Hi I am also observing this same behavior still almost 2 years after it was first reported. Is there a bug fix request to track this formally? 0 -
It doesn't look like there was an official case put in about this issue. If you're able to reproduce the behavior on your system reliably, could you submit a ticket so we can check that on our side? 0
Please sign in to leave a comment.
Comments
6 comments