chodeus

What is your preview context set to for the folders where clicking the container icon doesn’t work? It should be default or advanced.

Just FYI for those playing at home, I updated to 7.3.0 stable and haven't noticed any issues.

happy days, glad to hear it!

I have not tested FolderView3 past Unraid 7.2.5 so I cant comment sorry. When 7.3 moves to stable I will test it then but sounds like you're back in action. I've shipped a small patch, if that doesn't fix this for you I'm going to need a lot more info. V2026.05.07 - if you could please update.

Which version of folderview did you come from? I’ll have a look at this shortly but firstly a lot of these appearance issues, when coming from folderview2 or folderview plus, can be resolved with clearing cache/browser history. If you can give that a go and report back that would be awesome.

I should be able to release this fix tomorrow, I’ve got it sorted I’m just trying to refine a couple of column widths for users that do have containers not in folders and then make this all work with custom presets.

I see what I’ve done. I missed this from my testing since I do have a container floating around outside a folder. That shouldn’t appear if everything is in a folder and should only appear for advanced view. Leave it with me!

Im just pushing a main/stable release now that should resolve most of your firefox issues. Plus some other edge cases I experienced while testing and troubleshooting. I have updated the logic behind this, let me know if it's still not accurate for you.

For others experiencing a similar issue please note that this was primarily a cache issue. If you have moved from another folderview to FolderView3 please delete your cache/history. Also for Firefox users, some of the custom CSS will not view correctly. I am working on resolving this but it is challenging. I'd suggest you move to a good browser like Chrome 🤣

Glad you're enjoying it! What version of Unraid are you using? I haven't been able to recreate any of the bugs you have mentioned, would you mind grabbing some debug info for me so I can try figure out why you're having this issue? If you go to your docker screen and type "fv3debug" and then refresh the screen it should trigger a .json to donwload. Once that has downloaded type "fv3debug" again and refresh to turn off debug mode. Can you please send me that .json?

You got your wish, I included the margin "fix" in the latest stable build. For now the incognito button is staying where it is.

You do realise I have given you the tools to allow you to do whatever you like with the docker and VM pages? I like the style of the semi hidden incognito button which is why I built it the way I did. I want to bring a modern feel to the UI, not keep us in the dark ages. Anyway, while I wait for other opinions to come in if you want it how your screenshot is, add this to your docker and VM custom CSS. .ToggleViewMode:has(.fv3-incognito-btn) > span { margin-left: 16px; } .fv3-incognito-btn { all: unset; cursor: pointer; display: inline-flex; align-items: center; gap: 10px; font: inherit; color: inherit; } .fv3-incognito-btn.fv3-incognito-active { color: #0088cc; } .fv3-incognito-btn::before { content: 'Incognito Mode'; font-size: 1.1rem; text-transform: uppercase; letter-spacing: 1px; } .fv3-incognito-btn i { width: 25px; height: 11px; min-width: 25px; background: #ccc; border: 1px solid #aaa; border-radius: 4px; position: relative; display: inline-block; font-size: 0; line-height: 0; vertical-align: middle; margin: 1px 0; } .fv3-incognito-btn i::before { content: ''; position: absolute; width: 12px; height: 11px; background: #fafafa; border: 1px solid #aaa; border-radius: 4px; top: -1px; left: -1px; transition: left 0.2s; font-family: inherit; } .fv3-incognito-btn.fv3-incognito-active i { background: #486dba; } .fv3-incognito-btn.fv3-incognito-active i::before { left: 13px; } .fv3-incognito-btn:only-child { margin-left: auto; }

If Unraid reduce the spacing around the advanced view toggle, I will move or incorporate the incognito button again so it doesnt take up any extra space... again.

The incognito button does not take up any additional room than what was there pre-inclusion of the button or when compared to native unraid. If you want to gain more room above the table please see this method. https://github.com/chodeus/folder.view3/issues/6 You might need to buy a larger monitor 😉

I've been working with @myki to improve backwards compatibility with Unraid <7.2. That's the reason for the errors above. If anyone wants to help me improve backwards compatibility I can share my beta branch install link with you, I'd love some help!

If you click “console” do any errors appear there when you refresh the page? What version of FolderView did you migrate from and how did you do it? Also, does the VM page have an “add folder” button? While on your docker page, just type “fv3debug” and then reload the page and please PM me the debug.json that’ll get automatically downloaded. Compatibility earlier than Unraid 7.2 is negligible but I’m happy to work to improve the compatibility.

Any error logs in dev console while on the docker and/or VM page? (F12) Have you tried a hard refresh on your browser and a cache clear?

Awesome. I’ll think about what I can do for the orange preset but all the others should be fine.

Short answer is you cant do it cleanly. Just released a fix for this so "orange text on update" will override the preset colour for containers that need updating.

Happy days! Glad it sorted itself out 😂

Did you capture any dev console logs? What compose manager plugin and version are you using?

Yeah valid point. I’ll look at a tidy way to incorporate that. Thankyou for the suggestion!

Hi all, I wanted to update you on what I've brought to stable release v2026.04.04. Sorry for the essay below! It'll look and feel like the same FolderView but a bunch of things underneath got a decent overhaul, plus some new power-user features. Now I said I wasn't going to refactor the original plugin but I have to apologise because I've had to do a partial refactor to combine duplicate lines of code to make this easier to maintain and prevent regression or forgetting to update the other lines of code for the 1 fix. Anyway, what's new?CSS Tool — Built-in theme manager right in the Settings page. Import themes from GitHub repos, toggle them on/off, get notified when updates are available. Also includes a variable editor with colour pickers, presets and an advanced CSS text area. Also security scanning for unsafe imports. Folder Defaults — Set global defaults for preview mode, overflow behaviour, context menu, and more. Hit "Apply to All" to push defaults to every folder at once instead of editing them one by one. Full Backup & Restore — Export everything (all folder configs, settings, CSS config, installed themes) to a single JSON file. Import it back on a fresh install. Incognito Mode — (this one is my favourite) Blurs container/VM names, and folder names. If you think anything else needs to be blurred out please let me know. Updated Folder Editor— Settings organised into collapsible sections. Cleaner layout, same options. Unraid 7.2+ API Integration— If you're on 7.2+, the plugin now uses WebSocket for real-time stats (faster, lighter than SSE), GraphQL for container/VM actions, and automatically syncs your folder structure to Unraid's native Docker Organizer (when this is implemented). Falls back gracefully on older versions. Mobile & Touch Improvements — General improvements Here's the before and afters for those that want to make sure I have kept the plugin lean. Before (v2026.04.01): ~5,900 lines JS / ~1,400 lines CSS / ~800 lines PHP — 186 KB package After (v2026.04.04): ~8,200 lines JS / ~3,200 lines CSS / ~1,600 lines PHP — 223 KB package Alternate Plugin 1: ~58,900 lines JS / ~14,500 lines CSS, ~8,9030lines PHP - 14.2 MB package Can always view the repository for more details https://github.com/chodeus/folder.view3 I feel like I have tested this extensively but there's always edge cases or things I may have missed or not thought about. Please let me know ASAP if you spot anything. If you have additional feature requests please let me know. Rolling back to previous version: If you run into any issues, you can roll back to v2026.04.01: - Go to Plugins > Install Plugin - Paste: https://raw.githubusercontent.com/chodeus/folder.view3/v2026.04.01/folder.view3.plg - Click Install This will downgrade back to the previous stable release. Please report any issues so I can get them fixed quickly.

What ones have you tried?

There’s nothing stopping people from disclosing AI involvement now but they choose not to. As much as I support this system you have proposed, you are still relying on people being honest and telling the truth. At the end of the day, it comes down to the user to research developers and browse support forums and installing at their own risk because there is no verification process on plugins or containers (I think?). What would be helpful is some security guidelines or fundamentals clearly documented somewhere for those wishing to completely vibe code to review and adhere to, or have AI adhere to. It could also be used as a learning tool for those just starting out. I know @mstrhakr has started a plugin guide and I’ve found myself reviewing that from time to time because it saves me endless hours searching forum posts for key words. If not build on a guideline, I do think some sort of review panel with Community Devs, or higher, should exist as a “slop or not” and security check for all plugins, not just those flagged as AI influenced. This would benefit many aspects of the community but unfortunately it is asking Developers+ to commit spare time that they may not have. Also, I remember reading somewhere that the Community Developer user class on the forums isn’t just handed out, that’s only given to those developers that have shown to support a good product and I think it should stay that way. I think if we were able to build a proper guideline (building on what @mstrhakr has already built maybe?) highlighting the important aspects of development and make it visible and easy to access, this would definitely help new and potentially existing developers. Again, the issue being that it’s going to take up someone’s free time.