You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if you set Fooocus to a shared output folder in the Stability Matrix options, the log viewer straight up stops working, and it shows the following error:
{"detail":"File not allowed: outputs/viewer.html."}
I've tried moving the required files to the shared output folder, but that did nothing.
As of right now, the only known way to make it work with Stability Matrix that I was able to find online is to disable shared outputs, but I personally really like having all my outputs from different SD UIs in a single place, so that would be a most welcome feature, if at all possible to implement.
The text was updated successfully, but these errors were encountered:
I did check that issue before posting this, but that unfortunately doesn't apply to the shared output folder. The issue described in #26 refers to using Fooocus inside Stability Matrix, but not making use of a shared output folder. The method the OP there came up with is the same I found elsewhere on the Internet and it does work if you're not using a shared output folder, but it does not work if you use one.
Bumping this. l'd really like to see this feature created. I love the log viewer, but it cannot be used with Stability Matrix when aggregating all images to a central folder. PLEASE ENHANCE THIS! Thank you
Currently, if you set Fooocus to a shared output folder in the Stability Matrix options, the log viewer straight up stops working, and it shows the following error:
{"detail":"File not allowed: outputs/viewer.html."}
I've tried moving the required files to the shared output folder, but that did nothing.
As of right now, the only known way to make it work with Stability Matrix that I was able to find online is to disable shared outputs, but I personally really like having all my outputs from different SD UIs in a single place, so that would be a most welcome feature, if at all possible to implement.
The text was updated successfully, but these errors were encountered: