chodeus

It's only evident for those with all containers in folders. It's only slight but that's the level of OCD I'm working with. I spend a hell of a lot of time iterating changes to try and get it to appear just right. When you expand a folder, to make room for the Uptime Column, the preview row jumps to the left very slightly. This is the jitter I was trying to fix and had fixed by having the Uptime Column push right instead of left when it appears. But unfortunately this is the behaviour you disagreed with and I understand why. I think what I've achieved today is the best it'll get until the new webUI comes in. Hopefully I havent created new edge cases!

Fiery speeches are never required when you're using plugins that people volunteer their free time to maintain. I started maintaining FolderView3 for my own benefit and when I decided to share this with all the FolderView2 users I agreed to take advice/recommendations/suggestions from the users but I did not agree to receive fiery speeches. Unfortunately, sometimes the only way to receive feedback is to push changes because most people only come here when they have issues. Update, and if there's issues please provide me with constructive feedback, screenshots and a debugging .json and I'll do the best I can to keep you and everyone else happy 🙂 Cheers!

I've reverted the uptime column behaviour. I've spent the past 9 hours finding, testing and iterating a "better" way. Hopefully this keeps everyone happy. Update to the next main release and do a hard refresh.

After you do a hard refresh of your browser, can you send me a debug json please. Type “fv3debug” reload the page and then click the button that’ll appear in the middle of your screen and then send me that file. Hopefully that’ll help me see what’s so different with your setup that made this change so catastrophic for you. Thankyou Also “at a glance” uptime doesn’t appear for containers in folders. This behaviour hasn’t changed. The only behavior that has changed is if you expand a folder now, you need to scroll 50pixels to the side to see your uptime column. The jitter that was happening was the container icons were jumping in their row everytime you expanded a folder to make room for the uptime column in the viewport. I suspect you’re having a cache issue regarding the logic change so you might need to do a couple of hard refreshes in a row to sort it out.

So I looked into this further and while it's possible to do it creates a single new settings page for the 1 toggle which doesn't look very good and it's a bit of bloat for 1 option. Also, the risk of running the method you're asking for is you can no longer see when that container is running out of RAM so you may end up scratching your head as to why the container is broken. There is meant to be a big update coming to the docker WebUI so once that lands I'll revisit this and see if there's a tidy way I can include this option but for now I'm on a feature hold.

For anyone updating to 2026.06.22 you'll notice the Uptime column should now load out of the viewport (depending on the size of your screen) and will make the screen scrollable. This was to try reduce the amount of jitter experienced in the preview when expanding and collapsing folders. I made this change because I felt the jitter was more annoying than forcing the Uptime column to appear in the viewport. If this was an unwarranted change in your opinion please let me know. Please do a couple of hard refreshes on the docker page and if that doesn’t resolve any issues send me your debug JSON by typing “fv3debug” on your keyboard when on the docker page, reload the page and then click the orange button that will be in the middle of your screen.

If anyone figures out how to submit an additional plugin or have it detected in the form please let me know. I’m using the 1 repository which contains the profile.xml and app.xml’s. My repository is detected but doesn’t detect the new .xml. https://product.unraid.net/p/unclear-how-to-submit-new-plugin-to-be-published-to-ca EDIT: Turns out as long as your plugin template .xml is in your CA repository it’ll auto detect for review.

In your bazarr container you remove http://[IP]:[PORT:6767] and manually type your server IP and container port in the webui part of the template. Eg: http://192.168.1.35:6767 But I think tomorrow I’ll push a release to main that’ll make this not necessary.

Deletion is permanent — always review the folders offered first.I felt there was a gap in the market for people who wanted the traditional Appdata Cleanup Plugin so I made this Appdata Cleanup NG (next gen). It's aligned with Unraid's security protocols and contains a couple of enhancements. The webUI is very similar to the original plugin. ⚠️ For now I am calling it a BETA plugin though, please read below why. Testers wanted — the core is verified on my box; three things I can't test on my own hardware: - appdata on a non-standard/custom pool (full scan → delete cycle) - a real ZFS dataset delete (zfs destroy) - broad Docker Compose coverage (Compose Manager, ${VAR}/.env, stopped stacks) Help me finalise the testing and I'll continue to maintain this plugin and keep it simple. What's different from the original - compatible with Unraid 6.10.x+ - let me know if you have issues please. - Server-side delete confinement — stays inside the appdata share, never crosses a mount boundary. - ZFS-aware (zfs destroy, opt-in), custom-pool aware, and Docker Compose aware (protects in-use appdata). - Folder sizes, ignore list, filesystem scan, stale-template cleaner, and a one-click diagnostics export (a plugin-specific text file). Install — Plugins → Install Plugin, paste: https://raw.githubusercontent.com/chodeus/appdata.cleanup.ng/main/plugins/appdata.cleanup.ng.plg If you have issues, click Capture Diagnostics in the plugin and send it to me here or attach it to a GitHub issue. Source / issues: https://github.com/chodeus/appdata.cleanup.ng Original CA Cleanup Appdata © 2015–2024 Andrew Zawadzki (Squid) Similarly to FolderView3 this was ported and modified with AI assistance and has received extensive testing for my own use case in my own localised scenario.

Appreciate the bug report. FolderView3 is much stricter than FolderView2 in this area so you'd manually set the webui in the container template. In the next main release, this should work the same as FolderView2. Hoping to have the next main release out by Monday.

I appreciate the report! I have noticed this for some time and it has been on my list to resolve but hasn't been a huge priority because I felt it was very minor. However, I have fixed this in the beta branch and when I'm done trying to resolve @LordVader 's issue I will push these fixes to main branch. Cheers!!

I can dive into it a little deeper at a later date and see what it would look like but I’ve just gone away for a couple of weeks so it’ll be after I get back. I’ll still be looking at bug fixes while I’m away.

Believe the Dashboard — it's not a FolderView3 bug. Both numbers are real, they just measure different things. The Docker tab shows exactly what docker stats reports per container (FolderView3 just sums it per folder). That figure includes page cache — file data the container has touched that Linux keeps in RAM so it over reports. The Dashboard shows the actual footprint, with that cache excluded.

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.

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.