{{ message }}
Dry Run not so dry #929
Closed
scooterbaga
started this conversation in
General
Replies: 1 comment
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
Just wanted to throw out a thing that happened to me. Not really an idea, or even a suggestion. Thought it might be useful input.
Having to enable the renaming schedule to try a dry run is a little risky. Hitting Disable after you nope out of renaming the 5-6k files/folders found in the Dry Run can go a little sideways if you're not careful. It looks like it's been disabled. And if you don't notice the Save button light up on the other side of the window, you might just move on to other things and not save. If you're new to the interface, you can miss it. Feels like a dry run should be more siloed from the actual function.
Not sure if I actively dismissed a "leave page" prompt or the UI's Stay/Discard, or just managed to do something to miss it completely. FWIW- I've seen somewhere in the regex/custom profiles area that triggers a Stay/Discard prompt and, from what I could tell, it's a false positive of some sort. But chances are for renaming I was just tired, careless, and having too much fun tweaking all the things.
At least I had already set up the renaming format to what would have wanted beforehand. ¯\(ツ)/¯
Anyway, it would be kind of nice to be able to run the renaming on subsets of the media. Guess I did have a suggestion. Just remembered that's part of the reason I noped out of a full rename.
Also, the database conflicts don't seem to tell you what the conflict actually is? I probably just missed it.
Ain't even mad. Love the program. It's dialed up to 11 some Arr methods I had stumbled across and cobbled together on my own over the years. Thanks for your time.
All reactions