Skip to content

Transmission path is ignored #2131

Description

@dulakm

Expected behaviour:

When I specify path attribute to transmission plugin, it is forced and the destination is set for downloading content.

Actual behaviour:

With path attribute set as well as incomplete-dir set for transmission as a library, the library setting is used instead of path.

Steps to reproduce:

  • Step 1: In your transmission settings (e.g. /etc/transmission-daemon/settings.json) set
    • "incomplete-dir": "/something"
    • "incomplete-dir-enabled": true
  • Step 2: In flexget transmission plugin specify
    • path: "/something-else"
  • Step 3: Run your task using transmission plugin, /something path will be used instead of /something-else

Config:

https://github.com/zilexa/flexget_config

Additional information:

  • FlexGet version: 2.13.15
  • Python version: Python 2.7.13
  • Installation method: pip
  • Using daemon (yes/no): no
  • OS and version: Linux osmc 4.14.34-1-osmc

Activity

  1. gazpachoking commented on May 7, 2018

    @gazpachoking
    Member

    Are the files being moved to the location you set in flexget once they are complete? If so, things are working as intended.

  2. dulakm commented on May 8, 2018

    @dulakm
    Author

    Unfortunately not. Once complete, the files are still in my incomplete-dir. Neither they are moved to the dir specified in flexget plugin, nor to the one specified in general settings.json.

  3. gazpachoking commented on May 8, 2018

    @gazpachoking
    Member

    Hmm. Pretty sure this worked at some point, did transmission recently update?

  4. assigned and unassigned on May 10, 2018
  5. gazpachoking commented on Feb 25, 2019

    @gazpachoking
    Member

    @dulakm Can you check again with next version? Based on this it could have been a problem with trailing slashes in the path. https://discuss.flexget.com/t/config-for-transmission-moves-single-files-but-fails-with-folders/4586/2

  6. gazpachoking commented on Mar 7, 2019

    @gazpachoking
    Member

    I'm going to assume this is fixed for now. We can re-open if someone finds different.

  7. dulakm commented on May 26, 2019

    @dulakm
    Author

    @gazpachoking thank you for the fix and the information! I can confirm that it works as expected on version 2.21.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions