Skip to content

Compatibility and Performance

FolderView Plus Test edited this page Aug 21, 2026 · 4 revisions

Compatibility and Performance

Supported platform

  • 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 structural container mismatch Does not invent rows; requests one native structural refresh when needed.
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

The repository checks public official upstream contracts every day. The reviewed baseline covers stable/prerelease Unraid versions, PHP runtimes, Docker/VM/Dashboard webGUI files, Docker API/native-page signals, Community Applications publication, and plugin-manager install, update, downgrade, removal, pre/post-check, and change-display paths.

Upstream drift opens or updates one deduplicated review issue. Automation never approves a new baseline or changes runtime behavior automatically; a maintainer must inspect the upstream difference, update isolated fixtures where needed, and complete prerelease qualification. The monitor uses public repositories and synthetic PHP/runtime profiles—not a live Unraid server or stored server credentials.

Optional integrations

  • Compose Manager: supported where compatible metadata/markup exists; report versions and install order for conflicts.
  • Custom themes: use Auto/Safe/High contrast and shared theme tokens.
  • 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.

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.

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.

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