|
||||||||||||
Form Field: The Form should be set to Method Post for optimum use with the CatalogIntegrator Cart. The Dummy Cart pages and some sample pages included with the Kit are set to Method Get, because that setting allows you to simulate cart action on your local computer. If you use any of those sample pages in your site, be sure to change the setting to "Post". item: product: price: nontax: submit button: B. Linking to the Cart: BuyButtons are linked to the cart by one of several "add.php" pages. The following are the standard "add" pages: add.php is the one used most. It is for single BuyObjects that do not require multiple option choices, such as different colors or sizes. Its action is to put the purchase into the cart and take the customer directly to the cart page. addgroup.php is a special variation for use with the Group BuyObject that allows you to place multiple products within the same Form Field. This is an advantage when you want your customers to be able to make several selections on the same page before adding them to the cart. The Group BuyObject must be linked to addgroup.php. addloop.php is an alternative to "add.php" that reloads the page when the submit button is clicked, instead of immediately taking the customer to the cart. It is useful for when you want your customers to be able to make multiple selections on the same page in sequence, instead of all at once. It is usually a good idea to combine this method with the "OK BuyObject" so that the customer gets an acknowledgement and knows that he has completed the purchase. Because addloop.php does not automatically go to the cart, it requires that a "View Cart" or "Checkout" button be on the page. addwOptions.php is the add page for the multiple option BuyObjects, such as those with radio buttons, checkboxes, popup menus, or the BuyObject with Inscription field. If your options are not showing up in the Product Description field of the cart, make sure the BuyObject is linked to "addwOptions.php". C. BuyObject Configuration and Setting of Fields: Each Item Field in your catalog must have a unique number. The cart tracks items ordered by the item number, not the product description, so be very sure to assign a unique item number to each and every BuyObject in your catalog. This includes Group BuyObjects and Image Maps. Item and Product values should not exceed 30 characters each in length unless the cart is customized to handle longer lengths. Group BuyObject limits: there is no arbitrary limit to the number of Group BuyObjects you can put inside a Group BuyObject form. The acceptable size (for you)of the page determines the practical limit. BuyObjects with multiple product fields, such as popups, radio buttons and checkboxes all populate the product column in the cart. Their aggregate length should not exceed 30 characters, so keep the values as short as possible. This includes blank spaces, which are also characters. D) Important Notes for the Unix cart: 1) The fields contained inside the BuyObjects Forms, such as "product", "item", "quantity", etc. are case sensitive, so don't change them or mix cases. 2) BuyObjects with multiple "product" fields, such as those with popups, radio buttons and checkboxes, must be linked to "addwOptions.php" or "AddloopwOptions.php", NOT "add.php" or "addloop.php". 3) Also, the product fields in those BuyObjects with multiple product fields, must be named "product[]". (with brackets after the word: []. Not simply "product", like in the other BuyObjects. 4) All the fields in the Group BuyObject Field Elements objects, must have the brackets following their names. In other words, they would be named item[], product[], quantity[], custID[] and so on. The prepared BuyObjects contained in the "CatalogIntegrator" extend script "main.html" for Golive, are already named with the above convention, but if you build your own custom BuyObjects, you'll need to pay attention to it. |
||||||||||||