ezek1el3000

@chodeus i was curious what your version would look like. So i copy all necessary files of my old install to a save place and removed the old folderfiew2 plugin. I installed your version via the link provided in the description of your fork. Installation finished without any problems. By opening the setup page of the folderview plugin by clicking the plugin icon just opens a blank page. So i double checkd if the installation link was correct. Yes, it was. The same error occurs when i install the plugin the manually way. Any advice?

I got the exact same problem on the Dashboard page. Plugin Version 2025.08.07.5, Unraid 7.1.4. Any Idea whats causing this and how to fix it?

You should consider making a sticky post with information about the state of the plugin and manual install instructions to avoid answering the same questions over and over again.

reverted, all good again

DM sent

Did a fresh install. No styles, no scripts. Same result. All mixed up. Help.

Docker page looks good though

Any Idea why after the latest plugin update all my folders are mixed up? Removing and readding containers to folders didn't help. For example i add a bunch of database related docker to the folder Databases. After doing so, different docker show up insinde the folder. Any Idea why? Everything worked before the update.

I can confirm works like a charm. Thanks again @VladoPortos

If i reinstall the plugin from the link provided a few posts back, does it include the latest PR?

Odd, never noticed it before. Kind of glad thats not a FolderView issue. Hopefully LT fixes this in the feature.

I don't get that glitch without FolderView. sooo.... Edit: ok, just saw the @Mainfrezzer edit. Thanks for sharing.

The link let me install the plugin perfectly. I can restore all my settings just fine. But i get this strange litte graphic glitch. Anyone any idea whats causing this?

I am still getting the following error on boot: mv: cannot stat '/usr/local/bin/mover': No such file or directory Server boots up fine and only hangs for a couple of seconds on this error. Latest CA Version 2023.12.19 The error has only showed up on (re)boot in the console ls -l /usr/local/bin/mover Output: -rwxr-xr-x 1 root root 161 Mar 26 15:01 /usr/local/bin/mover* cat /etc/cron.d/root Output: # Generated mover schedule: 0 8 * * * /usr/local/sbin/mover &> /dev/null

Unfortuntly no. I still get the error. Server boots up fine and only hangs for a couple of seconds on this error. Latest CA Version 2023.12.19

Not really. Just ignore the error and occasionally delete the syslog. A BIOS update might help though.

How do i change the favicon?

That would be amazing if you could add that option.

Okay, notifications only happen if the backup got errors or warnings, not when its done correctly. I keep that in mind.

Readability. That is how i check from time to time if the backups are done. Sure, I could check the status/log page, but checking the latest folder is much faster, for me at least. Does the plugin sent out notifications?

Plugin works like a charm. But would it be possible to name the folders created for each backup differently? I don't like the name scheme. Now every folder has a name like "ab_20230713_043001" can we get an option that let us select a different name pattern? Or at least add "-" like yyyy-mm-dd-hh-mm-ss

I updated from 6.11.5 to 6.12 and unfortunately the error still occurs. Syslog keeps showing the same error

Thank you !

You're right. There it is. Somehow i missed it. Thank you for pointing me in the right direction!