RE: [mv] MV4.04 Problem - Multiple Orders In Same Visit

["Cameron B. Prince" <cbp@internetexpertsllc.com>]

******    message to minivend-users from "Cameron B. Prince" <cbp@InternetExpertsLLC.com>     ******

Hi Randy,

This is probably not the most elegant solution, but what I did is add code
from the cancelled page to the receipt page. So when the receipt is
displayed to the customer, he is automatically logged out.

I have also added code to the receipt page that removes the customer's
session files at the same time he is logged out. This is because in order to
accept online checks with iTransact, I have to pass account information from
page to page as values and the values are being stored in the session files.

If the visitor needs to buy something else, he will have to login again.

By doing this, the order_number field problem is avoided and the customer's
account information is not left on the system.

Cameron


-----Original Message-----
From: owner-minivend-users@minivend.com
[mailto:owner-minivend-users@minivend.com]On Behalf Of Randy Moore
Sent: Sunday, June 18, 2000 11:47 PM
To: minivend-users@minivend.com
Cc: Cameron Prince
Subject: Re: [mv] MV4.04 Problem - Multiple Orders In Same Visit


******    message to minivend-users from Randy Moore <ramoore@axion-it.net>
******

 >****** message to minivend-users from Cameron
Prince ><PRINCECB@novachem.com> ******
 >
 > I have noticed a problem where the field in the userdb
called >order_numbers doesn't get updated properly when a visitor
completes >more than one order in the same visit or session.
 >
 >For instance if I come to the store and purchase an item the
order >number is added order_numbers in the userdb. But if I order
something >else without closing my browser, the previous order number
in >order_numbers is overwritten with the new order number.
 >
 >This doesn't seem to cause any major issues but prevents the order
status >from showing all my orders on the account page.
 >

I've just found the same problem.

I'm using MV 4.04 & MySql.

I checked the MySql logs to see what is going on with this value.  It seems
that the '[data
         table=userdb
         column=order_numbers
         key="[data session username]"
         value=" [value mv_order_number]"
         append="1"
         ]'

tag in 'log_transaction' is appending & writing out the new order number
for each order as it should.

But, some other part of the checkout process (that happens before the code
in 'log_transaction' is run) keeps re-writing the order_numbers field back
to the value that was read from the database when the user first logged in.

Has anyone found a solution for this?

Thanks.

Randy Moore
Axion Information Technologies, Inc.

email     ramoore@axion-it.net
phone   301-408-1200
fax        301-445-3947
-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to
Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list

-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list