Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#1230 closed bug (WorksForMe)

Plugin label doesn't apply correctly the preferences when I change torrent between labels

Reported by: simonbcn Owned by:
Priority: major Milestone: 1.3
Component: Plugin Version: 1.3.0_dev
Keywords: Cc:

Description

Label "blu-ray"
http://img338.imageshack.us/img338/3798/captura020413.png http://img532.imageshack.us/img532/1435/captura030413.png

Label "dvd"
http://img341.imageshack.us/img341/3798/captura020413.png http://img341.imageshack.us/img341/1435/captura030413.png

Options of torrent in label "blu-ray":
http://img404.imageshack.us/img404/3798/captura020413.png

I change this torrent from "blu-ray" to "dvd" but Deluge doesn't apply any option of the new label.

Change History (11)

comment:1 follow-up: Changed 11 years ago by Cas

  • Milestone changed from 1.4.0 to 1.3.0
  • Status changed from new to pending

we cannot repeat with latest git master

comment:2 in reply to: ↑ 1 Changed 11 years ago by simonbcn

  • Status changed from pending to new

I have updated the git version now and the problem persists.

comment:3 follow-up: Changed 11 years ago by Cas

can you try with a fresh config

comment:4 in reply to: ↑ 3 ; follow-up: Changed 11 years ago by simonbcn

Replying to Cas:

can you try with a fresh config

Sorry, I can't. I execute deluged from server and I connect remotely via deluge-gtk. It's too work to make only a test.

When this last git version, when I restart the program, deluge removes the labels of torrents whose labels were manually assigned, except in one torrent... ¿?
This is really bad!

comment:5 in reply to: ↑ 4 Changed 11 years ago by Cas

  • Resolution set to worksforme
  • Status changed from new to closed

Replying to simonbcn:

Sorry, I can't. I execute deluged from server and I connect remotely via deluge-gtk. It's too work to make only a test.

In that case simply start a localhost server and test with that.

This is a development version so not having a clean config could cause unexpected results. Is the remote server 1.3.0dev as this could easily cause problems. We would need logs to actually determine the problem.

This cannot be reproduced as it stands so i am closing it

comment:6 Changed 11 years ago by simonbcn

I have tested in localhost and it now works...
But what do I do with the torrents that I have now? They are many.
Is this what we can expect every time you liberate a new version? Delete old config and delete all torrents and start again!!
Where is the backward compatibility?

comment:7 follow-up: Changed 11 years ago by Cas

I have already stated that this is a development version this means that things change constantly and so you should not rely on it to be 100% stable. This is the fundamental principle of building applications from source code that has not been released.

I did not say you had to delete your torrents but obviously it would recheck them all when they are added again.

Backward compatibility in relation to what?

comment:8 in reply to: ↑ 7 ; follow-up: Changed 11 years ago by simonbcn

Replying to Cas:

Backward compatibility in relation to what?

In relation to v1.2.3. I have used the same config from that version without problems and now...

What can I do now to update the actual torrents to new config!? Must I add one to one again!? o_O

comment:9 in reply to: ↑ 8 ; follow-up: Changed 11 years ago by andar

Replying to simonbcn:

Replying to Cas:

Backward compatibility in relation to what?

In relation to v1.2.3. I have used the same config from that version without problems and now...

What can I do now to update the actual torrents to new config!? Must I add one to one again!? o_O

I guess what's being asked is to try it out with a fresh config to see if the problem lies with your current config files. To do this, simply mv your current config directory somewhere safe and startup deluge.

mv ~/.config/deluge ~/.config/deluge.backup

Then add a torrent, assign a label and then change the label. See if you can reproduce your original results. This will help us track down the problem.

}}}

comment:10 in reply to: ↑ 9 Changed 11 years ago by simonbcn

Replying to andar:

Replying to simonbcn:

Replying to Cas:

Backward compatibility in relation to what?

In relation to v1.2.3. I have used the same config from that version without problems and now...

What can I do now to update the actual torrents to new config!? Must I add one to one again!? o_O

I guess what's being asked is to try it out with a fresh config to see if the problem lies with your current config files. To do this, simply mv your current config directory somewhere safe and startup deluge.

mv ~/.config/deluge ~/.config/deluge.backup

Then add a torrent, assign a label and then change the label. See if you can reproduce your original results. This will help us track down the problem.


I already have done and verified that works (comment:6 ).
But I think that the last modifications are incompatible with config in deluge prior to this git version. With my old config (it used the same from version 1.2.1) now it's incompatible the info of labels in torrents.
If there isn't backward compatibility, IMHO, there is a problem.

comment:11 Changed 11 years ago by andar

Well, to be fair you've been using the development branch so the config may not be the same as 1.2.1 at this point. What could be done is to load deluge 1.2.x up with fresh config and create some labels / add some torrents, then upgrade to the latest master version and try to reproduce this issue. We will know when if there a problem with migrating the config from 1.2.x to master.

Note: See TracTickets for help on using tickets.