Re: Using WebCat for product info requests

This WebDNA talk-list message is from

1997

It keeps the original formatting. numero = 13654
interpreted = N
texte = >I realize that I can do this quite readily with WebCat, but the problem>is that these products are not in a database, nor are they likely to be.>Can I accomplish something like this without a .db file, or do I need to>tell them to start building a database ASAP? It's certainly much easier if they're in a database (to help lead them towards a shopping site eventually), but there's nothing wrong with you just stuffing any old text into a custom database that sort of acts like a shopping cart.The hard part is creating a unique identifier to help WebCatalog remember who is adding what item to the pseudo-cart. I suggest that either you use the standard [cart] technique when the visitor enters the site, or you could get tricky and look at their [username]/[password] to see if they're blank and if so, throw up an [authenticate] dialog to ask for their first and last name. You would then use this [username]/[password] as the name of a database file you would create in the shoppingcarts folder (to get automatic housecleaning for old carts).Once the username/password is known, then every time they click on a 'more info' link, you would [append] that information to the database assigned to them. I think this whole thing can be done with 1 template and 1 database structure.Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ====Pacific Coast Software | WebCatalog, WebMerchant11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMasterSan Diego, CA 92128 | SiteGuard619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

>I realize that I can do this quite readily with WebCat, but the problem>is that these products are not in a database, nor are they likely to be.>Can I accomplish something like this without a .db file, or do I need to>tell them to start building a database ASAP? It's certainly much easier if they're in a database (to help lead them towards a shopping site eventually), but there's nothing wrong with you just stuffing any old text into a custom database that sort of acts like a shopping cart.The hard part is creating a unique identifier to help WebCatalog remember who is adding what item to the pseudo-cart. I suggest that either you use the standard [cart] technique when the visitor enters the site, or you could get tricky and look at their [username]/[password] to see if they're blank and if so, throw up an [authenticate] dialog to ask for their first and last name. You would then use this [username]/[password] as the name of a database file you would create in the shoppingcarts folder (to get automatic housecleaning for old carts).Once the username/password is known, then every time they click on a 'more info' link, you would [append] that information to the database assigned to them. I think this whole thing can be done with 1 template and 1 database structure.Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ====Pacific Coast Software | WebCatalog, WebMerchant11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMasterSan Diego, CA 92128 | SiteGuard619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Grant Hulbert

DOWNLOAD WEBDNA NOW!

Re: Using WebCat for product info requests

1997

Top Articles:

Related Readings: