Skip to content

Compatibility and Performance

FolderView Plus Test edited this page Nov 13, 2026 · 19 revisions

Compatibility and Performance

Supported platform

Blocked or unavailable browser storage does not prevent Settings, Docker, VMs, or Dashboard from initializing or saving server preferences. Browser-local UI state and offline preference replay cannot survive reload when storage is blocked. Allow storage for the Unraid site if persistent expansion, picker history, or local diagnostics capture is required.

  • Unraid 7.0.0 or newer.
  • Current major Chrome, Edge, Firefox, and Safari/WebKit.
  • Latest stable FolderView Plus release is supported; dev is best-effort prerelease testing.

Runtime surfaces

Docker

FolderView Plus supports the current legacy Docker-table surface and protects unknown/future native surfaces with safe mode. FolderView, Host list, and Command are the supported plugin views on compatible pages.

Docker runtime reads use capability detection instead of assuming a particular Unraid version or schema. On a compatible legacy page, the preferred path is GraphQL state enrichment over the existing native/PHP inventory. The PHP snapshot remains the automatic fallback and native Unraid controls remain authoritative for actions.

Detected condition FolderView Plus behavior
Compatible API and full container query Uses API-first runtime-state reads.
Compatible targeted container query Uses a targeted read after lifecycle actions when an ID is available.
API endpoint absent or legacy host Uses the PHP snapshot path without requiring configuration.
Introspection denied but supported operations work Uses operation probing and only enables confirmed capabilities.
Permission denied or required query unavailable Disables the unsupported API read path for the page lifecycle and falls back.
Partial data, rate limit, or service outage Preserves known metadata, applies a bounded retry cooldown, and uses fallback.
Schema drift or API identity mismatch Keeps native/PHP structure authoritative; a mismatch alone does not invent rows or request a host reload. Genuine host structural changes use normal reconciliation.
Unknown/future native Docker surface Leaves the host UI untouched and reports safe-mode compatibility evidence.

Virtual machines

VM grouping depends on recognizable native VM rows and host actions. Native state remains the authority.

Dashboard

Dashboard integration consumes the same normalized Docker/VM folder maps but renders cards. It should fail locally without preventing unrelated Dashboard widgets from loading.

Upstream compatibility monitoring

Upstream compatibility review is manual. The scheduled compatibility monitor and workflow-health watchdog have been retired and no longer create or update GitHub issues. Explicit review tools remain available for public Unraid OS/PHP, Docker/VM/Dashboard webGUI, Docker API/native-page, Community Applications, and plugin-manager contracts.

The reviewed Docker API reference baseline acknowledges Unraid API v4.37.3. This is a reference for manual review, not a runtime version requirement: the plugin discovers supported operations and permissions locally. Consult the repository's current baseline before comparing upstream changes.

Maintainers inspect upstream differences, update isolated fixtures where needed, and complete prerelease qualification. Review tools never approve or rewrite the baseline automatically. PHP profile checks are run explicitly in isolated environments; no live Unraid server or stored server credentials are used. Weekly isolated browser fixtures and scheduled security scans continue, and their results are reviewed directly in GitHub Actions.

Optional integrations

  • Compose Manager: supported where compatible metadata/markup exists; report versions and install order for conflicts.
  • Custom themes: use Auto/Host to follow supported host palette variables; Safe/High contrast provide recovery palettes. Imported themes and saved profile customizations are separate layers.
  • Custom CSS/JS: legacy roots remain compatible, but third-party code is outside normal support boundaries until reproduced without overrides.
  • User Scripts: custom folder actions can invoke installed scripts; script behavior itself belongs to that plugin/script.

Aurora Theme

FolderView Plus inherits supported Aurora colors, surfaces, borders, fonts, and button shapes in Auto and Host modes. Docker folder toolbar buttons match the native Aurora action-button sizing. Advanced -> Themes recognizes Aurora's enabled colors stylesheet separately from imported managed themes, including with Aurora's Page enhancements disabled.

Aurora 2026.10.27.1922 recognizes folderview.plus. Its reviewed implementation skips its competing Docker renderer and selected Dashboard handlers when Plus owns those surfaces. Use current versions of both plugins and hard-refresh after updating. This source review is not certification of every host, theme option, or viewport.

Older Aurora builds without Plus recognition can move stored rows or apply compact layouts to folder rows. Disabling Page enhancements, applying, and hard-refreshing remains a temporary comparison or workaround for those builds; colours, fonts, and navigation can remain enabled. Current builds do not require that blanket workaround solely because Plus is installed.

Plus 2026.10.27.05 also fixes an independent idle Docker refresh loop caused by equivalent runtime responses arriving in different entry orders. Update Plus before attributing column movement to Aurora. If movement remains, record the exact Basic/Advanced view and theme settings, leave Docker visible for 60–90 seconds, then export a sanitized support bundle from Settings. See idle column movement.

Theme authors should use the repository's layout ownership contract. Test Docker, VMs, Dashboard, and Settings separately before enabling a new integration.

Stable 2026.10.30.05 fixes another idle Docker refresh loop caused by incomplete or conflicting deferred container details. Repeated autostart animations can occur without Aurora and in multiple browsers. Update Plus and hard-refresh before retesting; the corrected merge preserves accepted identities, membership facts, and newer state. Aurora Settings buttons also ignore unsuitable icon-only header controls when adapting size, with centered icons and readable caption spacing.

In 2026.11.13.05, Aurora's extra Docker page heading/description/support beta chip and extra folder-editor heading are hidden from startup. The editor's own title remains visible, and other themes retain their headers. Docker status labels use the Application column's available width while narrow-column overflow handling stays active. These adjustments do not require disabling Aurora colors or Page enhancements.

NeoRaid

FolderView Plus recognizes an active same-origin NeoRaid color stylesheet separately from the native Unraid base and imported managed themes. It follows light/dark changes and retains readable Update Available badges, usable native Sort controls, and larger touch controls. Sanitized bundles include only bounded mode, density, corner, and font options.

Compatibility fixtures use NeoRaid 2026.10.27c. These synthetic checks do not certify every future theme release or server setup. After updating, hard-refresh and check Settings, Docker, VMs, Dashboard, and theme switching with your chosen NeoRaid options.

Legacy Folder View compatibility

Eligible imports, labels, regex, icons, and override roots from folder.view, folder.view2, and folder.view3 remain supported. Stable selector contracts receive at least a two-stable-release deprecation window before removal after notice.

Active Folder View 2/3 runtimes must not co-own the same Unraid pages. FolderView Plus detects either install order, pauses its Docker/VM/Dashboard injection, preserves saved data, and keeps Settings available. Keep FolderView Plus installed, migrate/back up old data, remove only the detected legacy plugin, and refresh. A resolved banner confirms that FolderView Plus can reactivate.

This legacy-conflict pause is distinct from native-Docker safe mode. Legacy conflict is caused by a known co-installed plugin; native safe mode is caused by an unknown or future host surface.

Performance profiles

Profile Recommended for Behavior
Standard Small/normal layouts Normal motion/refresh behavior; no profile-specific expansion cap.
Adaptive Most medium/large servers Adds safeguards based on size and measured render cost.
Maximum performance Very large or constrained clients Reduced motion, deferred preview work, smallest restore limit, longest minimum refresh interval.

Profiles do not remove members or folder data.

Startup loading

Folder editor scripts can download together while executing in their existing dependency order. Settings does the same within each loading stage and retains the deferred workspace boundary. Docker fetches its runtime during preparation but waits for compatibility and custom-script gates before execution. Dashboard graph libraries remain first-use only and load in dependency order. Unsupported preload hints fall back to the normal loader, and existing error/retry handling remains active.

Only initial Settings runtime enrichment waits until core bootstrap finishes, then until localization settles or its bounded fallback wait expires, before beginning in a later task. Saved configuration tables are prepared first. Explicit manual and diagnostic refreshes do not use that initial-loading gate and still await current runtime data. A failed bootstrap does not start background runtime rendering. When graph loading is retried after an asset failure, the failed file uses a fresh retry URL consistently for its preload and script; already successful dependencies stay cached, with lazy loading and execution order preserved.

Configuration-only editor reads and saves avoid unnecessary Docker/VM service initialization. An unchanged existing-folder Submit leaves without writing; actual changes still wait for confirmed persistence and required Docker order synchronization. These changes reduce avoidable startup/save work without promising a fixed time on every server. See Folder Editor and slow-editor troubleshooting.

Scale model

Deterministic performance fixtures cover:

Scenario Folders Members
Small 25 50
Normal 100 500
Extreme 250 2,000

Benchmarks measure native-row visibility, grouping, Settings bootstrap, editor opening, lifecycle reconciliation, Update All, DOM size, observer callbacks, retained heap after navigation, and bootstrap requests.

Full production-script startup fixtures also cover Settings and Docker cold/warm loads, German/Arabic, zero missing translation keys, rendering completeness, and a representative 23-folder/51-container library alongside small/normal/extreme cases. Docker centers the completed tree once to reduce repeated measurements. Normal editor opens use cached versioned scripts; explicit recovery retries request fresh scripts. Support bundles expose aggregate startup timings without workload identities. Synthetic results do not measure a real server's PHP or network latency.

Routine component and production benchmark inventories are capped at 500 resources. The retained 2,000-resource extreme scenario is excluded and recorded in reports; its timing qualification remains unresolved. A maintainer can explicitly request a larger investigation. Keeping an extreme fixture does not mean every release ran or passed it.

Hosted validation selects benchmarks for performance-sensitive changes. Settings-only or Docker-only changes select that production surface; shared changes select both. VM/Dashboard changes retain component and functional coverage. Exhaustive theme checks are scheduled or explicitly requested, while releases retain focused light/dark desktop/mobile checks. Workspace performance checks follow the owner's explicit instructions separately from hosted CI. Timing failures require investigation and a focused retry, not an automatic budget increase.

Tune a large installation

  1. Select Adaptive.
  2. Enable lazy preview around a meaningful folder/member threshold.
  3. Increase live refresh from the 20-second default.
  4. Reduce collapsed preview depth and graph work.
  5. Use Compact Matrix only when density helps readability.
  6. Remove broad custom CSS and long-running custom JS.
  7. Run Diagnostics performance retest after each major change.

Browser and responsive checks

When reporting rendering problems, test:

  • 100%, 125%, and 150% zoom.
  • Desktop and smartphone widths.
  • Light and dark themes.
  • Reduced motion.
  • A second supported browser.
  • A clean session without custom overrides.

Screenshot placeholder — responsive comparison

Capture the same fictional Docker folder at desktop and smartphone widths with Privacy enabled.

Support boundaries

Unraid core defects, third-party theme/plugin code, browser extensions, and custom scripts are not maintained by FolderView Plus. Reports are still useful when they identify a reproducible integration conflict and include versions plus diagnostics.

Authoritative technical references: Compatibility · Docker API integration · Performance budgets

Clone this wiki locally