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
I recently discovered https://github.com/LizardByte/Themerr-plex which I've been really enjoying. One thing I've noticed however is unfortunately the themes that Themerr adds to the movies is also marked as a bloat file by ImageMaid. This leads to /Uploads/themes/ being removed on a 'remove' ImageMaid run; unfortunately 'breaking' the themes.
Hoping it would be possible to have an additional options or flag that would prevent ImageMaid from treating those uploaded themes as bloat files but still removing the /Uploads/posters/ that are indeed bloat.
Attaching a link to a snippit of the logs while running on 'report' that shows those themes being marked as bloat files. https://pastebin.com/egK802mg
The text was updated successfully, but these errors were encountered:
I am the maintainer of Themerr, and to add some, hopefully, helpful information.
We "lock" the themes, just as if the user were to lock a any field of metadata or image. This script should probably ignore anything that is locked as the user intentionally set it that way.
Describe the Feature Request
Greetings!
I recently discovered https://github.com/LizardByte/Themerr-plex which I've been really enjoying. One thing I've noticed however is unfortunately the themes that Themerr adds to the movies is also marked as a bloat file by ImageMaid. This leads to /Uploads/themes/ being removed on a 'remove' ImageMaid run; unfortunately 'breaking' the themes.
Hoping it would be possible to have an additional options or flag that would prevent ImageMaid from treating those uploaded themes as bloat files but still removing the /Uploads/posters/ that are indeed bloat.
Attaching a link to a snippit of the logs while running on 'report' that shows those themes being marked as bloat files.
https://pastebin.com/egK802mg
The text was updated successfully, but these errors were encountered: