Akopia Akopia Services

[Date Prev][Date Next][Thread Prev][Thread Next][Minivend by date ][Minivend by thread ]

RE: [mv] how I can dynamically generate "Routes" for each item?



******    message to minivend-users from "Christopher Thompson" <ct@arborinternet.com>     ******

I think do what you are asking all in data. I am not sure what you mean by
routes, but if you treat each vendor like most stores treat catagories it
show work. For example, in the simple demo replace renaissance,
impressionists, americana, surrealists with vendor1, vendor2, vendor3,
vendor4. Each vendor could even each have their own ProductFiles.

> -----Original Message-----
> From: owner-minivend-users@minivend.com
> [mailto:owner-minivend-users@minivend.com]On Behalf Of Mark Stosberg
> Sent: Saturday, March 04, 2000 7:39 PM
> To: Minivend User's List
> Subject: [mv] how I can dynamically generate "Routes" for each item?
>
>
> ******    message to minivend-users from Mark Stosberg
> <mark@summersault.com>     ******
>
>
> Hello,
>
>   I'm working with MV4 and am setting up a marketplace system where many
> sellers can sign up. When someone shops at the site they can put items
> from many different vendors in one cart. Because the number of vendors
> is expected to change frequently, and also be potentionally large, it's
> not feasible to maintain their Routing information in catalog.cfg. So
> I'm interested in a system where I dynamically generate the Routes for
> each item at checkout (or rather, 1 route for each distinct vendor
> represented in the basket. :). I tried out two ideas for modifying
> catalog.cfg, but neither of them worked. Both relied on the idea of
> grabbing some information from the environment as needed, which I'm not
> sure I can do.
>
> <snip>
> ParseVariables Yes
>  [sql  type=list sql="select email, last_name from seller where id =
> [scratch seller_id]"]
>  Variable    SELLER_EMAIL	 [sql-param email]
>  Variable	    SELLER_LAST_NAME [sql-param last_name]
>  [/sql]
>
> Route    SELLER	email 	_SELLER_EMAIL__
>
> Route	SELLER	email	[data base="seller" field="email"
> key="[scratch seller_id]"]
> </snip>
>
> So that approach didn't seem to work.
>
> Another idea I had was to change configurations through custom perl,
> possibly setting variables with a syntax like:
>
>    $Config->{key} = $value;
>
> BUT, it's not all clear how to do this with Route, because there are 4
> different parts to each data element, so how should I arrange this as a
> name = value pair? Or is there an appropriate hash I can adjust? If
> there's some documentation I missed on this, a pointer is appreciated.
>
> Thanks for help on this!
>
>    -mark
>
>   <<-------------------------------------------------------------->>
> personal website                <    Summersault Website Design
>    http://mark.stosberg.com/     >       http://www.summersault.com/
> -
> 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


Search for: Match: Format: Sort by: