Hi all
Here's the scenario:
I have a client whose store uses OSCMax RC2 v3. The store has been around for a few years (previously it was v1.7) and the database is quite large.
Recently two orders have gone 'missing' after the client has updated the status using the edit_orders.php file in Admin.
Checking the database shows that the problem is being caused by a null value being written to the status history table by that file. The Admin can no longer 'see' the order because of the zero value.
A bodgeit fix is to create a new entry in the order status table of '0' 'Retrieved'. This allows the order to be 'seen' again in the orders.php file and the status can be updated from there (although edit_orders.php still will not update it).
This has only happenned in two orders out of hundreds and I can see no correlation between them that could account for this.
I have been through edit_orders.php with a fine toothcomb and I cannot see any reason for the problem (I cannot replicate it at all on the testing server) nor can I 'break' a test order on the live server. The code for writing to the status history table is the same as that in orders.php and I cannot find any reason for a null value being passed by the script.
(It also will not update any comments added whether or not the status is changed)
Google suggests a similar problem with ZenCart but there is no suggested solution.
Whilst I have a quick and dirty fix in place for my client I was wondering if anybody had come across this before and has a proper fix for it (my client is very thorough about keeping her order records up to date so is aware if any go 'missing' if she were not then this would cause a problem as it appears to be totally random - I don't think it's a server problem as it always occurs for these two orders - e.g. if I reset the value to 'Pending' using orders.php and then edit again using edit_orders.php the null value is returned)
Has anybody come across this before?
Regards
Graeme





LinkBack URL
About LinkBacks











Bookmarks