-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
Make "Save archive title" plugin setting handled by LRR #789
Comments
This makes sense to me, although I'm not sure where to show the then global setting for saving/modifying archive titles -- Having it in plugin configuration at the top makes sense, but all the other global toggles are in the main settings page.. |
I'd vote for putting at the top of the plugin configuration, mostly because there's no good existing section in the settings page. Shouldn't be TOO hard to move it later though, if LRR ends up getting a bunch of related settings in the future. |
Thanks for your nice work, but this change break my archive title😭 This change makes it impossible for me to only select certain plugins to save the title. I can't control it. I want to know if the titles returned by all plugins are in order and which plugin's title is ultimately written into the database. Because not all plugins return satisfactory title, such as What about this case:
titles returned by all plugins:
final title:
Now I have rolled back the E-Hentai plugin to the old version and turn off |
Thanks for the details -- Currently Filename Parsing is hardcoded to always run first as it's often helpful to clean up titles before doing text searches with other plugins. I've been wanting to implement configurable plugin execution order for a while but haven't gotten to it. I think it'd help you here? Since you could just run filename parsing after EH. |
Please describe your suggestion, and the problem it'd solve.
Most metadata plugins have a "Save archive title" setting. This could be handled by LRR instead, avoiding quite a bit of repeated functionality inside the plugins.
This setting does not make sense for the "Tag Copier" and "Add Timestamp tag" plugins though. Either
plugin_info
could return a flag whether or not it supports archive handling, or it could just be ignored.The text was updated successfully, but these errors were encountered: