Rename folder to the same as another

Good point. I did not think about this. I'll remove this check in v2.1.1.

BTW, you tried to rename the folder in the torrent addition dialog, right?

If you tried to rename later, I would expect it to fail. However, it should work if you rename the torrent directly on addition, in torrent addition dialog.

Yes, I tried it in the torrent addition dialog and in the main window after. Both produce the same result.

Well. I have just tested and it works just fine from torrent addition dialog.

I created "test" folder in the destination path. Then I added a new torrent to qBittorrent and in the torrent addition dialog, I renamed to "test" its root folder. I got no warning and qBittorrent is downloading the torrent in test folder.

Have the fix been included in the 2.1.1 release? I've just upgraded but the issue is still here... I think this one is really important, especially for downloading serial episodes. There are many cases, when whole season is seeded via one torrent, which updated repeatedly by adding new episodes. Every new version of torrent definitely should be saved to the existing folder with previous episodes.

It was largely fixed for me. I've only had trouble with a couple torrents. One was when the files in the folder had a very similar name to the folder, and another was when there was a folder inside the folder with a similar name.
I was able to get it to work on a couple that didn't work initially by changing the name to something completely different (ie. lolol) then changing it back.

Ok. It's rather strange then. I've tested it only with one torrent yet and the feature is not working at all. This torrent have one root folder with files (season of episodes). When I'm trying to rename root folder to the needed one (namely "Season 3"), I get error "The name is already in use in this folder" (it's true of cause). This happens both in "Torrent addition dialog" and in the main window.
Moreover I've even got this error for NOT existing folder. It's happens when the new name is the old one with the cropped tail. For example, renaming "ABCD" to "ABC" fails with the mentioned error.

PS: I'm on openSUSE 11.2 x86_64, package from the repository "BuildService:fisiu".

NovA: Your message does not make sense and I'll tell you why.

In torrent addition dialog, qBittorrent never checks the hard disk when you rename a file/folder in the torrent.

The message "The name is already in use in this folder" simply means that you are trying to rename a file in the torrent and give it the same name as another file that is also *in* the torrent (not hard disk) and same folder.

Ok. Then the message is a little misleading and the error is wrong in my case. I'm definitely sure that the new name doesn't conflict with any other in the torrent, and moreover I'm renaming root folder not containing file. Probably my torrent file is non-standard somehow, I can mail it for inspection...

No, you're right. I tried to rename the root folder and I got the error too. I'll fix this now. Thank you for insisting :)

I fixed it in SVN. I'll patch the packages on my PPA today (and notify other package maintainers). Thanks a lot.

Thanks for quick respond.
And thank you very much for making such a good torrent client. I've tried lot of them, and the most can't even rename files! :) Until recently I was stuck with a uTorrent under wine. But now, with qBittorrent 2.1 it's in the past. For me this is the best torrent client available for Linux. Yes there are some small bugs here and there, but it's going better and better each day, even each hour! Please keep it light and simple, do not transform it to the client-server monster, there are lot of them... Regards!

No problem. Thanks for the feedback. qBittorrent is usually quite stable but qBittorrent v2 brought so many changes that new bugs were impossible to avoid. Features such as torrent renaming are new and thus more likely to have bugs.

However, as long as users keep reporting bugs, qBittorrent v2 will become extremely stable (if not already).

qBittorent 2 is stable for me actually, meaning that it's not crashing, leaking memory or something like that. And of course many changes leads to some bugs. It's ok. Moreover, if any program has no bugs, the bug is in compiler. :)
Seriously, I believe qBT 2.1.* will be polished quite soon, and I'll try to report as many inconsistencies as I can to bring that day closer. Thanks again for your work.