View Single Post
Old June 17th, 2011, 09:03 PM   #1 (permalink)
KenDude
Member
Verified Customer
 
Join Date: Oct 2006
Posts: 426
Exclamation MAJOR BUG: Cost me $$$$$ with my members

Chuck,
You have a MAJOR bug in the auction system. I have just spent the last 30 minutes pouring over my database table cp_products looking at fields and values to try to figure out what has gone wrong and here is what I've found.

I had 14 auctions all end today. You can view these on my site at this link:

The Auction Block! - Classifieds

(Please note the first highlighted auction is not mine, it is someone elses)


Look down the list of items and you will see that most are marked SOLD, and if you click on the item it will tell you what it SOLD for. HOWEVER, it is allowing auction items to SELL FOR LESS THAN THE RESERVE PRICE!!!

Here is what's happening. Let's take the following item as a shining example:

AWE Tuning Chrome Exhaust Tips - Classifieds

When I listed that Item I put in a buy it now price of $500. I put in a RESERVE price of $275. I set the auction in motion.

People bid on the item. Here is the Bid History:

Login - Classifieds

As you can see a user named Chicane bid $220.
Another user named 3G3T7I BID $275,
BUT SINCE ALL THAT WAS NEEDED TO MOVE TO THE TOP OF THE BIDDING LIST WAS THE $10 INCREMENT, IT SHOWS HIS BID as $230.

Now if someone else had come along and bid say $250, they would have been immediately bumped by 3G3T7I because he had registered his high bid as $275, enough to meet the reserve.

The PROBLEM is that no one else bid and the auction ENDED and guess what!

THE ITEM IS MARKED SOLD FOR $230 and the user thinks they've WON the item for $230, when the RESERVE was $275!!!

HELLO I JUST LOST $45 ON THAT ITEM!!!

Let's go into the database for that item and look at the table fields and values.

FIELD NAME
PRICE - Value = $230.00
MAXBID - Value = $275.00
BUYIT - Value = Blank (Although originally this value was NO)
RESERVE - Value = $0.00 (This was NOT its original value)
RESLIMIT - Value = $0.00 (This was NOT is original value)

As you can see when the auction closes, the system is wiping the values stored in RESERVE and RESLIMIT and changing the value in BUYIT to be blank.

THIS SHOULD NOT HAPPEN!

What should happen is the following:

1) User bids on item, but their bid isn't as high as the reserve - System should enter their bid and increment the selling price, for example $220 to $230.

2) User bids on item and their bid is > or = the reserve price - System should IMMEDIATELY bump the price up to the reserve amount and list that as the current bid. If the reserve is $250 and they bid $270 while the item is at $200, the system should bump it up to $250 (The reserve price) NOT $210 the next increment price. If someone else comes along and bids $260 which is more than the reserve price then it needs to either do $260 if they are the high bidder, or it gets trumped by someone like in the example above who has bid $270 and it would go up to $270. The problem is the system doesn't seem to "know" if the reserve price has been met other than to say someone's high bid met the reserve price but it allows the actual selling price to be LOWER which completely defeats the purpose of a RESERVE!!!


Let's look at another auction that didn't sell. This item:
Capristo Control Box and Vacuum Tank - Classifieds

It is currently showing "High Bid - .25" but that's not really true, that member bid more, but since they were the first person bidding that's what it listed as. That's OK because their max bid didn't meet or exceed the reserve. Here are the database table values:

FIELD
PRICE - Value: .25
MAXBID - Value: 76.00
BUYIT - Value: NO (instead of being blank as the system does to the Sold)
RESERVE - Value: $500.00 (This was actually the BUY IT NOW PRICE when I listed the auction)
RESLIMIT - Value: $100.00 (This was the RESERVE when I listed the auction)

As you can see, since the max bid never met the reserve, the system did NOT wipe out the RESERVE and RESLIMIT field values.

It is VERY TROUBLING that the system wipes these 2 fields when an item is marked "Sold" in an auction.

Here's why. Let's go back to that AWE Exhaust Tip above. The selling price is $230, and the Max Bid the member made was $275. What if my RESERVE was actually $250??? All we know is that the MAXBID > Reserve because it got marked as Sold. But now that the system has wiped those 2 fields we don't know what the RESERVE actually was, other that it is "SOMEWHERE" between the value of $230 (price) and $275 (maxbid).

The big problem I have is that in nearly EVERY SINGLE AUCTION that closed today, the PRICE, what the Member is expecting to PAY ME because that's what is listed next to the big SOLD marking on the add is LESS THAN MY RESERVE.

I AM GOING TO HAVE TO EAT $235 by my calculations due to this BUG in the Classifieds. I'm extremely upset because I've reported before that the Reserve price wasn't working correctly, but I was "assured" that it was.

Well it isn't and I have the evidence to prove it in my database and in this topic I've just posted!!!

PLEASE FIX THIS ASAP, a check for $235 would be nice too, but I don't see that happening, how about a free license renewal on the 3 products I have (Classifieds, Review, Gallery) for the next year or two??
KenDude is offline   Reply With Quote