Eddie you asked:
"What is the standard, ShopSite-company-recognized, approach to assing
DATA from the front-end to the back-end, data that is UNIQUE to each
line item?"
The information in the cart for each product, with the exception of the
one text box under Ordering Options, where the shopper can enter text,
all comes from the ShopSite products database and is not changeable by
the shopper.
The one exception to this would be the variable price product option,
Pro stores only, which allows the Name, Price and Sku to be variable
depending on how the merchant has configured it. Perhaps this option
would work for you. You could create a custom product template that is
used with the variable price option for your product. If the price is
always the same you could hard code that value instead of making it
variable. You could use the variable sku field to hold the special
information that you need. That information will then be passed to the
shopping cart.
In the shopping cart you would modify the tag that displays the product
table to exclude displaying of the SKU.(*see below) You would also
need to set your store to send html email receipts so that the
information would be hidden on the shopper receipt.(It would be visible
in the normal text receipt) It would still be available to the merchant
in the backoffice and probably on the mechant copy of the receipt.
*[-- SC_Cart --] would become
[-- SC_Cart delete quantity name price total --]
Note that sku is missing from the list. There are 4 of 5 places in the
shopping cart template file that this would need to be done.
Jim
PS, I speak for myself since this is a user to user newgroup and not an
official means of providing ShopSite support.
Eddie Caplan wrote:
Jim,
Thanks for all the help, both here and in your private email. You
understand why I want/need to pass information reliably from the
front-end to the back-end of the sales process. (I won't go into WHY
here for my own security concerns).
BUT...
I simply cannot think of how to do it, either by pre-setting PHP
session variables before the customer goes to the cart, or using the
Javascript in the cart, adding <input type="hidden"> variables in the
shopping cart form, or by passing additional parameters to the custom
CGI script. Each approach has some flaw that prevents success:
Really, every approach seemed promising. I guess what I'm asking is,
"What is the standard, ShopSite-company-recognized, approach to passing
DATA from the front-end to the back-end, data that is UNIQUE to each
line item?"
Thanks again,
Eddie
P.S. Jim, do you speak for ShopSite?
In article <cnedig$6la$1@eval.shopsite.com>, jim
jstavast@xmission.com> wrote:
There is javascript in the shopping cart screens to handle data
validation etc. In version 7.1 there is a new field added to the
Commerce Setup > Order System > Shopping Cart, Checkout, Confirmation
screens called "Javascript added at start of built-in CheckIt function:"
You can enter your javascript checking in there and it will become
part of the built in CheckIt function. That may be a way for you to do
what you want.
Jim
Eddie Caplan wrote:
Is it possible to have ShopSite make a call to a function (presumably
JavaScript) when the "Remove" button is pressed in the shopping cart?
Thanks,
Eddie