#713 ✓resolved

Seller (unknown) for new items

Reported by Joop | February 22nd, 2009 @ 08:27 AM | in 2.1 Release

With the new 2.0-800 it seems when adding new articles the sellers are sometimes listed as "(unknown)". For some (older?) articles (they were added before with an older version) the seller is still listed correctly. When I exit and restart JBidwatcher they are visible again. Not a showstopper, but confusing.


Comments and changes to this ticket

  • Holger Lembke

    Holger Lembke February 26th, 2009 @ 12:43 AM

    Same problem for me, here is a sample.

    As you see: it looks a little bit random.

  • Therese Telepski

    Therese Telepski February 26th, 2009 @ 01:18 AM

    Please download the actual 2.01-825 version containing some bugfixes.



  • Holger Lembke

    Holger Lembke February 26th, 2009 @ 03:36 AM

    Dear Therese,

    of course I always use the latest version.

    Respectfully yours,


  • sbarner

    sbarner February 26th, 2009 @ 04:40 AM

    I was having a similar problem. On update, auction seller names were changed to Unknown, even though they had been correctly identified in JBidWatcher before the update. I also had a successfully completed auction listed as unsuccessful, even though the Show Information pop-up showed the auction as having been won. Finally, a bunch of auctions, including all new auctions, had a snipe of $1.00 listed, whether or not I had entered a snipe. In a couple of cases, snipes I had loaded were replaced (at least in the snipe column) with snipes of $1.00.

    I went back to version 2.0 and all the problems cleared up, though I had to delete all current auctions from the cache and then have JBidWatcher re-add them.

  • Holger Lembke

    Holger Lembke February 26th, 2009 @ 05:34 AM

    Ok, another addon:

    of course it is a "fresh" search made bay an automated URL-Search. Today morning, never run before.

    Everything sorted out now?

    Thanks. :-)

  • Holger Lembke

    Holger Lembke February 26th, 2009 @ 09:53 AM

    And now something repaired it and all names appear. It is so magic.

  • Therese Telepski

    Therese Telepski February 26th, 2009 @ 01:55 PM

    As at least with Windows OS, too (and I think it's comparable on Macs and UXes) it's always a good idea to try a restart (program or whole computer) when something goes wrong before beginning to dig deeper. Experience is teaching us this clears something about 95% of all the trouble. Magic indeed ...



  • Morgan Schweers

    Morgan Schweers February 26th, 2009 @ 02:01 PM

    • Tag set to parsing, seller
    • State changed from “new” to “open”


    Yeah; the problem here is that eBay is randomly (some percentage of the users coming to the site) experimenting with different view-item pages, and so sometimes it will get one that JBidwatcher doesn't parse properly. :( When that happens, eBay has marked the login session to receive that page, so all the pages loaded after that will get the altered View Item page.

    I'm concerned that this might be the cause of the problems with multisnipes as well, but I'm not sure.

    -- Morgan Schweers, CyberFOX!

  • Morgan Schweers

    Morgan Schweers February 26th, 2009 @ 02:26 PM

    (from [827]) If we couldn't parse the seller's information, but we have seller information from a prior parse, don't overwrite the old-but-good seller information with new-and-bad data.


  • Morgan Schweers

    Morgan Schweers May 16th, 2009 @ 03:58 AM

    • Tag changed from parsing, seller to @moved, parsing, seller
    • Milestone changed from 2.0 Full Release to 2.1 Release

    [milestone:ID#38598 tagged:"@moved" bulk edit command]

  • David

    David May 20th, 2009 @ 10:22 AM

    How about refreshing the eBay session when you can't parse the seller information? Too kludgy?

  • Morgan Schweers

    Morgan Schweers May 24th, 2009 @ 02:00 AM

    • State changed from “open” to “resolved”
    • Tag changed from @moved, parsing, seller to @moved, committed, parsing, seller

    (from [919]) Seller info fix; eBay changed the wording on the beta seller information block to something shorter, so JBidwatcher wasn't picking it up.

    [#713 tagged:committed state:resolved]

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Shared Ticket Bins

People watching this ticket


Referenced by