| Summary | Can not import vcard into turba |
| Queue | Horde Groupware Webmail Edition |
| Queue Version | 1.2.4 |
| Type | Bug |
| State | Duplicate |
| Priority | 2. Medium |
| Owners | |
| Requester | spm (at) boiteauxlettres (dot) sent (dot) at |
| Created | 11/29/2009 (5700 days ago) |
| Due | |
| Updated | 11/30/2009 (5699 days ago) |
| Assigned | 11/30/2009 (5699 days ago) |
| Resolved | 11/30/2009 (5699 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
bug 8707.turba checks to see if the entry already exists. That is when the
error occurs.
The bug affects other vcard-import-related activities. In my case, I
discovered this bug when trying to use syncML (which fails because of
this bug).
Yesterday I discovered the fix discussed in
ticket #8707. I tried it,and it solves my problem. It appears that the
#8707fix is notintegrated into turba yet.
State ⇒ Feedback
with data not replicating to the read slave in time for the check, but
I thought that was fixed before this release.
Do you get the error before uploading data, or after?
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Can not import vcard into turba
Queue ⇒ Horde Groupware Webmail Edition
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
entries, and I am able to export vcards, but I am not able to import
vcards. I get
"Read failed: (0) Success" errors, and nothing gets imported.
It appears that in turba/data.php, an LDAP search is performed.
if(PEAR_Error) {
signal error;
} else if(count != 0) {
signal that entry already exists;
} else {
add entry
}
It appears that the empty LDAP search result is generating a
PEAR_Error for some reason (Read failed: (0) Success). A google search
shows that I am not the only one receiving this error when a search
returns 0 entries. In fact, if I empty all of my contact entries, I
get the error when I click on the Browse button. Once I add an entry,
I do not see this error anymore, until I attempt to import a vcard.
Dave.