-
-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KNOWN ISSUE: Plugins no longer working after upgrading to V24 #186
Comments
Yes, known issue, development has the breaking schema changes (very extensively changes). Many scripts will break, so they'll need to be changed. Hopefully the plugin improvement rolled out at the same time will help ease the pain. The upcoming schema changes have been public for a while but nobody was being proactive. RoU and SNEK will get full revamps soon. |
I guess the same happened to the Stash-Plugin for Plex right? It still matches, but only gets Title and puts the date into the title. |
@scruffynerf I started working through updates on RoU to work against my local development instance of Stash. Anything I can do to help with this plugin in particular? I'm happy to publish a pull request if it's helpful. |
Now that v24 has hit the stable branch, is there a fix in the works for this or is the plugin unmaintained? |
Working on v3.0, there are hacky shortcut fixes that basically remove items currently broken, but I'm not recommending those... I'm working on a rewrite that remove the use of sqlite direct access, and makes it easier to use, adds Plugin settings the new way, etc. If you must have a quick fix, I can provide a link to someone's mod for it, but... At your own risk. |
Yes please, the link to a temporary fix would be great. |
v2.5 is working without issue for me. |
yes, RoU 2.5 is my stopgap fix until I get v3 out the door. |
You can use this for meanwhile https://github.com/rustyinfinity/StashNfoExporter |
v0.23.1-23-g2b871810
Updated to latest this development channel this morning. Seems like both plugins have stopped working.
Reverting back to latest channel and v0.23.1 solves the issue.
The text was updated successfully, but these errors were encountered: