Topic awaiting preservation: any of you asylumites handy with oscommerce? (Page 1 of 1)

I hope so... I can't seem to get this figured out anywhere else:

I've installed oscommerce on a clients site and added a few contributions. For some unknown reason to me, under orders in the admin panel (admin>customers>orders), the 'Status' column is not reflecting what the order really is. Everything that should be "Shipped" is showing as "Cancelled". Even though when you click on the order itself it shows as "Shipped". I've tried everything I can think of to get this working properly. Just this last weekend I moved the entire site over to my new server, re-installed oscommerce and the contributions. I was hoping the problem would weed itself out (thinking that I messed up somewhere with a contrib installation) through the re-install, but it didn't. I'm thinking that it may have something to do with the PayPal IPN contrib. But alas, my skills in this area (php) are slim at best. Any help would be greatly appreciated. I promise someday when I know stuff I'll start contributing to the asylum. Thanks!

*kicking this over to the Server-Side forum*

well, it really sounds to me like the orders have a status ID (perhaps 0 for cancelled, 1 for shipped, 2 for pending, etc) and the program's not matching the correct status t othe ID, which is something messed in its code somewhere. I'm not sure, 'twould take some long searchnig through the code to find it, but it's doable...


Justice 4 Pat Richard

I've done www.tools4wood.se with oscommerce and it will indeed take time to spot an error like that...

I know that thgis works in my installation, but I've only got one contrib installed that allows you to update the db through excel.

Best bet is to drop the local install you did, install from scratch, verify that it works, then add each contribution one at a time and verifying between each contrib install. Once it stops working, you stop installing

From that point on you have isolated a decent size of code that most likely will be contain the problem, that is the last contribution.

After that you can either contact the author of that contribution or start to compare the original code with the code that the contribution inserts. I'd go with the first option...



The main problem with oscommerce and all other similar products is that once contributions starts to develop, quality control goes down the drain... No matter how good a developer of a contribution is ha/she will never have enough different installations with different other contributions plugged in to guarantee that the interaction between original code and all contributions won't develop unrelated bugs together

/Dan

{cell 260} {Blog}
-{ ?Computer games don?t affect kids; I mean if Pac-Man affected us as kids, we?d all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music.? (Kristian Wilson, Nintendo, Inc, 1989.) }-

i have also done one site with oscommerce - but honestly, i have no idea what causes your problem did you try to ask in their support forums? they are usually helpful. http://forums.oscommerce.com/

B | T | E | P | L

Yeah I've posted over there... I'm not getting too much action though (see here) You know, it dawned on me last night after I posted... the problem was still there immediatly after I installed a new version of oscommerce. That means the only thing on the new server that was from the old server was the database. I looked through it (the db) but couldn't see anything fishy. The fact that I really don't know what I'm looking at or for doesn't help much either. Where could I go from here? There's no way I can wipe out the database... it's huge! Thanks! Incase it helps the site is here.

edit: fixed link



(Edited by redroy on 12-08-2004 00:48)

Hmm...? I'm in the database now and the order_status table isn't in chronalogical order.

Would that make a difference? Or is that irrelevant as long as the ID's are unique? Thanks for your help.

the order in the table does not matter. It is, by design, unspecified, and code that was relying on it is simply broken.

Ok, next thing would be to open the file that actually prints the order status. Find out where it get's it from. Trace it back, all the way to the actual query. Find out what's wrong in between. Spend half a day working on this. You did check that your orders actually have an appropriate order_status in the database, right?

so long,

->Tyberius Prime

Holy mocus! You're right TP. I assume way too much. I need to stop doing that. The database is exactly what it's showing. That means the problem is were it updates (or writes) to the database... right?

most likely.

though if this was really evil, there might be a completly unexpected place where it updates the database ;-).

most likely.

though if this was really evil, there might be a completly unexpected place where it updates the database ;-).