Page 1 of 1

Customer Info Disappears

Posted: Fri Jul 04, 2014 5:56 am
by sports310
I am looking for a extension that when a customer enters there info in the checkout and then the leave the cart and shop some more all of there info that they entered disappears. Is there a way that all there info will stay there besides there credit card info ?

Thanks
Mike

Re: Customer Info Disappears

Posted: Fri Jul 04, 2014 6:17 am
by tacobandito
You could save it to the PHP session, and recall from that. That would be a good temporary save, but it wouldn't save it indefinitely. The alternative would be to save it to the DB along with the IP address to recall from.

I couldn't find an extension to suit those needs, but I'd be happy to build it! PM me for a quote, or check the commercial support forum!

Re: Customer Info Disappears

Posted: Sun Jul 06, 2014 9:00 am
by straightlight
Credit card storage should not be stored in session, globals nor in the DB. It should rather be put in sanitized post then to unset the variable whenever the browser doesn't require it anymore. A good example would be with the API when SHA256 must be used. Not only it protects the merchant account from websites but also enforces security during transactions.

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 8:42 am
by JAY6390
Storing that data in the DB based on IP is a really bad idea too. IP's get re-assigned on a lot of home users' connections, and you could potentially (though not probable) fill in the data with someone else's. There's also connections that have hundreds/thousands of users on the same IP (schools, universities, open wifi hotspots) which would fill in the data based purely on that one IP

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 8:21 pm
by straightlight
Storing that data in the DB based on IP is a really bad idea too.
While this statement is true, it would be questioned on why the order table from the core has an IP address field to store along the orders from checkout or manual order.

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 8:39 pm
by JAY6390
The IP address in the orders table is to log the IP that makes the order, not to remember customer data for the checkout

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 9:01 pm
by straightlight
Database storage is normally use to remember data, basically. If IP addresses are stored in database for the order only so not to remember ... it is a bit puzzling on seeing why this is being stored in the first place if we compare this methodology with what you mentioned on the above:
There's also connections that have hundreds/thousands of users on the same IP (schools, universities, open wifi hotspots) which would fill in the data based purely on that one IP
Which relative IP is tracked in the end? ! ;)

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 9:55 pm
by tacobandito
sports310 wrote:...Is there a way that all there info will stay there besides there credit card info ?...
straightlight wrote:...Credit card storage should not be stored in session...
O0
JAY6390 wrote:Storing that data in the DB based on IP is a really bad idea too. IP's get re-assigned on a lot of home users' connections, and you could potentially (though not probable) fill in the data with someone else's.
PHP Session would be ideal, hence it being the first suggestion. While IP/DB would be one way of accomplishing a goal, it's agreeable that this wouldn't be the best method, although there would certainly be a few quick things done to make it a more solid option (like being logged in + matching IP, etc..)

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 10:00 pm
by JAY6390
Fair point, though if the customer was logged in, the IP wouldn't be required

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 10:23 pm
by straightlight
JAY6390 wrote:Fair point, though if the customer was logged in, the IP wouldn't be required
Correct. However, manual orders from the admin are also processed without the need to use an IP address.

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 10:29 pm
by JAY6390
Sorry, but you seem to be misunderstanding what we are talking about. We're not talking about creating orders. We're talking about remembering details if a customer starts to fill out data in the checkout process but doesn't finish, as per the original post. An order and the IP in the order table have nothing to do with any of this

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 10:46 pm
by straightlight
You missed the point on what I was implying. It's not about the orders; it's about the example on storing the IP address in a database. Whether it's about an order or not, IP addresses should not be stored other than on the browser period.

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 10:50 pm
by JAY6390
Right but I addressed why the IP is stored with the order... in case it's a fraudulent order, it can be used potentially

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 10:57 pm
by straightlight
For fraudulent order? Doesn't the fraud table already handles that? Granted, the fraud table wasn't always in OC as it was implemented after a few releases in v1.5x. Although, this methodology is now handled over API.

Re: Customer Info Disappears

Posted: Mon Jul 07, 2014 11:24 pm
by tacobandito
JAY6390 wrote:Fair point, though if the customer was logged in, the IP wouldn't be required
Conceded! You're absolutely right, customer being logged in would almost certainly be enough by itself.