-
Notifications
You must be signed in to change notification settings - Fork 172
Torrent search broken? #1003
Comments
Your search provider order is empty, so it's not searching against anything due to that. Shutdown mylar, edit your config.ini file, and then wipe out the entire provider_order line. Save the config.ini, start up mylar and you should be snatching torrents again. Just remember that if you make any configuration change, even if it's as small as enabling/disabling a provider, you need to restart mylar after saving the configuration. Mylar recreates the search provider order on startup only so if you don't restart after a provider change it messes up the order. |
I had already restarted Mylar several times. Stopping Mylar and clearing the provider_order line also didn't fix it. I still get this: |
Are you removing the entire line or just blanking out the values? (deleting the entire line is required). Can you paste in the config.ini showing your provider_order and torrent sections? |
I'm removing the entire line. I tried it again with the same results. The line gets added back like it was before (blank) after I restart. Here you go:
|
Oh that stupid lone comma! Change the provider_order line so it's just : provider_order = "" Then start up mylar and it should work. I think I patched my local repo with the fix but haven't pushed it just yet. |
Unfortunately that still doesn't fix it. It automatically gets changed back with the comma after I restart. |
Ok, then we try a manual edit. Edit the config.ini so it looks like: Save and start up mylar and see if that fixes things. |
That did the trick. Thanks! |
I noticed after the latest update that Mylar stopped finding any results for any series I added, including newer issues where I would assume it would find something. I only have torrent search (with KAT) enabled. It used to not have an issue finding results. In the log it looks like perhaps it's not searching on the full title name? Here are a coupe examples for Spider-Gwen and Ant-Man:
The text was updated successfully, but these errors were encountered: