loki wrote: it doesn't differentiate a folder from a file.

Python has a simple test to differentiate a folder from a file: stat.S_ISDIR(os.stat(file).st_mode)

So from the sounds of it, you had a completed file located at: <download directory>/file.7z/file.7z you then removed that file from deluge and re-added it, specifying <download directory>/file.7z/ to be the download directory. deluge saw the file.7z (actual file) and thought it was the file.7z fold...

The only thing I can think is the file wasn't the same as when the torrent file was created so it marked the data as corrupt and started downloading the proper data for the torrent. No. Deluge expected to place a FOLDER in the torrents folder. Instead there was a FILE of the same name as the FOLDER...

I removed the torrent from deluge before adding it back in again. Did you do that?

Okay I had a torrent with a folder named something.7z inside this folder was a 7zip file named something.7z (same exact name) I though there was an error in my torrent so I moved the 7zip file back into the torrents folder and re-initialized the .torrent file. Deluge promptly overwrote the something...

johnnyg wrote:have you tried forcing a recheck?

When I do that, it just ignores me.

Deluge froze up. On restart all my torrents are blank.














Deluge make me a sad panda.