Versions:
Linux Mint 21.3
kernel 5.15.0-122-generic (x86_64)
mylar3-master 0.8.0
comictagger 1.6.0a22 (installed in venv with pipx)
In trying to keep the current list of publishers to filter out when doing CV searches, I find myself updating 3 different files:
mylar3's config.ini file (ignored_publishers)
comictagger's settings file (id_publisher_filter) which is what mylar3's config.ini points to
comictagger GUI settings (which saves to a json file in a different directory from the other settings file)
Is there any way to simplify this?
Can I point mylar3 to the directory with the json file? Will it even recognize that?
Maybe replace the comictagger.py file in the mylar3 directory with a link that points to the alpha version comictagger python file? Would that accomplish anything?
Any and all advice welcome. And as always, thank you this amazing piece of software!
Mylar3 and updated comictagger version
-
musictrivianut
- Posts: 20
- Joined: Fri Jun 10, 2016 10:07 am
-
evilhero
- Site Admin
- Posts: 2891
- Joined: Sat Apr 20, 2013 3:43 pm
- Contact:
Re: Mylar3 and updated comictagger version
The version of comictagger that is included with Mylar is an older customized forked version of CT. Newer versions won't work with it, and you won't be able to just change out the py file and have it work.
The only file in that list that mylar pays attention to is the ignored_publishers in the config.ini. This has zero usage in CT, as it's not used the way mylar uses CT. This config.ini setting only affects what mylar will display on search results (via the search page), or when you're viewing the weekly pull by filtering out publishers not wanted from displaying.
The 2 CT files you mentioned aren't being used by this particular version of CT that's incorporated within mylar. This is because whenever mylar tags something using the bulit-in CT, it doesn't have to search for anything - it just calls it against the exact issueid that's being metatagged (since it already knows that when you initiate a search + download, or metatagging).
Now at some point, and as long as lordwelch is ok with it, I'll look into possibly updating the version of CT in mylar to a newer version of CT that's maintained by them. There's absolutely no guarantee that I'll be able to do it, nor a time frame of when this would occur - or if they don't want it being used the way it currently is....
The only file in that list that mylar pays attention to is the ignored_publishers in the config.ini. This has zero usage in CT, as it's not used the way mylar uses CT. This config.ini setting only affects what mylar will display on search results (via the search page), or when you're viewing the weekly pull by filtering out publishers not wanted from displaying.
The 2 CT files you mentioned aren't being used by this particular version of CT that's incorporated within mylar. This is because whenever mylar tags something using the bulit-in CT, it doesn't have to search for anything - it just calls it against the exact issueid that's being metatagged (since it already knows that when you initiate a search + download, or metatagging).
Now at some point, and as long as lordwelch is ok with it, I'll look into possibly updating the version of CT in mylar to a newer version of CT that's maintained by them. There's absolutely no guarantee that I'll be able to do it, nor a time frame of when this would occur - or if they don't want it being used the way it currently is....