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
This is a follow-up to #789 -- A generic title update setting leads to conflicts if you have multiple plugins enabled and can't decide which order they're ran in.
It might also be good to be able to block a plugin from updating archive titles even if the generic setting is toggled on, or move the generic setting to a per-plugin option again(but handled server-side).. god this is complicated
The text was updated successfully, but these errors were encountered:
I've noticed on the latest version of LRR 0.9.0, you can no longer have eze (or any metadata plugin that attempts to rename) turned ON with Filename Parsing turned ON and get the result of Parsed Name + Metadata tags only. Instead, it looks like File Name Parsing runs, does its job and then immediately gets its archive title replaced by eze archive title.
Annoyingly, the only way I've found around this is to turn on Filename Parsing only as the sole metadata plugin that runs on queue. Once the files are put in with only the Parsed Name, then go to Metadata plugin, TURN OFF 'allow plugins to replace archive titles'. Then go to Batch Operations and run eze. Now eze will place in all the tag info but leave the archive title alone.
This is a follow-up to #789 -- A generic title update setting leads to conflicts if you have multiple plugins enabled and can't decide which order they're ran in.
It might also be good to be able to block a plugin from updating archive titles even if the generic setting is toggled on, or move the generic setting to a per-plugin option again(but handled server-side).. god this is complicated
The text was updated successfully, but these errors were encountered: