Posted on 2008-11-06 23:33:56-08 by scottcoburn
duplicate results, non-exact matches
Me again. The searches are working now. I have two problems though: 1) Some of the searches return duplicate results, sometimes 2, sometimes 10, 20, etc. Some searches behave as expected and return non-duplicate results. 2) The searches now return results with words that are a close spelling to the search word. How do I stop this? Is this a change at ebay? Thanks, Scott
Direct Responses: 9278 | Write a response
Posted on 2008-11-11 10:49:45-08 by mthurn in response to 9242
Re: duplicate results, non-exact matches
I fixed the "duplicate results" problem... Unfortunately the "fix" is that we can not go beyond the first page of results. This is in the 3.001 distro.
I also got rid of spell-check results in the 3.002 distro.
- - Martin
Direct Responses: 9288 | Write a response
Posted on 2008-11-13 00:00:42-08 by scottcoburn in response to 9278
Re: duplicate results, non-exact matches
So how many responses are there per page? Given the choice I would probably choose duplicate resul +ts over truncated results. I can manage duplicate results by doing some post processing. Thanks for the non-exact matches fix. This was really annoying. Cheers, Scott
Direct Responses: 9289 | Write a response
Posted on 2008-11-13 04:16:04-08 by mthurn in response to 9288
Re: duplicate results, non-exact matches
Unfortunately, it's not a choice between the two. After all these years, eBay has finally managed to thwart me -- I can not figure out how their new "next page" link works. And the "duplicate" results were actually an infinite loop of fetching the first page over and over again -- an infinite loop that exited after a random number of iterations 8-)

The module should be getting 200 results from the first page.

Direct Responses: 9295 | 9302 | Write a response
Posted on 2008-11-13 13:53:27-08 by meatsju in response to 9289
Re: duplicate results, non-exact matches
Instead of using the next button, could you parse the numbered pages links at the bottom and use those links? The Page #2 link seems to work differently than the Next link. I can copy the link paste it into a new browser window and it will actually work unlike the Next link.
Direct Responses: 9300 | Write a response
Posted on 2008-11-13 20:37:12-08 by mthurn in response to 9295
Re: duplicate results, non-exact matches
No, from the point of view of Perl code, all the links look and act the same.
Direct Responses: Write a response
Posted on 2008-11-14 00:02:45-08 by scottcoburn in response to 9289
Re: duplicate results, non-exact matches
For what it is worth: I use Konqueror (on Debian) as my browser. Some time ago the 'next' and the numbered 'page' button +s stopped working for me. If you mouse over the links they are all the same and they all point to + the current page. The only way for me to get to the next page is to type the page number into th +e little box and click the go button. If I switch to Iceweasel (3.0.3) the links work fine. So somehow it knows the difference between the two browsers. I tried playing with the identificati +on string that Konqueror sends (including setting it to the same string that Iceweasel sends) but +it made no difference. (I don't have a Windows box available at the moment to check IE, but I assume that it works...) Maybe this is a clue. Scott
Direct Responses: Write a response
Perl Weekly newsletter
A free weekly newsletter for people who are busy to read all the blogs. click here to check it out.