Opened 13 years ago

Closed 10 years ago

Last modified 6 years ago

#2006 closed feature-request (Fixed)

Add move storage failed alert

Reported by: nicorac Owned by: Calum
Priority: minor Milestone: 2.0.0
Component: Web UI Version: 1.3.3
Keywords: Cc:

Description

Right click on a running torrent (single file one), then choose "Move storage" and enter an existing folder... nothing happens.
The WebUI still shows the old (and default) download folder and torrent download continues there.

Change History (8)

comment:1 by Calum, 13 years ago

Status: newpending

I cannot replicate this.

Are you sure the destination folder has permissions?

What format are you entering the folder details? For example I tested with: /home/ubuntu/Downloads

comment:2 by nicorac, 13 years ago

Status: pendingnew
Type: bugfeature-request

You're right, it was a permission issue.
I have 3 destination subfolders and one of them was owned by root (I feel so noob).

I think a warning message should be added to WebUI and/or console client.
Both of them do not warn user at all, they simply discard the move command.
So I changed this bug to a feature request.

comment:3 by Calum, 13 years ago

Milestone: 1.3.41.3.x
Summary: Move storage feature not workingAdd move storage failed alert

There is currently no function in the core to catch a libtorrent 'storage_moved_failed_alert' alert so that creates an issue with compatibility between 1.3 versions. There will be no issue adding it to 1.4 though.

comment:4 by Calum, 12 years ago

Milestone: 1.3.x1.4.0

comment:5 by Calum, 10 years ago

Owner: changed from Damien Churchill to Calum
Status: newassigned

This is fixed in develop so that the torrent is paused and put into an error state: [a2fcaa15c96880de]

I realised that I did not test if the Error persists on daemon restart but that is sort of covered in another ticket however will leave this ticket open to remind me.

comment:6 by Calum, 10 years ago

Resolution: Fixed
Status: assignedclosed

Ticket for persistent error over restart: #1032

comment:7 by Calum, 9 years ago

Milestone: 2.0.x2.0

comment:8 by Calum, 6 years ago

Milestone: 2.02.0.0

Milestone renamed

Note: See TracTickets for help on using tickets.