charettepa

sorry for delay in my reply i have been away. thank you for the quick turnaround, i can test tonight.

hi. I'm new to FolderView Plus. Coming from folderview3 decided to switch to gain nested folder support i have noticed a few things that i would like help with 1- importing my foldervie3 settings gives me my settings and defaults that being said, i cannot find where the defaults are and how i change them not existing settings, or new ones, the default settings that show up when you create a new folder 2- i have fond certain settitngs are not working -advanced open on hover, still requires a click -status grey icon when off, leaves the icon in colour -sorting the folders apart, like you have in some screenshots ie. folder, folder, container, container, folder is not possible, on refresh they all resort to top of screen even after setittng sort to manual 3- the docker widget on the dashboard is very narrow with 2 columns to the left with lots of free space to the right i changed the display opting and they all provide minimal change staying tightly to the left 4- with the app installed, i was unable to reboot the system, it would envoke the reboot.php page, the page would go blank, and do nothing i tried 3 times and still could not reboot i finally uninstalled the app and rebooting worked properly any help would be appreciated i am on unraid 7.3.2

@EDACerton will surely want the APP logs as it is currently working with the newest version there must be a specific issue at hand he posted instructions on how to share app logs about 1-2 pages back

there are exceptions by default in the settings like not tracking SSD and certain other things

It's been working perfectly for me since the change on May 4th. Are you sure you didn't have any exceptions that conflict with your setup.

Just following up is this still an issue? is it now possible to boot without setting the default? also now that they have internal boot, does that work any differently in terms of booting without issues.

sorry I cant help, but I am interested in some of those I hope they get accepted and posted soon also, if you don't mind my asking how would i create my own templates?

to verify that the issue is no longer present? yes, as the issue only presented itsself after reboot i can confirm that it now works after reboots without requiring and reset or restart of the app/plugin

Thank you Installed update rebooted can confirm functional logging after reboot was i correct about the delay?

further update it does not need to be reset to default it simply stopped and then started @EDACerton with the logs i supplied this further lines up with the app/plugin simply starting too soon please add a delayed start up of X seconds even better if it simply verifies the availability of disks.ini and only starts after it is available and readable instead of giving up

@EDACerton have the diag files and/or additional details been helpful?

@EDACerton any thoughts?

@EDACerton I have rebooted in order to replicate the issue confirmed that nothing was logging downloaded the log as well as uploaded (52c7806dcb1790b7341ac6c2851b2a0d) the bottom of the watcher file indicates that the disks file cannot be found {"level":"fatal","error":"open /var/local/emhttp/disks.ini: no such file or directory","time":1776777253,"message":"Error loading disks file"} - i then reset the app to default, and started, (as its stopped when reset) performed a file activity, which was registered, then grabbed those logs as well downloaded the log as well as uploaded (9205ed5a146bb37dd853ae9464790df2) this one does not show that error - i then rebooted once more confirming the files are present however the log once again says the file "disks.ini" is missing downloaded the log as well as uploaded (4aa91abd6fcd6afbe0206219468ba3cf) - here is the log after reset and start downloaded the log as well as uploaded (6c3238097824ee8fc2f70b6411a15ada) - I suspect, the plugin is starting too quickly at system startup and the disks.ini file is either locked by the system or does not exist yet I now believe that delaying the startup of the plugin MAY fix this issue or perhaps a conditional statement to only start once disks.ini is present

ok, i can reboot the system, perform an action on HDD, check the plugin to verify no activity seen, then reset the plugin defaults, then start it as its off after reset, then perform action on HDD, then verify the plugin that will show activity, then grab the diagnostics where can i send the file to?

Any thoughts on why it does not work after reboot however, if you then reset defaults, which stops it, then start it it works again until next reboot?