-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't swap contacts between address books #20492
Comments
I didn't notice, but confirming it on my end now. |
Surprisingly I see a MOVE request that returned 200, meaning it was successful 🤔 How many addressbook do you have? Does it do that for all contacts? |
Yes, the contact gets moved to the other address book, but when I return to the contact the old address book is shown. I hope this clarifies things. I have two address books. Let me know if you still need that screencast, could be problematic as I don't want to make my contacts public... edit: I tried with several contacts. All showed the same behaviour. I'll try it with another user! |
Can you try with another new addressbook too?
Sure, let's postpone until it's really necessary (you can send me privately so your data is safe) |
You mean create a contact in a new address book and swap him to a second new address book? |
I did as described before and now it works as expected:
|
I tried to export my "problematic" address book and import it into a new address book. After the import, i tried changing address books (both new) for several contacts. |
It seems that all contacts with a birthday entry "swap bad" and all contacts without a birthday entry swap as intended. Could this be the reason??? |
I've encountered this issue before as well. Forgot to look into it. If I remember correctly, the issue had something to do with calendar events for a contact (so yes, birthday, but also anniversaries). My best guess is that the DAV backend treats a moved contact like a new one and tries to create a new calendar event using the UID of that 'new' contact. But since a calendar entry with this UID already exists, it fails. Or something like that. |
Hey, @skjnldsv! Anything new concerning this issue? Best regards |
Hey sorry! I was crazy busy :) |
This comment has been minimized.
This comment has been minimized.
Issue not solved yet. |
Also affected by this, this is a massive problem as it generates duplicates in the database and does not show birthdays of affected contacts in the calendar, without any warning that something might be wrong. |
This comment has been minimized.
This comment has been minimized.
Not solved yet... |
This is my monthly reminder xD 🙈 |
@phiL0co can you reset my password & test account please? Cannot access it it seems 🤔 |
I didn' create a test account for you. At least not yet... ;-) |
Damn, I mixed up the issues xD |
Okay, so can yuo try the nextcloud/contacts#1579 test release there please? Same as https://github.com/nextcloud/contacts/issues/1431#issuecomment-576639643, it was what I need |
Click the 400 error in the network tab and copy the response here please :) |
So you have a duplicate :) |
No, he isn't. |
Okay, you see the url you currently have, it should be something like yourdomain.com/apps/contacts/group/addressbookid~contactsuid Change the addressbookid from default (it seems to be that) to the other one. Does it display a contact? |
@skjnldsv No intention of disrespect but did you notice that it complains about duplicate in calendar, not in contacts. As stated above this problem only seems to happen with contacts that have birthday information. |
No worries! :) |
Yes, that looks Birthday calendar related. |
Another thing I should add that I didn't know in my initial opening post: When I switch a contact from one address book to another, at first it seems the switch was successful. The contact is only shown once in the new address book. So the sync with the phone is definitely not the reason for the duplicates, which I suspected at that time. |
On Nextcloud 19.0.1 the error message is different:
Exception stack trace:
|
The problem is as follows:
I am not sure what the right solution would be here. |
The problem is not that the card is changed; moving a card to another address book means that 1. a new card is created and 2. the old card is deleted. This also means that we cannot see that a card is being moved; we must handle the duplicate calendar entry problem before the old one gets deleted. |
…dress book When an contact is moved to another address book, the contact is copied to the second address book. During copying, the birthday event is created - but it gets the same UID as the contact's birthday event in the first address book. To prevent the "Calendar object with uid already exists" error that followed, we need to delete the old entry before the new one is created. Resolves: #20492 Signed-off-by: Christian Weiske <cweiske@cweiske.de>
…dress book When an contact is moved to another address book, the contact is copied to the second address book. During copying, the birthday event is created - but it gets the same UID as the contact's birthday event in the first address book. To prevent the "Calendar object with uid already exists" error that followed, we need to delete the old entry before the new one is created. Resolves: #20492 Signed-off-by: Christian Weiske <cweiske@cweiske.de>
…dress book When an contact is moved to another address book, the contact is copied to the second address book. During copying, the birthday event is created - but it gets the same UID as the contact's birthday event in the first address book. To prevent the "Calendar object with uid already exists" error that followed, we need to delete the old entry before the new one is created. Resolves: #20492 Signed-off-by: Christian Weiske <cweiske@cweiske.de>
…dress book When an contact is moved to another address book, the contact is copied to the second address book. During copying, the birthday event is created - but it gets the same UID as the contact's birthday event in the first address book. To prevent the "Calendar object with uid already exists" error that followed, we need to delete the old entry before the new one is created. Resolves: #20492 Signed-off-by: Christian Weiske <cweiske@cweiske.de>
…dress book When an contact is moved to another address book, the contact is copied to the second address book. During copying, the birthday event is created - but it gets the same UID as the contact's birthday event in the first address book. To prevent the "Calendar object with uid already exists" error that followed, we need to delete the old entry before the new one is created. Resolves: #20492 Signed-off-by: Christian Weiske <cweiske@cweiske.de>
Steps to reproduce
Expected behaviour
The address book should remain the previously selected
On the phone (after a sync) a "switched" contact should only be in one address book, the address book that is selected in Nextcloud's contact app.
Actual behaviour
The address book always switches back to the first one.
BUT: When I sync the new address book on my phone, suddenly the contact seems to be in both address books, according to the phone. In the browser view, the contact remains in the old address book. So it seems somethings is happening in the background.
After syncing with the phone at some point the contact appears twice in Nextcloud contacts app, one contact in the old address book, the other one in the new address book.
Server configuration
Operating system:
Ubuntu 18.04
Web server:
Apache
Database:
MySQL 5.7.28
PHP version:
7.2.24
Nextcloud version: (see Nextcloud admin page)
17.0.2
Contacts version: (see Nextcloud apps page)
3.1.6
Updated from an older Nextcloud or fresh install:
Updated
Signing status:
What does this mean?
Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.
List of activated apps:
Accessibility 1.3.0
Activity 2.10.1
Auditing / Logging 1.7.0
Bookmarks 2.3.4
Calendar 2.0.0
Checksum 0.4.3
Collaborative tags 1.7.0
Comments 1.7.0
Contacts 3.1.6
Default encryption module 2.5.0
Deleted files 1.7.0
Draw.io 0.9.4
Federation 1.7.0
File sharing 1.9.0
First run wizard 2.6.0
Gallery 18.4.0
Log Reader 2.2.0
Markdown Editor 2.2.0
Metadata 0.10.0
Monitoring 1.7.0
Nextcloud announcements 1.6.0
Notifications 2.5.0
ocDownloader 1.7.5
Password policy 1.7.0
PDF viewer 1.6.0
Privacy 1.1.0
RainLoop 6.0.4
Recommendations 0.5.0
Right click 0.15.1
Share by mail 1.7.0
Support 1.0.1
Suspicious Login 3.0.1
Tasks 0.11.3
Text 1.1.1
Theming 1.8.0
Two-Factor TOTP Provider 4.1.2
Update notification 1.7.0
Usage survey 1.5.0
Versions 1.10.0
Video player 1.6.0
Viewer 1.2.0
Nextcloud configuration:
Are you using external storage, if yes which one: local/smb/sftp/...
no
Are you using encryption: yes/no
yes
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Only CalDav and CardDav if thats a user-backend
LDAP configuration (delete this part if not used)
Client configuration
Browser:
Firefox 68.4.1 esr / Firefox 72
Operating system:
Windows 10 / Manjaro Linux
CardDAV-clients:
DAVx5
The text was updated successfully, but these errors were encountered: