nextcloud / nextcloud/contacts
Backslashes (Escaped slashes) in URL's on imports from google
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 220
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 51
Description
Describe the bug
I'd import my addresslist from Google.
On Google I've exported it as VCARD :

If I import those vcs file into nextcloud/contacts, all / are escaped:

If I look into the vcs, I see, that slashes are also escaped there, but only once:

It would be nice, if contact could recognize such escape characters, and remove them
Steps to reproduce
- Create an address entry with an http://xyz.com in your google contacts
- Export an addressbook as VCS from Google
- Import it to nextcloud contacts
- see error in contacts address entry
Expected behavior
slashes should not be escaped in contacts
Actual behavior
slashes are escaped
Contact version
4.1.0
Operating system
didn't found.. as it's a managed one by hetzner. BTW, isn't there a way to see that in nextcloud gui?
PHP engine version
No response
Web server
No response
Database
No response
Operating system
No response
List of activated Apps
Can't run this command.
I do have an managed service on Hetnzer: https://www.hetzner.com/storage/storage-share?country=de
So I don't have access to the server below.
Couldn't you create such an URL to output those list like the following section "Nextcloud Signing status"?: https://yournextcloud.tld/index.php/settings/integrity/failed
That would make things easier for bugreporters.
Nextcloud Signing status
No errors have been found.
Configuration report
Same here as above, no access to cli.
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source file or test. Start by reproducing a Google VCS import containing an http:// URL, then trace how the imported contact value is parsed; done means URL slashes remain unescaped in the contact address.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100