You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running roundcube 0.8.1 on debian stable, with roundcube-Carddav 5.1, patched following issue 29 (#29)
When syncing my adressbook, contacts which don't have a ".vcf" extension in the davical server are not seen by roundcube-carddav : they do not appear in roundcube (please note that they do not get deleted from the server either : roundcube-carddav just don't "see" them).
roundcube log is clean, roundcube carddav saying that everything was synced correctly.
I would guess this is due to roundcube-carddav pruning elements whithout extension.
Any help indicating what to change in the code would be welcome. All I could find are lines which strip the vcf extension in carddav_backend.php.
I can try to provide two example of "synced" and "not synced" contacts if needed, althought the trick here is that it's only a matter of how davical "represent" them in its DB.
The text was updated successfully, but these errors were encountered:
I'm running roundcube 0.8.1 on debian stable, with roundcube-Carddav 5.1, patched following issue 29 (#29)
When syncing my adressbook, contacts which don't have a ".vcf" extension in the davical server are not seen by roundcube-carddav : they do not appear in roundcube (please note that they do not get deleted from the server either : roundcube-carddav just don't "see" them).
roundcube log is clean, roundcube carddav saying that everything was synced correctly.
I would guess this is due to roundcube-carddav pruning elements whithout extension.
Any help indicating what to change in the code would be welcome. All I could find are lines which strip the vcf extension in carddav_backend.php.
I can try to provide two example of "synced" and "not synced" contacts if needed, althought the trick here is that it's only a matter of how davical "represent" them in its DB.
The text was updated successfully, but these errors were encountered: