Skip to content

Commit f19e74e

Browse files
author
FolderView Plus Test
committed
Stable release 2026.04.17.04
1 parent 2f07eff commit f19e74e

6 files changed

Lines changed: 20 additions & 9 deletions

File tree

archive/folderview.plus-2026.04.15.21.txz.sha256

Lines changed: 0 additions & 1 deletion
This file was deleted.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
d32eb6e4b6bcc9e0e1a15ff0c165673554ada5dfef1f4172a8d76b8b249c7b58 folderview.plus-2026.04.17.04.txz

docs/releases/2026.04.17.04.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
- Fix: Hardened the Docker runtime privacy toggle so rapid repeated clicks now coalesce to the latest intended state instead of throwing a false save failure and reverting the UI.
22
- UX: Moved the Docker runtime privacy toggle back into the native Basic View control cluster and kept its placement consistent across FolderView, host-only, Command view, and Tree Explorer surfaces.
3-
- Privacy: Extended Docker runtime privacy masking to isolated Command view and Tree Explorer names and icons so those views honor the same privacy toggle as the host list.
3+
- Fix: Extended Docker runtime privacy masking to isolated Command view and Tree Explorer names and icons so those views honor the same privacy toggle as the host list.
44
- Fix: Added stale-response protection to Docker runtime settings saves so fast page-view changes in Settings keep the last selected view instead of letting older requests overwrite newer intent.
55
- Refactor: Split the shared folder editor into a type-aware architecture with dedicated Docker and VM type modules while keeping one editor shell, reducing Docker-only logic inside the shared runtime without forking the page.
66
- UX: Moved Docker-only folder editor rows, preview signals, runtime member enrichment, rules configuration, and smart-default suggestions into the Docker type layer so Docker keeps its richer editor workflow while VM stays scoped to VM-safe controls.
77
- UX: Tightened the VM folder editor path by moving Docker-only field visibility into the VM type layer instead of relying on broad shared-runtime Docker checks.
88
- Fix: The folder editor Rules tab now deep-links into Settings > Advanced > Rules > Auto-assignment and honors explicit Docker or VM rules workspace launch overrides instead of restoring the last basic settings tab.
99
- Fix: VM runtime folders now keep native VM detail rows attached to the VM you actually clicked, including already-expanded detail blocks during folder renders and later host-inserted detail rows after native toggle actions.
10-
- Quality: Expanded regression coverage for the Docker privacy/runtime settings flow, the shared folder editor type contract, the rules workspace deep-link path, and VM detail-row adoption behavior.
10+
- Quality: Cleaned up the Docker privacy persistence path so the shipped runtime passes the unused-symbol guard and the full release CI suite on the final stable build.

folderview.plus.plg

Lines changed: 17 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,27 @@
55
<!ENTITY github "alexphillips-dev/FolderView-Plus">
66
<!ENTITY launch "Settings/FolderViewPlus">
77
<!ENTITY plugdir "/usr/local/emhttp/plugins/&name;">
8-
<!ENTITY pluginURL "https://raw.githubusercontent.com/&github;/dev/folderview.plus.plg">
9-
<!ENTITY version "2026.04.17.03">
10-
<!ENTITY md5 "64ebf4e8677193a1f32176c4b860b78d">
8+
<!ENTITY pluginURL "https://raw.githubusercontent.com/&github;/main/folderview.plus.plg">
9+
<!ENTITY version "2026.04.17.04">
10+
<!ENTITY md5 "94d7657e44de721e3bab931f98809cfd">
1111
]>
1212

1313
<PLUGIN name="&name;" author="&author;" version="&version;" launch="&launch;" pluginURL="&pluginURL;" icon="folder-icon.png" support="https://forums.unraid.net/topic/197631-plugin-folderview-plus/" min="7.0.0">
1414
<CHANGES>
1515

16+
###2026.04.17.04
17+
- Fix: Hardened the Docker runtime privacy toggle so rapid repeated clicks now coalesce to the latest intended state instead of throwing a false save failure and reverting the UI.
18+
- UX: Moved the Docker runtime privacy toggle back into the native Basic View control cluster and kept its placement consistent across FolderView, host-only, Command view, and Tree Explorer surfaces.
19+
- Fix: Extended Docker runtime privacy masking to isolated Command view and Tree Explorer names and icons so those views honor the same privacy toggle as the host list.
20+
- Fix: Added stale-response protection to Docker runtime settings saves so fast page-view changes in Settings keep the last selected view instead of letting older requests overwrite newer intent.
21+
- Refactor: Split the shared folder editor into a type-aware architecture with dedicated Docker and VM type modules while keeping one editor shell, reducing Docker-only logic inside the shared runtime without forking the page.
22+
- UX: Moved Docker-only folder editor rows, preview signals, runtime member enrichment, rules configuration, and smart-default suggestions into the Docker type layer so Docker keeps its richer editor workflow while VM stays scoped to VM-safe controls.
23+
- UX: Tightened the VM folder editor path by moving Docker-only field visibility into the VM type layer instead of relying on broad shared-runtime Docker checks.
24+
- Fix: The folder editor Rules tab now deep-links into Settings > Advanced > Rules > Auto-assignment and honors explicit Docker or VM rules workspace launch overrides instead of restoring the last basic settings tab.
25+
- Fix: VM runtime folders now keep native VM detail rows attached to the VM you actually clicked, including already-expanded detail blocks during folder renders and later host-inserted detail rows after native toggle actions.
26+
- Quality: Cleaned up the Docker privacy persistence path so the shipped runtime passes the unused-symbol guard and the full release CI suite on the final stable build.
27+
28+
1629
###2026.04.17.03
1730
- Fix: VM detail rows now stay attached to the VM you clicked inside folders instead of appearing under the previously expanded VM.
1831
- Fix: Existing expanded VM detail rows move with their VM during folder renders, and later host-inserted detail rows are adopted back under the correct VM owner.
@@ -5481,7 +5494,7 @@
54815494
</CHANGES>
54825495

54835496
<FILE Name="/boot/config/plugins/&name;/&name;-&version;.txz" Run="upgradepkg --install-new">
5484-
<URL>https://raw.githubusercontent.com/&github;/dev/archive/&name;-&version;.txz</URL>
5497+
<URL>https://raw.githubusercontent.com/&github;/main/archive/&name;-&version;.txz</URL>
54855498
<MD5>&md5;</MD5>
54865499
</FILE>
54875500

src/folderview.plus/usr/local/emhttp/plugins/folderview.plus/scripts/docker.js

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3402,7 +3402,6 @@ const flushDockerRuntimePrivacyModePersistence = async () => {
34023402
const setDockerRuntimePrivacyMode = async (enabled, options = {}) => {
34033403
const nextEnabled = enabled === true;
34043404
const previousPrefs = getDockerRuntimePersistedPrefs();
3405-
const previousEnabled = previousPrefs.dashboard?.privacyMode === true;
34063405
if (readDockerRuntimePrivacyMode() === nextEnabled && dockerRuntimePrivacyPendingEnabled === null && !dockerRuntimePrivacyPersistPromise) {
34073406
queueDockerRuntimePrivacyToggleMount();
34083407
return;
@@ -6433,4 +6432,3 @@ if (FOLDER_VIEW_DEBUG_MODE) console.log('[FV3_DEBUG] docker.js: End of script ex
64336432
})(window, window.jQuery || window.$);
64346433

64356434

6436-

0 commit comments

Comments
 (0)