REVERT TO OLD VERSIONS? HOW?
Johnnyprim3 opened this issue · 2 comments
Hi, I'm not as skilled as many here & as such, I'm having issues with reverting to earlier versions. Can anyone please EXPLAIN how this is done? How do you revert to earlier versions?
Thanks & Cheers.
Try this first. Go to the SD-CN-Animation folder inside the Extensions folder. Click on the address bar, and type "cmd" and hit enter. That will bring up a command window.
Now choose the older commit you want to try (click on the "commits" txt that you see on the repo just below the green "Code" button dropdown on the top right), and copy the commit hash you want to try, e.g eddf1a4 is the hash for commit 82 from May 13. Now just write "git checkout eddf1a4", or whatever hash for the older commit you are testing into the cmd window, and hit enter. The cmd window should say something about it being a detatched head, which means you've rolled back successfully. That's the easy part. Start up Auto1111 and hopefully it should show the SD-CN tab.
However, from what I've seen other users reporting, I'm not certain that you'll have success if you're using the newest A1111 (1.4.0 or above) and I haven't tried anything past 1.4.0 myself yet. I've been experimenting with a bunch of older versions of A1111 and SD.Next (Vlad's fork) to find versions that play nice with the older SD-CN-Anim commits.
It's a chore, I had no experience with it until I really wanted to get back some SD-CN-Anim traits that were working well for me on a project, so prepare for headache's until you've done it a few times, and you'll also need space for setting up several fresh installs of older A1111 or SD.Next to test out different plugin commits in older environments. It's not a very efficient way of doing things, but I found that when I was rolling back and forward using the git checkout method volotat advised me to use, versions that were throwing no errors when I first rolled back to them, would then throw breaking errors after I tried to go back and forth between commits. You may have more more luck with it than me (and please let me know if you do!) but I managed to test several different version that way.
I think I was using a dev branch commit of Auto1111 somewhere between 1.2.0 and 1.3.0, sorry I can't be more specific, and to be honest it's all still pretty esoteric to me, I have no solid clue why some versions of the plugin work with some version of A1111 and others throw errors and won't display the plugin tab. Apparently the version of Gradio, other plugins, and quite possibly other things going on under the hood in A1111 may have an impact on whether the older commits work for you (IIRC volotat addressed this on another thread and he though it was due to Gradio version bumps).
Hope this gives you a few pointers in the right direction, and good luck. If anyone else has a better strategy please chime in!
@peteTater Thanks Bro, I'll give this a try!