avm/hassio-addons
1
0
Fork 0
mirror of https://github.com/alexbelgium/hassio-addons.git synced 2026-10-03 15:02:41 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
docs/skill-regression-lesson
hassio-addons/filebrowser_quantum/CHANGELOG.md
Alexandre 331af4bcc9 fix(filebrowser_quantum): navigate in place instead of opening a new tab under ingress (#3026) 
The tool views (Tools -> File Size Analyzer, Duplicate Finder, the file list
panel) always pass showLimitedOptions to the context menu, and the context
menu's openParentFolder() hands that same flag to goToItem() as its newTab
argument. The parent folder is therefore opened with
window.open(<absolute url>, '_blank'). Behind Home Assistant ingress that
popup lands on the raw /api/hassio_ingress/<token>/ URL with no Home
Assistant frontend around it to keep the ingress session alive, so the new
tab answers 401 instead of showing the folder.

The ingress vhost now injects the same window.open shim the komga add-on
uses, scoped to the two SPA route prefixes goToItem() builds ('files/' and
'public/share/'), so download and preview popups keep their own tab.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-08-30 07:59:04 +02:00

4.6 KiB
Raw Permalink Blame History

1.5.3.1 (2026-08-29)

  • Fix "open parent directory" in Tools -> File Size Analyzer under Home Assistant ingress. FileBrowser opened the parent folder in a new tab, which lands on the raw ingress URL with no Home Assistant frontend around it to keep the ingress session alive, so the new tab answered 401 instead of showing the folder. The ingress vhost now turns that popup into a navigation of the panel itself. The same fix covers the other tool views and the "go to item" action on search results, which open a new tab the same way. Download and preview popups, links pointing out of the add-on, and direct access on port 8071 are unchanged.

1.5.3 (2026-08-29)

1.5.2 (2026-08-22)

1.5.1.2 (2026-08-19)

  • Fix direct access on port 8071, which was broken in 1.5.1.1: the root redirect pointed at the container-internal port 8072 instead of the published one, and the page it led to referenced assets under a path the add-on did not serve, so every asset returned 404. Requests are now passed through unchanged, with the bare root and the two previously documented /filebrowser_quantum URLs redirected to the app's configured base path.

1.5.1.1 (2026-08-16)

  • Expose the web UI on host port 8071, reachable at <your-ip>:8071 (redirects to /filebrowser_quantum/). Direct access is served by a new, separate nginx vhost that proxies to the same backend Ingress already uses; Ingress itself, and the app's own base URL, are unchanged.

1.5.1 (2026-08-08)

1.5.0 (2026-07-22)

1.4.0-2 (16-07-2026)

  • Minor bugs fixed

1.4.0 (2026-06-20)

1.3.3-8 (2026-06-03)

  • Add default_user_scope option: sets the FileBrowser source path and default user scope (must be an existing absolute directory path, defaults to /)

  • Allow config persistence

1.3.3 (2026-05-19)

1.3.2 (2026-05-16)

1.3.1 (2026-05-02)

1.3.0 (2026-04-23)

1.2.4 (2026-04-04)

1.2.3 (2026-03-28)

1.2.2 (2026-03-14)

1.2.1 (2026-02-28)

1.1.3 (2026-02-23)

1.1.2 (2026-02-14)

1.1.1 (2026-01-13)

1.1.0 (2026-01-10)

1.1.6b0 (2026-01-08)

1.1.5b0 (2026-01-03)

1.2.0 (2025-12-28)

Changelog

1.1.0

  • Initial FileBrowser Quantum add-on.