![]() ![]() So basically, if it's a source install (in this case since you're having problems) - backup your config.ini, mylar.db and entire cache folder and then wipe the directory. py files if they've been moved, so it might not be able to run properly if there's more than multiple files that perform the same function in the same directory. If it was source, when you perform the update it will not delete the old. Was it a source installation or did you use git to install? Which branch/commit of Mylar are you using? The post-processing scripts (in the post-processing folder) have nothing to do with manual metatagging - they're only used when your download client runs them after a successful download. ![]() I've checked the permissions of the script folder, the Mylar source folder, and the folder w the CBR file in question. comicpath : C:\mylar-master\cache/mylar_1lh6lz Running the ComicTagger Add-on for Mylar ComicTagger 1.25.1 being used - using personal ComicVine API key supplied via mylar. Enabling ComicTagger script: with options: Failed to convert cbr to cbz - check permissions on folder : C:\mylar-master\cache/ and/or the location where Mylar is trying to tag the files from. Unable to write metadata successfully - check mylar.log file. Unfortunately now manual Meta-tagging doesn't seem to work. I just copied my Mylar post-processing scripts to C:\Program Files\SABnzbd\scripts to get Mylar to process downloads. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |