13 minutes ago, bmartino1 said:

is this compatible with the folder view 3 plugin chagnes?

or should i uninstall both the compose manger and folder view 3 before attempting this plugin?

https://forums.unraid.net/topic/197223-plugin-folderview3/

I have done work on the dev branch specifically to fix a bug that interfered with that plugin. The beta branch has that fix already. With that said, the beta is closing tomorrow and the changes will be merged to main. I JUST fixed a but that interfered with Folder View Plus so that should also be compatible with the latest beta.

12 minutes ago, mstrhakr said:

I have done work on the dev branch specifically to fix a bug that interfered with that plugin. The beta branch has that fix already. With that said, the beta is closing tomorrow and the changes will be merged to main. I JUST fixed a but that interfered with Folder View Plus so that should also be compatible with the latest beta.

cool, thank you looking forward to trying this.

10 hours ago, mstrhakr said:

Safest will always be:

• Compose down on everything.

• Back up all the compose files and env files.

• Uninstall current plugin

• Install new plugin

With that said, I have done in place upgrades from the original the the new one with no issues. Going down for all is still safest though.

Thanks I just did the upgrade following the steps above and it worked like a charm. My old stacks were found by the new plugin without any problem.

10 hours ago, bmartino1 said:

cool, thank you looking forward to trying this.

I’m running both plugins for testing reasons. The beta compose manager is compatible.

The only issue to date, which is fixed in compose manager plus beta, was when you hide compose containers. Everything else appeared to work fine with FolderView3.

I’m happy to work with @mstrhakr to keep both plugins compatible with each other.

Edited March 27Mar 27 by chodeus

@mstrhakr The latest release of FolderView Plus fixed the compatibility issues with Compose Manager. It's now working with no issues on the main and beta. Github | Forum Post

Edited March 27Mar 27 by XCrownedClownsX

1 hour ago, XCrownedClownsX said:

@mstrhakr The latest release of FolderView Plus fixed the compatibility issues with Compose Manager. It's now working with no issues on the main and beta. Github | Forum Post

Yea I fixed it from my side in the beta also. just name-spaced escapeHtml to composeEscapeHtml to avoid potential issues in the future.

Also that FolderView Plus setup wizard is super cool lol.

12 minutes ago, mstrhakr said:

Yea I fixed it from my side in the beta also. just name-spaced escapeHtml to composeEscapeHtml to avoid potential issues in the future.

Also that FolderView Plus setup wizard is super cool lol.

Appreciate it! I'm doing a lot of work to enhance the UI and clean things up in the coming releases for better UI/UX.

FYI: The beta will be going live today (merged to main) around 6PM EST. If you have any issues let me know before then.

not sure if tempalte is pointing to the githb repo yet

atempted to install form CA Stabe not beta.

Downloading plugin plugin: installing: compose.manager.plg Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks plugin: downloading: compose.manager-package-2026.03.27a.txz ... plugin: compose.manager-package-2026.03.27a.txz download failure: Invalid URL / Server error response Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks Plugin installed

manula install form link is failing as well:

https://raw.githubusercontent.com/mstrhakr/compose_plugin/main/compose.manager.plg

plugin: installing: compose.manager.plg Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks plugin: downloading: compose.manager.plg ... done Executing hook script: CA_preHook Clearing Community Applications plugin cache plugin: downloading: compose.manager-package-2026.03.27a.txz ... plugin: compose.manager-package-2026.03.27a.txz download failure: Invalid URL / Server error response Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks

going to <!ENTITY pluginURL "https://raw.githubusercontent.com/&github;/main/&name;.plg">

https://raw.githubusercontent.com/&github;/main/&name;.plg

hits 404, causing install issue atm. Please double-check the template path

Thank you

Edited March 29Mar 29 by bmartino1
Its Alive - beta works fine.

My fault. CI was breaking the package url when reassigning the branch in the plg url. Fixed and install is working again.

Edited March 28Mar 28 by mstrhakr
fixed wording

I added this plugin several hours ago, now the Action Center is listing this as "Blacklisted"...?

Seeing the same issue. Also lots acces to al my stacks? Tried reinstalling but that does not seem to do the trick:
Still seeing my files at /boot/config/plugins/compose.manager ...

39 minutes ago, Soulplayer said:

Seeing the same issue. Also lots acces to al my stacks? Tried reinstalling but that does not seem to do the trick:
Still seeing my files at /boot/config/plugins/compose.manager ...

He's just had a glitch with github and needs to correct the branch in the URL for the beta .plg.

After update to latest version I also lost acces to all my stacks. they don't show up in the Gui anymore (they still start after reboot), and path is correctly set.

3 hours ago, chodeus said:

He's just had a glitch with github and needs to correct the branch in the URL for the beta .plg.

Dev PLG now correctly points to the last beta instead of stable.

6 hours ago, cave said:

I added this plugin several hours ago, now the Action Center is listing this as "Blacklisted"...?

Seems like its from the PLG Url Mismatch I caused. It doesn't explicitly say it was blacklisted for that but I can't imagine another reason.

2 hours ago, The_Kief said:

After update to latest version I also lost acces to all my stacks. they don't show up in the Gui anymore (they still start after reboot), and path is correctly set.

Can confirm after update to latest version i lost access to all my stacks too. Did a rollback to Version Compose Manager v2026.03.27a

I tried Version Compose Manager v2026.03.27-dev.1632 (Beta) and now it is working for me.

Edited March 28Mar 28 by Sascha147

1 hour ago, The_Kief said:

After update to latest version I also lost acces to all my stacks. they don't show up in the Gui anymore (they still start after reboot), and path is correctly set.

What do you see. Does the section still show up but doesn't list any stacks?

33 minutes ago, Sascha147 said:

Can confirm after update to latest version i lost access to all my stacks too. Did a rollback to Version Compose Manager v2026.03.27a

I tried Version Compose Manager v2026.03.27-dev.1632 (Beta) and now it is working for me.

Stacks show on the beta but not on the main release? It sounds like the plugin install failed. Glad things are working again.

I had to remove the official version. Then install the beta and then everything is back okay for me.

18 minutes ago, mstrhakr said:

What do you see. Does the section still show up but doesn't list any stacks?

Stacks show on the beta but not on the main release? It sounds like the plugin install failed. Glad things are working again.

Yes only Version Compose Manager v2026.03.27-dev.1632 (Beta) is working for me. On the non Beta Version Compose Manager v2026.03.27 all my Stacks are gone and the compose Tap on the Dashboard is missing after install and reboot.

This is strange as they should essentially be the same package. I will investigate what differs between the packages. Sorry for the trouble guys.

3 hours ago, The_Kief said:

After update to latest version I also lost acces to all my stacks. they don't show up in the Gui anymore (they still start after reboot), and path is correctly set.

I have the same problem. My stacks a not visible any more. What should I do?

14 minutes ago, mstrhakr said:

This is strange as they should essentially be the same package. I will investigate what differs between the packages. Sorry for the trouble guys.

I have the same problem. My stack (only one) is not visible any more.

Reinstalled the deprecated plugin from dcflachs. Now my stack is back again.

Edited March 28Mar 28 by mafa1410

Its looking like this is all due to bad package naming. Slackware expects a certain format and I had a hyphen in a place that caused issues. Its most likely that the plugin failed to install due to this. This is being fixed in dev right now.

got update to 2026.03.28, fixes it. I see my stacks again. thx

5 minutes ago, The_Kief said:

got update to 2026.03.28, fixes it. I see my stacks again. thx

Awesome, sorry for all the trouble.

Beta users will need to uninstall -> install to get the fix as the -dev tag breaks the update sequencing and it thinks that IS newer that the new naming scheme.