Everything posted by chodeus
-
[Plugin] FolderView3
sorry, no you just type it on the screen you're viewing. No need to press f12. Just load the troublesome screen, type "fv3debug" and then ctrl+r or F5 to refresh and it'll download a debug .json. Then type fv3debug to turn off debug mode. DM that .json to me here.
-
[Plugin] FolderView3
can you type "fv3debug" and reload the page when this issue occurs and send me that .json so I can have a look? Type "fv3debug" again to stop debugging.
-
[Plugin] FolderView3
What version of unraid are you using? Have you tried clearing your browser cache? When you press F12, can you see any errors in the developer console?
-
[Plugin] FolderView3
Nah that's a legitimate bug, I'm looking into it. Was easy to replicate thankyou EDIT: Now fixed in 2026.05.28.1
-
[Plugin] FolderView3
Awesome mate thankyou for the error report. I have fixed this with a few other things I noticed. ###2026.05.28 - Restart on a Dashboard docker folder now actually restarts containers - Dashboard folder status icon now turns orange pause when every started container is paused, returns to play on resume - Same pause-icon aggregation added to Docker tab and VM tab folder rows - ReferenceError when triggering a custom action on a Dashboard folder configured with "Override default actions" (docker and VM) - Restart no longer fires on stopped containers - VM custom-action "Set Restart" mode now reboots running VMs - Folder context menus now hide actions that wouldn't apply to any child (matches Unraid native per-container menu behaviour)
-
[Plugin] FolderView3
Not a problem! Happy to be of service.
-
[Plugin] FolderView3
Ive got a busy weekend planned but it should be done before Monday. Leave it with me!
- [Plugin] FolderView3
-
[Plugin] FolderView3
-
[Plugin] FolderView3
I can certainly look into that.
-
[Plugin] FolderView3
-
[Plugin] FolderView3
If you select Icon + Label in the preview option it’ll show status but if you’re only using Icon I can probably repurpose the greyscale option that already exists in the folder settings to only greyscale stopped containers. This is what Icon and Label looks like. I’ll look into the grey scale option!
-
[Plugin] FolderView3
All good mate. It could be browser cache if you’ve come from another version of FolderView. Always best to delete browser history and cache if that’s the case.
-
[Plugin] FolderView3
Just so you know what to expect... If you click reset order you delete the userprefs.cfg which will then: Containers: native Unraid alphabetical sort Folders: FV3 layering folder names into the same alphabetical comparison Autostart: FV3 mirroring the combined order Create a new container: appears in its alphabetical slot. If you toggle autostart on, it lands at its alphabetical position in the autostart file. Create a new folder: appears in its alphabetical slot by folder name. Its containers get pulled into the folder. Autostart members appear at the folder's alphabetical position. As soon as you drag/re-order folders/containers you then create a userprefs.cfg which will then: Containers: custom sort order Folders: custom sort order Autostart: FV3 mirroring the order as per layout. Create a new container: goes to the top of the table. If you toggle autostart on, it lands at the top of the autostart file. Create a new folder: goes to the top of the table. Its containers appear at the top of the autostart file until you drag/reorder to your preference.
-
[Plugin] FolderView3
it has been a comical experience troubleshooting this with you. This is now much better aligned with unraid. Enjoy! 2026.05.15 - Fix Reset Order button (was silently broken by FV3's request interceptor) - Folders now sort alphabetically when no manual order is set - VM tab Reset Order also fixed
-
[Plugin] FolderView3
It’s alright I’ve decided to do the destructive testing. On the next main/stable release you should have a working reset order button that puts your containers and folders in alphabetical order. The new container creation will work as per native unraid. Just keep in mind, the folder/container order you see on the docker page will be your auto start order.
-
[Plugin] FolderView3
It would seem we have been teaching each other about Unraid! I've learnt alot looking up what reset order is meant to do and why FolderView breaks its functionality. I've got a fix for you that I'll be pushing to beta, when I'm ready I'll PM you a link and I would love it if you were able to install it and test it.
-
[Plugin] FolderView3
Never in my life have I used that reset order button and I don’t have access to a PC right now so I can’t see its proper behaviour. But I’ll say it again, there is no automatic sorting for newly installed containers or newly created folders. When you install a new container you need to manually place it where you want it to go.
-
[Plugin] FolderView3
What is this “reset order” button on the docker page? If you add containers you’ll need to sort them unless you have a folder setup for regex matching.
-
[Plugin] FolderView3
Haha that’s pretty funny! Glad you got it sorted.
-
[Plugin] FolderView3
-
[Plugin] FolderView3
There’s a green or red padlock button on the docker page. If you’re on a PC, it’ll be the top right of the docker page. This is standard Unraid. Click that so it’s red/unlocked and then drag the folders to create the order you want just like you would if FolderView isn’t installed. The autostart order, without the FolderView plugin installed, is your container order from top to bottom. (And then the wait time comes in there too). I’ve got a graphic in my first post that explains how the autostart order works with FolderView 3.
-
[Plugin] FolderView3
No automatic ordering of folders sorry. I’ve left this as user defined because the order of your folders impacts your container autostart order. Just unlock the docker page and re-arrange your folders however you like.
-
[Plugin] FolderView3
It is possible! It has felt like a long time since i used FolderView2 so I can’t be sure. Glad you’re up and running! Any other questions just reach out.
-
[Plugin] FolderView3
Most default settings are set to off. You can configure your own defaults on the plugin settings page. (Excuse the phone screenshot)