Yahoo Search Broken (again?)
Asides, Yahoo
[inurl:yahoo.com search], no results found. This search worked fine days ago. Contrast. This is why WordPress.org search is broken. Any suggestions for better web search API providers? I loooove the way Yahoo provides results as serialized PHP in addition to XML (every API provider should do that!) but the underlying search product seems to be built on a shaky foundation.
Pingback: Make You Go Hmm: » Wordpress Matt looking to dump Yahoo search because of “shaky foundation”
It works well from here. Maybe there have been a little hiccup on their network? It happens sometimes
The problem must be widespread, because I’ve tried proxying the requests through 7 machines in various datacenters.
Works fine for me here as well.
Wait, so when you guys click the first link in the post, you see results? It doesn’t give you this?
It doesn’t work for me. I am getting:
We did not find results for “inurl:yahoo.com search”.
I didn’t get any search results.
that link replies:
Pingback: WordPress.org 站上的 Search åˆçˆ›äº†… at Gea-Suan Lin’s BLOG
Matt, I can confirm that yahoo is returning “We did not find any results” on my computer.
This is from here in Australia, as well as proxied through a few datacentres in the US. Same result each time, regardless of the location.
I got “We did not find results for inurl:yahoo.com search.”, too.
But I tried on another machine, it works fine.
both the Yahoo and Google links bring up search results for me.
I get results for the first search link on yahoo: “1 – 10 of about 130,000,000 for inurl:yahoo.com search – 0.03 sec. “, with yahoo.com coming up as the first result.
Yep, I get results for the first link in the post. Maybe a bad yahoo datacenter that you kept getting routed to?
I don’t think they did, because it most certainly isn’t working here.
I’m not a Yahooligan, but if you’re sure of the Syntax in that link then something is definitely up.
There *are* many other search providers, some of them that even match Google’s black-box rack-mount servers that you can buy for an organization and some of these are open source, in keeping with the WordPress Spirit
If you’re interested in switching or whatnot, drop me an email, and we’ll see what we can find.
What sucks is you’re going to have to redo the entire WordPress.org site to match the new API for whatever product you choose, but I’m sure the brains at WordPress can figure out how to do it in as little time/effort/cost as possible.
I think I’ve said it before, but I’ll reiterate: Since Yahoo Search was implemented, with the combined results of both the codex, forums, blog and what not, I haven’t been able to find anything… If you keep with Yahoo, or a similar solution, I’d love to see an easy way of searching only a particular section of the WordPress network.
PS: Yes, I know you can do searches for a particular URL, but that’s a hack at best, and something 99% of the users looking for help won’t know how to do, or like me, is too lazy to figure out the syntax for.
Doesn’t work for me, I get “We did not find results for “inurl:yahoo.com search”.”
Nothing for “inurl:yahoo.com news” either. Looks more like an intentional block from their side, rather than a bug
As I recall it, I’d always get “We couldn’t find anything! Please try a different search.” while using wordpress.org search. In fact I cannot remember a single time it has returned any results. These days I’m manually typing “site:wordpress.org” into Google. Works every time.
Michael, you may not have checked out the search lately, but it gives you options about which section to search. It default to just the Codex, but allows support forums, trac, etc.
I got “We did not find results for “inurl:yahoo.com search”.”
aah, I was wondering what the heck was wrong when I spent hours trying to search my way through the wordpress codex. I hope it gets better soon though. Doesn’t work down here either. Also, before this, everytime I tried to search from the search page, it used to break.
Hey Matt. Are you sure you’re spelling WordPress right?
heh heh heh
Your example is broken, (domain in
inurl:) but this works fine for me:Why not just use the
site:operator to designate the domain, and then useinurl:to designate a subdirectory?Mark, I’ll try that to bring the search back online quickly, thanks for the suggestion. What’s weird is that it just stopped working overnight.
Actually the inurl: operator is not designed for that purpose, it is suppose to do a search in all the sites that contains the word that follows the : within the url.
If what you want to do, is a search that is restricted to an specific domain you have to use the site: operator instead. Then you can combine it with inurl: to force the search to be a little more specific, so you have.
site:matt.wordpress.com *for a search that is only restricted to the (sub)domain.site:matt.wordpress.com inurl:2006 *for a search that is also restricted to the (sub)domain but requires the word/number 2006 to be within the url.We were using
inurl:because Yahoo doesn’t allow you to put a full path insite:like Google does.Using site + inurl I’ve got the search working now again, hopefully for good. It’s bizarre that the linked search works for some folks but not for others.
Your example returns zero results but search at wordpress.org works fine for me.
How about ask.com? Been seeing a bunch of their commercials lately and thought I’d try it out.
Hey, have you guys looked at the new Google AJAX Search API? Its very cool! JSON under the covers but comes complete with a JavaScript API. Its popping up in lots of blogs and sites.
http://googleajaxsearchapi.blogspot.com/
http://code.google.com/apis/ajaxsearch/
AJAX Search API results are JSON.
-E