linuxserver / docker-transmission

GNU General Public License v3.0
595 stars 185 forks source link

Default UI does not show Queue tab in Settings #222

Closed Porrumentzio closed 1 year ago

Porrumentzio commented 1 year ago

Is there an existing issue for this?

Current Behavior

There is no Queue tab in the Settings via the wrench icon.

Expected Behavior

No response

Steps To Reproduce

Click the wrench icon and there will be no tab for Queue settings

Environment

- OS: Raspbian Bullseye
- How docker service was installed: official distro repos

CPU architecture

arm64

Docker creation

version: "2.1"
services:
  transmission:
    image: lscr.io/linuxserver/transmission:latest
    container_name: transmission
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Madrid
      - TRANSMISSION_WEB_HOME=/combustion-release/ #optional
      #- USER=username #optional
      #- PASS=password #optional
      #- WHITELIST=iplist #optional
      #- PEERPORT=peerport #optional
      #- HOST_WHITELIST=dnsname list #optional
    volumes:
      - /mnt/elements/jellymission/trans/config:/config
      - /mnt/elements/jellymission/downloads:/downloads
      - /mnt/elements/jellymission/trans/watch:/watch
    ports:
      - 9091:9091
      - 51413:51413
      - 51413:51413/udp
    restart: unless-stopped

Container logs

I would say this is not needed in this case
github-actions[bot] commented 1 year ago

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

drizuid commented 1 year ago

remove your web ui and re-check. we support the container, not the application, so if you feel container logs aren't necessary, that implies you already know this isn't a container issue.

github-actions[bot] commented 1 year ago

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 1 year ago

This issue is locked due to inactivity