12 minutes ago, chodeus said:

Your heading of the column is missing.

If you mean uptime, it's by design of custom CSS

11 minutes ago, Masterwishx said:

Your default css is fine, it was issue in my custom CSS.

Yeah mine looks a lot better than your first screenshot but it could do with widening a little bit for other people that don’t have a custom CSS. Yours looks really good!

The CPU and Memory load column heading like my screenshot.

This was taken on my phone.

6 minutes ago, chodeus said:

Yeah mine looks a lot better than your first screenshot but it could do with widening a little bit for other people that don’t have a custom CSS. Yours looks really good!

The CPU and Memory load column heading like my screenshot.

This was taken on my phone.

Yep it seems need more width...

When made 145px width, it was looks OK but sometime was drop down becosue no space, so made 150px in my case...

If you interested I used @Mattaton CSS with small customize by me :

https://github.com/masterwishx/folder.view.custom.css

17 minutes ago, chodeus said:

Yeah mine looks a lot better than your first screenshot but it could do with widening a little bit for other people that don’t have a custom CSS. Yours looks really good!

The CPU and Memory load column heading like my screenshot.

This was taken on my phone.

Ohh I see now, Thanks

6 minutes ago, Masterwishx said:

Yep it seems need more width...

When made 145px width, it was looks OK but sometime was drop down becosue no space, so made 150px in my case...

If you interested I used @Mattaton CSS with small customize by me :

https://github.com/masterwishx/folder.view.custom.css

That’s pretty cool! Thankyou.

If you notice any bugs that aren’t relevant to your customer css please let me know!

29 minutes ago, chodeus said:

That’s pretty cool! Thankyou.

If you notice any bugs that aren’t relevant to your customer css please let me know!

Thanks ,fixed :

Looks good!

DOCKER LABELS

You can add docker containers to folders by adding the label "folder.view2", the value of the label is the name of the folder.

Is this working for anybody? I am using folder.view2 - latest version.

Is this only working for docker container created with the unraid GUI or should this work as well using the compose plugin?

I tried several compose files but folder.view2 is not creating the folder automatically when adding a label to my service like:

labels:
      net.unraid.docker.managed: 'composeman'
      net.unraid.docker.webui: 'http://10.10.20.20'
      net.unraid.docker.icon: 'https://phpipam.net/css/images/logo_icon.png'
      folder.view2: 'phpipam'

Do I have to enable or trigger it somewhere or did I do it wrong?

3 hours ago, chodeus said:

Looks good!

Forgot to mention in VMS tab i has wrong containers in Folders in webui :

vm.json

7 hours ago, Masterwishx said:

Forgot to mention in VMS tab i has wrong containers in Folders in webui :

vm.json

Just to be clear, this is nothing to do with your custom css or anything you’ve modified?

I don’t use folders for VMs because I only have the 1 VM but if this is something broken in folderview2 I can have a look.

7 hours ago, UnKwicks said:

Is this working for anybody? I am using folder.view2 - latest version.

Is this only working for docker container created with the unraid GUI or should this work as well using the compose plugin?

I tried several compose files but folder.view2 is not creating the folder automatically when adding a label to my service like:

labels:
      net.unraid.docker.managed: 'composeman'
      net.unraid.docker.webui: 'http://10.10.20.20'
      net.unraid.docker.icon: 'https://phpipam.net/css/images/logo_icon.png'
      folder.view2: 'phpipam'

Do I have to enable or trigger it somewhere or did I do it wrong?

I don’t use compose but do you not need to create the folder first?

Also “latest version” doesn’t help sorry, I need to know your version number.

Edited February 6Feb 6 by chodeus

When writing files an unraid yes, we have to have the folders pre-created before the compost file runs as it will not be able to understand or maintain access nor create the folders needed like the unraid templates due for the CA.

This is due to the docker file having absolute path and how bind mounts work in Docker compose.

This is why a lot of my guides will go over having a default understanding of file passing and a very specific buying amount information at the very bottom of my compose file.

And at the very beginning before you even download or insert a compose file to unraid, you've already run the make folder, commands and the app data folder or the locations where you're looking to store the data...

Example:

https://bmartino1.weebly.com/immich-on-unraid-docker-compose-guide.html

36 minutes ago, bmartino1 said:

When writing files an unraid yes, we have to have the folders pre-created before the compost file runs as it will not be able to understand or maintain access nor create the folders needed like the unraid templates due for the CA.

This is due to the docker file having absolute path and how bind mounts work in Docker compose.

This is why a lot of my guides will go over having a default understanding of file passing and a very specific buying amount information at the very bottom of my compose file.

And at the very beginning before you even download or insert a compose file to unraid, you've already run the make folder, commands and the app data folder or the locations where you're looking to store the data...

Example:

https://bmartino1.weebly.com/immich-on-unraid-docker-compose-guide.html

Okay perfect. Do you use folderview2 with compose? Can you verify what the above person wrote is not a bug and just user error?

Unfortunately I don’t have the luxury of a test rig.

8 hours ago, chodeus said:

I can have a look.

Yep, this seems broken in plugin, have no custom CSS for it. You can see it by image

31 minutes ago, chodeus said:

Okay perfect. Do you use folderview2 with compose? Can you verify what the above person wrote is not a bug and just user error?

Unfortunately I don’t have the luxury of a test rig.

I think there was a misunderstanding. @bmartino1 is talking about appdata folders on the filesystem. I was talking about folders in folder-view. Anyway, I testet precreating the folder.view folder. Then startet my stack and the container are getting sorted into the folder. So just adding the label is not enough, we have to create the folder.view folder before. Maybe this can be added to the first post of this thread.

Edited February 7Feb 7 by UnKwicks

20 minutes ago, UnKwicks said:

I think there was a misunderstanding. @bmartino1 is talking about appdata folders on the filesystem. I was talking about folders in folder-view. Anyway, I testet precreating the folder.view folder. Then startet my stack and the container are getting sorted into the folder. So just adding the label is not enough, we have to create the folder.view folder before. Maybe this can be added to the first post of this thread.

To be fair, the dev that started this thread hasn't posted in a few months. If you're running the version from the community apps store you'll be coming up with quite a few issues.

On 5/16/2025 at 8:01 PM, VladoPortos said:

Guys, not a simple fix as I hoped... had to rewrite some stuff due to changes in unraid 7+ also the css theme for folderview will need to be updated so if you are brave enough to test this beta please disable theme.

 

It works for me ( as usually that does not mean much... ) but also @Masterwishx  was helping a lot with testing and seems like its working for him as well.

- Advance view was reworked a lot

- Added TailScale link to advanced view ( for some reason the translation is not loaded for it, could be a cache issue... but report back if it does look like this for you and I will have to rework the language/translation part next )

 

- The links in the folder priew should work again

 

 

- In this "beta" there is a debug option turned on, and its talking to web console a bit whats happening when docker tab loads etc... this help when you have issue you can save it to file and send it to me. 

- It also create log in /tmp/folder_view2_php_debug.log so you can drop that for me as well..

 

So please give it a test and let me know, then I will update Unraid listing and make it the default version (just with debug turned off :D)

folder.view2.plgfolder.view2-2025.05.16.txz

 

So this still isn't working for me, opening it up and using the menu WebUI button works, preview on default. Example of working button:

But just clicking the direct WebUI button inside the folders isn't working. Example of not working WebUI Button:

I'm on Unraid 7.2.3, using folderview2 2025.04.13 which is showing up to date in plugins.

2 minutes ago, TacHub said:

So this still isn't working for me, opening it up and using the menu WebUI button works, preview on default. Example of working button:

But just clicking the direct WebUI button inside the folders isn't working. Example of not working WebUI Button:

I'm on Unraid 7.2.3, using folderview2 2025.04.13 which is showing up to date in plugins.

I believe this is only fixed in one of his betas, I’m not sure which one because I never ran it.

This is fixed in the fork I modified though. If you’re wanting this resolved I’ve explained what I have done here. https://forums.unraid.net/topic/189167-plugin-folderview2/page/14/#findComment-1606306

I stopped using it with compose. In a default can install on v 6.9

It has issues since. And a few authors changed edits

When it did work I had no issues with compose.more docker start order...

Folder view broke parts of the unraid UI labeling which is why I installed and tested with it. I would need to install the plugin and play around. I can neither confirm nor deny user error. As quite a bit if we. Ui code css and other has changed since 6.9 to 7.2

Bugs I've even reported due to css text graphics error and not being shown...

I'm also not as active with edits as I can only suggest things for fixes as there was a folder needed in 6.9 when either transioned where we could add and edit some code on the USB in this folder or add scripts to test fix... Som the best I can do is install the plugin and report back.

10 hours ago, chodeus said:

To be fair, the dev that started this thread hasn't posted in a few months. If you're running the version from the community apps store you'll be coming up with quite a few issues.

Maybe you need to post also to CA apps your fixed version :)

before and after on a unraid no pre exisitng files.

default unradi diaplay settings. (as ther are konwn chagnes per the OS builds and chagnes...)
https://docs.unraid.net/category/release-notes/
...

Example...
Plugins

The Theme Engine, Dark Theme, Dynamix Date Time, and Flash Remount plugins are incompatible and will be automatically uninstalled, as will outdated versions of Unraid Connect.

Please upgrade all plugins, particularly Unraid Connect and the Nvidia driver, before updating. Note that some plugins may have visual issues in this release; please give plugin authors time to make adjustments.

For other known issues, see the 7.1.4 release notes.

As I'm not aware of an update nor fixes from either this plugin or the theme engine due ot hte changes... BUT IT WAS NOTED!

so now for the ca install...

Current Version

2025.04.13

*Note the plugin change log as well... as there has been alot of back and forth...

the file manger apears to be working as it should

*NOTE THIS IS A FRESH INSTALL NO PRE EXISITNG FOLDERS SETTINGS EDITS!

Time to add a folder. I will separate the Immich web ui and the compse dockers...

so now I have a blank folder to begin moving things into:

*Save empty to make sure files are in (General test) then edit compose...

Time to include them:

Don't forget to hit "Submit":

So far everything is working as it should...

This said we have a webui plugin display area and a compose plugin setup error issue.

See Docker COmpose based on services can have whats known as docker depends and also controls ther own start order.

Usualy its via the services Order of operation...
https://bmartino1.weebly.com/immich-on-unraid-docker-compose-guide.html
example:

SO compose would start immich-server
then hit depends on and the docker would be ina "pause/standby not up but image created state...

then it woudl load immich-machiune-learning and so on and so forth
UNTILL we hit teh necessary depeds on and sometimes health chcecks and conditoion the other stack docker needs to complete befre immich-server fully starts...

SO I can see if one started to use the compose Down, Compose up and especially the update stack button errors occur due to how FOLDER VIEW is now controlling the startup order!
-SOmehitng I hit before and decided that I'm not runing enoth docer adn the plugin is too out of sink and now getting updates fast enoth and not worth the them edits...
Unraid devs made it clear to use there thems and have ther own html/css code issues them selves...

SO can I confirm a potental issue Yes. Is what the user experienceing this plugin maybee, it could aslo be that twe are useing another plugin and they don't mix well due to under line labels of what is being manged by want....

Unraid and teh compose plugin intrdue an adataionl docker orcestration layer.
This is why adational labeling:

CA apps are labled and use under label dockerman ...

And older intergrations of the OG folder view plugin i have immich so i would expect this plugin to reuse the old lableing at docker creation and/or this to be the same folder name (note i said compse and added the docekr not immich!

SO yes there a weird compse intergration!

But ITs per user per cleint issues I can't confirm nor deny and as I'm able to do advance workarounds. Some not stable enoth to share. It wasn't worth the time to go over and expalin. as Vlad has done very well with keeping up and maintin what does adn suposed to work. But given the recent web ui edits and chanes no I don't think this plugin will support nor fix issues with Comnpsoe as the compsoe plugin is still run comse version 2 when version 3 has been out (other form post to update to lattest binary)...

that said a FRESH INSTALL I don't see the isseus the client mentions in the post and more jumbped in to clarify and clear confisuion on compose... as there are other things one must due to mkae it play nice with teh unriad web ui...

4 hours ago, Masterwishx said:

Maybe you need to post also to CA apps your fixed version :)

Yeah I would like to but I feel like I need a docker compose user to test my version before I do that.

I’m still surprised to read that not all users are on Unraid v7+.

4 hours ago, bmartino1 said:

before and after on a unraid no pre exisitng files.

default unradi diaplay settings. (as ther are konwn chagnes per the OS builds and chagnes...)
https://docs.unraid.net/category/release-notes/
...

Example...
Plugins

The Theme Engine, Dark Theme, Dynamix Date Time, and Flash Remount plugins are incompatible and will be automatically uninstalled, as will outdated versions of Unraid Connect.

Please upgrade all plugins, particularly Unraid Connect and the Nvidia driver, before updating. Note that some plugins may have visual issues in this release; please give plugin authors time to make adjustments.

For other known issues, see the 7.1.4 release notes.

As I'm not aware of an update nor fixes from either this plugin or the theme engine due ot hte changes... BUT IT WAS NOTED!

so now for the ca install...

Current Version

2025.04.13

*Note the plugin change log as well... as there has been alot of back and forth...

the file manger apears to be working as it should

*NOTE THIS IS A FRESH INSTALL NO PRE EXISITNG FOLDERS SETTINGS EDITS!

Time to add a folder. I will separate the Immich web ui and the compse dockers...

so now I have a blank folder to begin moving things into:

*Save empty to make sure files are in (General test) then edit compose...

Time to include them:

Don't forget to hit "Submit":

So far everything is working as it should...

This said we have a webui plugin display area and a compose plugin setup error issue.

See Docker COmpose based on services can have whats known as docker depends and also controls ther own start order.

Usualy its via the services Order of operation...
https://bmartino1.weebly.com/immich-on-unraid-docker-compose-guide.html
example:

SO compose would start immich-server
then hit depends on and the docker would be ina "pause/standby not up but image created state...

then it woudl load immich-machiune-learning and so on and so forth
UNTILL we hit teh necessary depeds on and sometimes health chcecks and conditoion the other stack docker needs to complete befre immich-server fully starts...

SO I can see if one started to use the compose Down, Compose up and especially the update stack button errors occur due to how FOLDER VIEW is now controlling the startup order!
-SOmehitng I hit before and decided that I'm not runing enoth docer adn the plugin is too out of sink and now getting updates fast enoth and not worth the them edits...
Unraid devs made it clear to use there thems and have ther own html/css code issues them selves...

SO can I confirm a potental issue Yes. Is what the user experienceing this plugin maybee, it could aslo be that twe are useing another plugin and they don't mix well due to under line labels of what is being manged by want....

Unraid and teh compose plugin intrdue an adataionl docker orcestration layer.
This is why adational labeling:

CA apps are labled and use under label dockerman ...

And older intergrations of the OG folder view plugin i have immich so i would expect this plugin to reuse the old lableing at docker creation and/or this to be the same folder name (note i said compse and added the docekr not immich!

SO yes there a weird compse intergration!

But ITs per user per cleint issues I can't confirm nor deny and as I'm able to do advance workarounds. Some not stable enoth to share. It wasn't worth the time to go over and expalin. as Vlad has done very well with keeping up and maintin what does adn suposed to work. But given the recent web ui edits and chanes no I don't think this plugin will support nor fix issues with Comnpsoe as the compsoe plugin is still run comse version 2 when version 3 has been out (other form post to update to lattest binary)...

that said a FRESH INSTALL I don't see the isseus the client mentions in the post and more jumbped in to clarify and clear confisuion on compose... as there are other things one must due to mkae it play nice with teh unriad web ui...

So they do work well with each other but the start order between the compose plugin and folder view cause conflicts.

Thanks for jumping on and running that test and highlighting that. Hopefully the other people running compose can see this.

Just a FYI Note over the years and watching/lurking on the forum...

in earlier versions of unraid v5 v6 era... when Docker Compose was actively being developed and the OG folder.view plugin was made, the 2 maintainers worked with each other. (This is where you see my OG labeling of folder.view foldername.) As originally, if both plugins were installed, it would auto make the folder in the docker and Compose ran the order so no conflict...

as AT first time compose creation, if folder.view was installed, it would make and add the Docker containers to that folder. Data lost on the forum and buried in the support.
https://forums.unraid.net/topic/114415-plugin-docker-compose-manager/

Vlad said he kept the legacy code of the OG plugin and Compose maintainer hasn't made much edits to the OG code. So I'm not sure with labeling of fodler.veiw2 what the labeling, if any of it, was save. Nor have I seen the folder.view code labeling work, but I haven't done good testing as I'm in and out.

I believe that folder.vew was meant for adaptation to unraid CA dockerman orchestration, and its best to not use folder view with compose with the above docker compose potential issues. Not that one couldn't... just ill-advised, as its a question of who, what, where,where and when... in terms of the file / stack...

I haven't seen issues when keeps all stack dockers in only folder like my example with compose and immich all of the dockers stack for immich.

but if you separate, like, all database dockers in a folder and break the potential for the start order. That's when I remember seeing some bugs. Its been a while since testing....
which I would say is out of scope for the plugin and would require edits / workarounds...

Even Vlad attempted backwards push forward code rename still goes over the backup and restore in folder v2
https://github.com/VladoPortos/folder.view2

So from my point of view I would say avoid Compose in conjunction with the plugin and do so at your own risk. not that one couldn't.

I don’t use compose so I apologise for my ignorance.

I see a few different compose managers, do they all overwrite the Unraid docker container start up? Do they fundamentally function the same and just appear different?

From the screenshots I’ve seen it looks like the compose managers almost do what folderview does as far as organising the containers.

Are you wanting folderview2 to ignore the container start up order if compose is installed?