Re: search results broken - giving .atom page links

On 17 November 2010 08:16, Ferenc Kovacs <info@tyrael.hu> wrote: > On Wed, Nov 17, 2010 at 4:51 AM, Philip Olson <philip@roshambo.org> wrote: > >> >> On Nov 16, 2010, at 12:31 PM, Ferenc Kovacs wrote: >> >> > On Tue, Nov 16, 2010 at 8:22 PM, Jeff S <jpsoren@gmail.com> wrote: >> > >> >> Search results seem broken - results are returning links to the atom >> feed >> >> of >> >> a page rather than the HTML content. For example- >> >> >> >> http://us3.php.net/results.php?q=imagemagick&p=manual&l=en >> >> The relevant results, #1, #2, #5 are all linked to the .atom feed of the >> >> page instead of the page itself. >> >> >> > >> > I experienced this also, when tried to search for Reflection. >> > I think we should create some functional tests for the search, because we >> > create new bugs or regressions with every change in the sorting >> algorithm. >> > :/ >> >> Search is a problem, but it's a difficult one. We do have: >> >>  - http://wiki.php.net/ideas/phpnetsearch >> >> But regardless, we may need to add a temporary solution. Yahoo offers many >> options but they feel complex, whereas a series of simple google custom >> searches work well. A simple test, both generic and language specific, >> appears to work fine. >> >> What do people think we should do? The main concerns are: >> >>  - Language specific. E.g., if my language is en, I shouldn't see ja >> results >>  - Offsite. Most of the work should be done by others (like Yahoo or >> Google) and not us >>  - 404 handler information integration (currently not done) >>  - Do we need the sqlite based keyword stuff? An intelligent search may >> remove this need >> >> Regards, >> Philip > > > I will check the current implementation, I think we should remove some > complexity, if we can, and I think that the yahoo search integration can be > tuned further, I don't know how did you integrate it, but in the past I've > played with the google and yahoo search apis, and yahoo was better, and if I > remember correctly, google discontinued their search API, so you can only > use them with an AJAX search field, or if we redirect the visitors to the > google (custom search). For what it's worth, Yahoo!'s web search service will be going offline at some point in December [1]. Their BOSS service is another option but there are talks of "a potential fee-based structure as well as ad-revenue models" [2] which don't appear very attractive. Google's AJAX or Custom search APIs might be an option, as would Bing (who provide Yahoo!'s search results now). The former seems to have silly limitations from the little I've used them. [1] http://developer.yahoo.com/search/web/V1/webSearch.html [2] http://developer.yahoo.com/blogs/ydn/posts/2010/08/api_updates_and_changes/ > > Tyrael >