[BUG] "Remove search provider dropdown when there's only a single provider" doesnt work

Open Beginner friendly
#161 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker
Domain
frontend, search

Research direction

Reproduce the issue from Settings by selecting a single search provider and saving the configuration, then trace the search-provider dropdown entry point. Confirm the fix by verifying that the dropdown is absent when only one provider is configured and that the search setting still works.

Written by the indexing model from the issue text.

Description

no-issue-activity
Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

When specifying a search provider, it still shows the dropdown:

Image
Expected Behavior

No dropdown

Steps To Reproduce
  1. Open Settings
  2. Select a search provider
  3. Save
Environment
- OS: 24.04.4 LTS
- How docker service was installed: https://docs.docker.com/engine/install/ubuntu/
CPU architecture

x86-64

Docker creation
---
services:
  heimdall:
    image: lscr.io/linuxserver/heimdall:latest
    container_name: heimdall
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Berlin
      - ALLOW_INTERNAL_REQUESTS=false
    networks:
      - dockerinternal
    volumes:
      - heimdall_config:/config
    #ports:
      #- 1000:80
      #- 1001:443
    restart: unless-stopped

networks:
  dockerinternal:
    name: dockerinternal
    external: true

volumes:
  heimdall_config:
    name: heimdall_config
Container logs
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────
      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝
   Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: v2.8.0-ls353
Build-date: 2026-07-09T11:34:36+00:00
───────────────────────────────────────
    
using keys found in /config/keys
New container detected, installing Heimdall
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Dominant language
Dockerfile
Stars
365
Forks
50
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxserver/docker-heimdall

All issues in linuxserver/docker-heimdall

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.