Tortoise SVN adds characters to Wordpress Plugin Repository web address - Bug?

[itmon...@gmail.com]

Hi,

When I try to Commit the Wordpress Plugin trunk files to http://plugins.svn.wordpress.org/​search-excel-csv/trunk Tortoise will add by itself some garbled characters before the slug search-excel-csv. This results obviously that the Commit is not completed as the repository address is wrong.

Please, see here https://diigo.com/0eu04y to check the screen shots.

I uninstalled Tortoise, cleaned the PC with Glarys Utilities, but on reinstall Tortoise will still add the garbled characters.

Any advice to fix this issue is welcome

Rgs

IM

[Oskar Berggren]

I very much doubt the problem is with TortoiseSVN. Most likely you have some garbage letter in the URL that Tortoise is dutifully URL escaping.

The E2 80 8B byte sequence happens to be the UTF-8 encoding for Unicode character U+200B (ZERO WIDTH SPACE).

It wouldn't be the first time someone has accidentally gotten this included somewhere where it shouldn't due to unknowingly copy-pasting invisible characters.

Hope it helps,

Oskar

--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/798bbfca-9f2f-477d-93bd-8fd21dbb9efd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Iti Monitor]

Hi

 

thank you. If you see in the screenshots I shared in my first email  https://diigo.com/0eu04y, the repository web address (slug) is correct at the Tortoise window top bar, but somehow Tortoise adds the garbled slug when commiting to the Wordpress repository. Also, even after uninstalling Tortoise, cleaning the PC, cookies, flushing Windows 10 DNS, etc. , on reinstall Tortoise will again add the garbled slug when commiting to the Wordpress repository. 

Please, let me know how to fix this and do a clean reinstall of Tortoise.

Rgs

IM

You received this message because you are subscribed to a topic in the Google Groups "TortoiseSVN" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tortoisesvn/mwHnIaYf3G0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/CAHOuc7OUoiHa7WVSirARnUrSrjrnbg2qkk3Q%3DMry2aLDX6v9zg%40mail.gmail.com.

[Stefan]

Committing is always done to the url of the working copy.

Your screenshots show that you're committing to a http url. But every svn repo I know of does not allow commit access to a http url, only https ones.

So: do a fresh checkout from the same url but use https instead of http.

And also enter the url manually when checking out: seems last time you copy/pasted the url but it contained hidden chars.

[Oskar Berggren]

Hi

I suspect that tortoise might not do the URL escaping when the URL is displayed in the title bar as that generally makes it less readable. The zero width space would of course be invisible when not URL encoded. When actually calling it, it must be encoded in accordance with standards.

The title of the first window also states https but the commit window then calls http. Did you really open that repository browser from the context menu for the same working directory that you are then trying to commit? Perhaps you opened the repo browser and pasted the URL separately there?

As Stefan said, you can try checking out to a fresh working directory. You can also use Relocate from the menu to check and edit the working copy URL. To remove the invisible space, put the text marker after the s in search, and hit backspace twice. If the slash is now still there, it means there was an invisible character. Retype the s and proceed.

I guess it's also possible that the zero width space is an actual part of the repo name in which case the encoding is correct and the problem is something else.

/Oskar

To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/CADVcmiY8NPyDouQGdKcUQS8o8PjSYrmVYT7PmiAmKivZqjOerQ%40mail.gmail.com.

[Iti Monitor]

Hi, 

thank you. I found time to check the steps carefully. Incredibly as it may sound, when I click the https link at the Wordpress "welcome" email, it will open the plugin repository, but as http (no https). When I hover the my mouse over the link in the Wordpress email, it will display a https link in the browser bar (I am using gmail), but on clicking it will open a non ssl tab with the plugin repository. I agree with you that nobody would let access to a non SSL repository nowadays, but seems like Wordpress is not blocking non https access to their repository.

Thank you for our advice, the issue is solved now.

rgs

To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/CAHOuc7NTFoCpyye0LekgtWoHpA9_pnZNidZYUW1vEq-ZW%2BJQyg%40mail.gmail.com.