rice.shawn Posted October 15, 2013 Share Posted October 15, 2013 I think the URL for the Google Images search is broken. All the other search ones that I've tried work. I type "images test" Alfred send me to "https://images.google.com/images?q=test" I get a 404: "The requested URL /images was not found on this server." So, the URL probably just needs to be switched out. OS X 10.8.5; Alfred v2.0.9(214) --Shawn Link to comment Share on other sites More sharing options...
RodgerWW Posted October 15, 2013 Share Posted October 15, 2013 Works fine for me ... OS X 10.8.5 / Alfred 2.0.9(214) ... perhaps Google's servers were down? Link to comment Share on other sites More sharing options...
rice.shawn Posted October 15, 2013 Author Share Posted October 15, 2013 Still happening for me... So, then it's a real puzzle if it's working for you when it's not working for me. Damn. I thought that it would be a quick fix. My setup probably has some other quirky-something-or-another going on then. I'll look more into it on my end. Maybe it's a Chrome thing (are you using Chrome?), or maybe it's a Chrome app that I installed. That might make sense. Link to comment Share on other sites More sharing options...
rice.shawn Posted October 15, 2013 Author Share Posted October 15, 2013 Yeah. It's a Chrome thing. (I should have checked this before posting the last one). When I switch my default browser back to Safari, then it works just fine. So, I guess this isn't a bug. Andrew, Vero, just ignore this thread. Link to comment Share on other sites More sharing options...
raguay.customct Posted October 15, 2013 Share Posted October 15, 2013 It's working with Chrome on my system. Maybe re-install Chrome on your system. Link to comment Share on other sites More sharing options...
politicus Posted October 15, 2013 Share Posted October 15, 2013 +1 working like a charm on my Mac. Configuration :OSX Lion 10.8.3 Google Chrome 30.0.0.1 Link to comment Share on other sites More sharing options...
rice.shawn Posted October 15, 2013 Author Share Posted October 15, 2013 It's probably not Chrome itself but an app that I installed inside of Chrome. When I get a chance, I'll look through those and see which one might be screwing it up. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now