[Bug]: Contacts menu broken if uids in oc_cards contain slashes about server

[michaellass]

Of course, this assumes you have access to the database, if you don't then I'm not really sure what you can do here as you can't even delete the contacts as they won't be showing in the contacts list.

For me, all contacts are shown correctly in the Contacts app and can be accessed. I think it is just the contacts menu (and maybe the global search) in the Nextcloud main interface that struggles with this.

[ShivaSystem]

I have exactly the same problem

[pswilde]

I've been having this same problem, it's a real nuisance error message, but I don't think it has any real impact on anything - but I am certainly no expert!

Anyway, I think I've got rid of my error here by doing a bit of database admin:
I use postgres as db backend, but the basic statements should be the same.
first, find the properties that have a slash in them:

select * from oc_cards_properties where name = 'UID' and value like '%/%';

this will likely show you a list of contact properties where the UID contains a slash - take note of the "cardid" for them all
Then, take a record of the contact properties of the above:

select * from oc_cards_properties where cardid in ( ## a comma separated list of the ids from the previous select statement, i.e. 10,42,43... ## );

take note of this information, as you're going to delete the contact and re-add it
delete the problem contacts

delete from oc_cards_properties where cardid in (## comma separated id list as above ##);
# and #
delete from oc_cards where cardid in (## comma separated id list as above ##);

That should remove the problem contacts from the database, then just simply re-add the contacts from the nextcloud contacts front end - they should get added with correct UIDs without slashes

Of course, this assumes you have access to the database, if you don't then I'm not really sure what you can do here as you can't even delete the contacts as they won't be showing in the contacts list.

[Armin-Gips]

I also have no errors in the application. But the error log reports this error dozens of times!