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.

9 hours ago, chodeus said:

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.

From the way you wrote and explained it, I believe I'm seeing exactly the new, intended behavior that you are describing. It's not behaving any differently, even after a hard refresh or inside a private window - so I doubt this is a caching issue.

I'm merely stating that this new behavior has unintended and, at least for me, highly undesirable consequences.

9 hours ago, chodeus said:

Also “at a glance” uptime doesn’t appear for containers in folders. This behaviour hasn’t changed.

I know, but your immediate use assumption is already wrong: Not all of my containers are organized in folders!

The primary and most important as well as any in progress of being configured and deployed ones are not, and I want to be able to immediately see their uptime and/or exit code when I load the docker page. This change no longer allows for that and requires horizontal scrolling to access it before even opening any folders. Seriously, trying to configure and deploying new and complex containers is made needlessly harder by this plugin now doing everything it can to constantly hide the exit code.

The "jitter" I'm complaining about is the fact that the "Uptime" column and its content is visible during page load only to then jump outside the viewframe once the page has finished loading.

I'm using the Docker view in "Advanced Mode" and FolderView3 in its "Classic" style defaults.

Making vital information like Uptime and Exit Code only accessible via horizontal scrolling and making it impossible to see both the container name and its uptime at the same time on a 32" wide screen is an absolutely abysmal user experience.

I understand what you are trying to solve with this, I really do. And you clearly value the information you are now hiding less than others. But you unintentionally created far more harm with this change than good, at least for my workflow. If this behavior remains the way it is, I can only revert to the previous build or fork my own private "FolderView4".

1 minute ago, chodeus said:

Hopefully this keeps everyone happy.

Looks like we clicked "Submit" at the exact same moment. I guess I didn't need to write that fiery speech against this new behavior after all.

Anyway, thank you so very much for listening - even anticipating. Can't wait for the next build.

It certainly will make me very, very happy again.

EDIT: I just upgraded to 2026.06.23 and all is well again. I'm seeing extremely little shifting when opening and closing folders, a pixel or two at most. Maybe all it takes for this to work smoothly is to have at least a single container not organized in a folder?

Edited June 23Jun 23 by csb

1 minute ago, csb said:

Looks like we clicked "Submit" at the exact same moment. I guess I didn't need to write that fiery speech against this new behavior after all.

Anyway, thank you so very much for listening - even anticipating. Can't wait for the next build.

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!

Edited June 23Jun 23 by chodeus

I hope you can see that, while passionately making my point for the old and against the changed behavior, at no point did I resort to personal attacks or even demanded anything from you. I believe my feedback was sufficiently descriptive and constructive. Likewise, I truly value your time and contribution and at no point wanted to diminish that.

In fact, I'm now genuinely trying to understand what you even tried to fix with it because I'm simply not seeing the "jitter" you were trying to address. Maybe you could tell me how to reproduce it? There may be better ways to address it.

Just now, csb said:

I hope you can see that, while passionately making my point for the old and against the changed behavior, at no point did I resort to personal attacks or even demanded anything from you. I believe my feedback was sufficiently descriptive and constructive. Likewise, I truly value your time and contribution and at no point wanted to diminish that.

In fact, I'm now genuinely trying to understand what you even tried to fix with it because I'm simply not seeing the "jitter" you were trying to address. Maybe you could tell me how to reproduce it? There may be better ways to address it.

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!

Yeah, I just put all my "loose" containers into a Test-Fold and I see what the problem is. It zeros out and hides the - then empty - Uptime column. Makes sense.

It's not really a lot of jitter, but it shifts a little when opening Folders, and it isn't exactly super smooth. It still beats the usability-monster that is horizontal scrolling by miles, though.

11 minutes ago, chodeus said:

I think what I've achieved today is the best it'll get until the new webUI comes in.

I agree. I don't see anything really wrong with the current implementation other than it being about as rough around the edges as the entire rest of the Unraid interface - feels very native. 😅

I see my post got lost during the forum issues.

@chodeus Any chance you can add a special folder "New / Unassigned" that will contain all of the new containers not assigned yet to any user made folder?

Something like this is achievable with regex "^", but it's a pain in the back to later on assign it to desired folders.

12 hours ago, btTeddy said:

I see my post got lost during the forum issues.

@chodeus Any chance you can add a special folder "New / Unassigned" that will contain all of the new containers not assigned yet to any user made folder?

Something like this is achievable with regex "^", but it's a pain in the back to later on assign it to desired folders.

Sorry I don't use this feature, can you explain the behaviour of what you are hoping to achieve and give me some clarity on why it's a pain with the current regex option?
I am on a feature freeze right now but if you can help me understand this feature a bit better and why the current regex offering isn't ideal then I can look at it later.

On 7/7/2026 at 1:14 AM, chodeus said:

Sorry I don't use this feature, can you explain the behaviour of what you are hoping to achieve and give me some clarity on why it's a pain with the current regex option?
I am on a feature freeze right now but if you can help me understand this feature a bit better and why the current regex offering isn't ideal then I can look at it later.

Let's say you have 2 user made folders with all of the containers.
"Media" and "Download"

Create a new 3rd folder "NEW APPS"
Add regex "^" (this will place every new app in this folder).
Add new container from app store. Let's say "plex"
Plex now will be automatically placed in "NEW APPS"

Now if you want to move "plex" in to "Media" folder you can't do it simply click edit on "Media Folder" and add plex to it. It will not be available on the list, as it is already assigned to another folder (NEW APPS)

The only way to do it is:
Edit "NEW APPS"
remove regex
Edit "Media" folder
add plex
go back to editing new apps
put the regex back


The idea:
Add function of "NEW APPS" folder that will be special folder
It will contain ONLY apps not assigned to any other folder.
Any app in "NEW APPS" will still be seen as unassigned by other folders
App assigned to any other folder will be removed from "NEW APPS"
This way user can just edit any other folder, quickly add app to it. Done

It appears when expanding a folder the containers within the folder are no longer indented on my end, is there a setting i missed for this (i recently did a catch up update to the latest). Used to be the containers were at least slightly indented making it clear which ones are in the folder.

13 hours ago, btTeddy said:

Let's say you have 2 user made folders with all of the containers.
"Media" and "Download"

Create a new 3rd folder "NEW APPS"
Add regex "^" (this will place every new app in this folder).
Add new container from app store. Let's say "plex"
Plex now will be automatically placed in "NEW APPS"

Now if you want to move "plex" in to "Media" folder you can't do it simply click edit on "Media Folder" and add plex to it. It will not be available on the list, as it is already assigned to another folder (NEW APPS)

The only way to do it is:
Edit "NEW APPS"
remove regex
Edit "Media" folder
add plex
go back to editing new apps
put the regex back


The idea:
Add function of "NEW APPS" folder that will be special folder
It will contain ONLY apps not assigned to any other folder.
Any app in "NEW APPS" will still be seen as unassigned by other folders
App assigned to any other folder will be removed from "NEW APPS"
This way user can just edit any other folder, quickly add app to it. Done

Okay awesome, appreciate the explanation. I have created a feature request issue on my Github and I'll look into this in the not too distant future!

6 hours ago, jetuser said:

It appears when expanding a folder the containers within the folder are no longer indented on my end, is there a setting i missed for this (i recently did a catch up update to the latest). Used to be the containers were at least slightly indented making it clear which ones are in the folder.

Turns out I broke this in April and I just got use to the new look without the 30px indentation. I'll bring this indentation back in some shape in the next stable release. Thankyou for raising it!

On 7/9/2026 at 1:11 AM, btTeddy said:

Let's say you have 2 user made folders with all of the containers.
"Media" and "Download"

Create a new 3rd folder "NEW APPS"
Add regex "^" (this will place every new app in this folder).
Add new container from app store. Let's say "plex"
Plex now will be automatically placed in "NEW APPS"

Now if you want to move "plex" in to "Media" folder you can't do it simply click edit on "Media Folder" and add plex to it. It will not be available on the list, as it is already assigned to another folder (NEW APPS)

The only way to do it is:
Edit "NEW APPS"
remove regex
Edit "Media" folder
add plex
go back to editing new apps
put the regex back


The idea:
Add function of "NEW APPS" folder that will be special folder
It will contain ONLY apps not assigned to any other folder.
Any app in "NEW APPS" will still be seen as unassigned by other folders
App assigned to any other folder will be removed from "NEW APPS"
This way user can just edit any other folder, quickly add app to it. Done

So I've been playing around with this.

I can fix the "^" regex to be a "catch all" folder, any container not assigned goes to the folder with the "^" regex.

This doesn't assign the container to the regex folder so you can still pick it and assign containers in the "^" regex folder to other folders.

Is this acceptable behaviour? I think fixing "^" regex is better than adding another toggle that does the same thing.

If you wanted to test it out yourself as it is now, you can load the beta branch.

https://raw.githubusercontent.com/chodeus/folder.view3/beta/folder.view3.plg

On 7/11/2026 at 11:22 AM, chodeus said:

So I've been playing around with this.

I can fix the "^" regex to be a "catch all" folder, any container not assigned goes to the folder with the "^" regex.

This doesn't assign the container to the regex folder so you can still pick it and assign containers in the "^" regex folder to other folders.

Is this acceptable behaviour? I think fixing "^" regex is better than adding another toggle that does the same thing.

If you wanted to test it out yourself as it is now, you can load the beta branch.

https://raw.githubusercontent.com/chodeus/folder.view3/beta/folder.view3.plg

This is actually bang on! Works exactly as expected

All it needs is adding information about this behaviour in regex description and it's done.
Thanks for this.

One more thing that bothers me.
This plugin loads after the basic docker page flashes for a split second. It appears to be just overlay
Wondering if there is any way to avoid this.

Unsure if this will be any help, but there is a plugin in apps store "Custom WebUI CSS" which allows to injects random things but what's interesting, changes are loaded immediately, not like FolderView3 - after a while

https://forums.unraid.net/topic/195276-plugin-simple-custom-webui-css-plugin-for-unraid-72/

15 hours ago, btTeddy said:

This is actually bang on! Works exactly as expected

All it needs is adding information about this behaviour in regex description and it's done.
Thanks for this.

One more thing that bothers me.
This plugin loads after the basic docker page flashes for a split second. It appears to be just overlay
Wondering if there is any way to avoid this.

Unsure if this will be any help, but there is a plugin in apps store "Custom WebUI CSS" which allows to injects random things but what's interesting, changes are loaded immediately, not like FolderView3 - after a while

https://forums.unraid.net/topic/195276-plugin-simple-custom-webui-css-plugin-for-unraid-72/

Unfortunately that plugin and FolderView are completely different. FolderView has to wait for the Unraid page to load to gather the container/vm information and then build the page from that which is why the flash happens.

I have made a small change in the beta branch, if you're still running it, that should improve the "flash" by ~300ms. Version 2026.07.13.1 if you're happy to run it and let me know what you think? I'm going to run it for probably a week so I can try get some solid testing out of it before I push it to main with the regex fix.

@chodeus

Yes I'm still running beta version.
Updated just now to 2026.07.13.1 - works like a charm. I'll stay on it for the time being, to see if there are any issues.

The flash of the plain docker page is no longer there.
Takes a few ms to load the page (always did, as docker page is slow anyway), but now without the flash it's a lot better.
Regex "^" it's great - maybe once you're bored it's worth to turn it in to a toggle switch (like other options) as many users just don't touch regex, so they might never know about this great addition.

Wondering if you can do a few more updates to the docker page.
Once folder expanded, unraid page displays a lot of pointless informations that really should be only visible in advanced view. like Container ID, Repository (which gets trimmed if to long anyway)

Wondering if you can make toggle switches to optionaly:
Show <OPTION> only in Advanced view.
e.g. Show Volume Mappings only in Advanced view

<Options>:
Repository
LAN IP:Port
Container Port
Container IP / MAC
Network
Version
Container ID
Repository
up-to-date (pointless info when using orange highlighting for updates

TBH. Allow user to move to advanced view every single column and displayed information


Unraid default page have just to much info for a basic view.
Most of it should be in advanced view, or at least selectable by the user.

It's not a bad idea but that's a decent structural change. I'm trying to not make any major structural changes because the new Docker page that is due is a huge structural change itself and I'm not really sure if that level of effort is worth it right now. Feel free to write a feature requests here https://github.com/chodeus/folder.view3/issues so I don't lose track and I can see how this might work depending on how far away the new Docker page is.

I'm going to avoid yet another toggle for now but update documentation (the tooltip is already update to highlight using "^") to raise awareness around the catch all scenario and how to use it.

Thankyou for your help in getting this plugin improved! I'll be release a stable release soon.

On 7/16/2026 at 7:25 AM, chodeus said:

Docker page that is due is a huge structural change itself

Fair enough, if this is actually happening anytime soon
It had a status Soon™ for as long as I remember.

If that's actually the case then no point wasting any more time.

Just now, btTeddy said:

Fair enough, if this is actually happening anytime soon
It had a status Soon™ for as long as I remember.

If that's actually the case then no point wasting any more time.

I'm keeping my ear to the ground but i've seen snips of the beta version so I think it's not far away.