Jump to content

tone

Member
  • Content Count

    38
  • Joined

  • Last visited

  • Days Won

    4

tone last won the day on November 28 2017

tone had the most liked content!

About tone

  • Rank
    Member

Recent Profile Visitors

985 profile views
  1. Hi @Southgirl. I'm struggling to find a reason for this issue. It really seems to be a network issue. A couple more things you can try: Try hitting this URL to see if it works. Try disabling Little Snitch temporarily.
  2. Hi @Southgirl, To rule out a network issue, you could try going to https://api.themoviedb.org/3/. If you don't receive the following, it means something on your network is blocking communication: {"status_code":7,"status_message":"Invalid API key: You must be granted a valid key.","success":false} If you are still having issues, you'll have to provide more details (version of Alfred, Mac OS, python, etc) and we can try to get to the bottom of it!
  3. Hi @romebot! It's been a while since I've done anything to this workflow, but the issue should now be fixed with the new release on github. Thanks!
  4. Big thanks to @vitor for his help in enhancing this workflow. He's added the OMDb API key as a workflow environment variable as well as implemented OneUpdater (auto-updates).
  5. I am on Alfred 3, but haven't updated this workflow in ages. A pull request would be awesome. I'm not a GitHub expert, so bear with me.
  6. Nice! Back in business. I've updated Packal and GitHub with a new version that has a free OMDb API key. Because it only allows 1,000 hits per day, you may want to use your own key... To do so, edit line 103 in the "media.py" file in the workflow. If I continue to update this workflow (or we see the limit being hit), I'll make changing the API key more user-friendly. But for now, we'll see how this free API key goes.
  7. Ahh... It's too bad the OMDb API had to end its public API. I will edit the main post to describe why this workflow no longer functions. Forum admins, please feel free to do what you'd like with this thread.
  8. Looks like the OMDb API is needing to change some things around and maybe even lose some Rotten Tomatoes info. The current spot in the API results that the RT score is retrieved now returns "N/A". The workflow code is setup to handle this scenario which is why the "Search" item in the workflow is still shown. I've done some work to retrieve the RT score from the new place in the API. It's updated in Packal and Github. Let me know if it works!
  9. Looks like the issues with the OMDb API are resolved. The workflow should work smoothly once again.
  10. Hi Guys, Thanks for reporting the issue and glad you have been finding this workflow useful. It looks like something is going on at OMDb. This is the API that the workflow uses to get IMDb, metacritic, rotten tomatoes ratings. I'll keep my eye on OMDb. Hopefully it'll come back online and the workflow will start working again. If it becomes a permanent issue, I can look into alternatives.
  11. The workflow I developed seems to work still (tbh I don't use it all that much).
  12. Bingo. TMDb API gives fairly good search results. I, too, like how your workflow shows results right on the search screen. Hopefully you can implement the TMDb searching without too much of a hit on speed.
  13. Cool workflow. Thanks for sharing! Mine wasn't in there either - MacBookAir6,2.
  14. I found a few minutes and was able to implement your suggestion, mnisbet. The update is available through Packal. Thanks for the suggestion!
  15. Looks like this should be doable as the data is included in the OMDb API. Unsure when I'll be able to get around to implementing it though. If you don't want to wait for me, you could always try tinkering with the code .
×
×
  • Create New...