Putting MvCALLs in MMUI

------=_NextPart_000_0011_01C4F197.4F567B80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I am using MMUI for my Miva store. In some cases, I would like to have =
Miva send certain data to a PHP script which will be written to populate =
the data into my MySQL database. I was told that I can have Miva send =
data to PHP scripts using MvCALL. I could use some assistance from you =
experts in determining where in MMUI I should place these calls.

I would like to use the MvCALL in places where the customer adds, =
deletes or changes items in their basket. I would also like to use the =
MvCALL during the Checkout process, after the customer has confirmed =
their "Ship To" and "Bill To" information and hit Continue.

Can someone tell me where in the MMUI I should place the calls so that =
they will be executed at the times I've mentioned?

Melanie S. Martin


------=_NextPart_000_0011_01C4F197.4F567B80--

Putting MvCALLs in MMUI



I use OUI, but since mmui seems to call the /lib/db.mv via a reference to
g.Module_Library_DB, I assume you could place the calls in the db.mv file
for execution. You would just need to find the proper functions in the
file.

For example: To pass order lines to a php program, you could look for:

<MvFUNCTION NAME = "Order_Create_From_Basket" PARAMETERS = "session_id,
total" STANDARDOUTPUTLEVEL = "">

in db.mv and add the following:

<MvCOMMENT>:::: Start tmp Line Segment ::::</MvCOMMENT>
<MvASSIGN NAME="tmp_line_order_id" VALUE="{OrderItems.d.order_id}">
<MvASSIGN NAME="tmp_line_count" VALUE="{l.line_count}">
<MvASSIGN NAME="tmp_line_bask_line" VALUE="{Baskets.d.line_id}">
<MvASSIGN NAME="tmp_line_sku" VALUE="{OrderItems.d.code}">
<MvASSIGN NAME="tmp_line_name" VALUE="{OrderItems.d.name}">
<MvASSIGN NAME="tmp_line_price" VALUE="{OrderItems.d.price}">
<MvASSIGN NAME="tmp_line_qty" VALUE="{OrderItems.d.quantity}">
<MvASSIGN NAME= "function" value="order_lines">
<MvCALL
ACTION="http://localhost/process_lines.php?"
METHOD="GET"
FIELDS="tmp_line_order_id,
tmp_line_count,
tmp_line_bask_line,
tmp_line_sku,
tmp_line_name,
tmp_line_price,
tmp_line_qty,
function">
</MvCALL>

The same approach could be used different functions in db.mv


I hope this helps, and please correct me if I am wrong about the db.mv
references in mmui, as I only am accustomed to OUI.

Ryan Erich Rodkey
Webmaster
Ace Mart Restaurant Supply
2653 Austin Highway
San Antonio, Texas 78218

Email: [email protected]
Phone: (210) 323-4492
Fax: (210) 323-4404
Web: <A HREF ="http://www.acemart.com">http://www.acemart.com</A>


-----Original Message-----
From: That Little Something Special, LLC
[mailto:[email protected]]
Sent: Monday, January 03, 2005 12:23 PM
To: [email protected]
Subject: [mrc] Putting MvCALLs in MMUI


I am using MMUI for my Miva store. In some cases, I would like to have Miva
send certain data to a PHP script which will be written to populate the data
into my MySQL database. I was told that I can have Miva send data to PHP
scripts using MvCALL. I could use some assistance from you experts in
determining where in MMUI I should place these calls.

I would like to use the MvCALL in places where the customer adds, deletes or
changes items in their basket. I would also like to use the MvCALL during
the Checkout process, after the customer has confirmed their "Ship To" and
"Bill To" information and hit Continue.

Can someone tell me where in the MMUI I should place the calls so that they
will be executed at the times I've mentioned?

Melanie S. Martin

Putting MvCALLs in MMUI



Actually, you'd want to first try using a System Extension module to do what you are
trying to accomplish. The System module has built-in functions that are called at
different times in the execution of the Merchant application. For example,
SystemModule_Action_Customer_Insert runs anytime a customer creates an account,
SystemModule_Action_Customer_Update runs when the account is updated. So, if you place
your MvCALL within those functions and use the global variables for input, you should be
good to go. (Note, the db.mv would be a good place to find what the system variables are
at that point, although you could also just look at the screen's form elements.)


-Bruce
......................................
PHOSPHOR Media
Featuring: StoreMan - A smarter way to manage Miva Merchant(tm) Store Content.
Download a hassle-free demo today
<A HREF ="http://www.phosphormedia.com/go.mv?ID=listsm">http://www.phosphormedia.com/go.mv?ID=listsm</A>
......................................




> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Ryan Rodkey
> Sent: Monday, January 03, 2005 11:18 AM
> To: 'That Little Something Special, LLC'; [email protected]
> Subject: RE: [mrc] Putting MvCALLs in MMUI
>
>
> I use OUI, but since mmui seems to call the /lib/db.mv via a reference to
> g.Module_Library_DB, I assume you could place the calls in the db.mv file
> for execution. You would just need to find the proper functions in the
> file.
>
> For example: To pass order lines to a php program, you could look for:
>
> <MvFUNCTION NAME = "Order_Create_From_Basket" PARAMETERS = "session_id,
> total" STANDARDOUTPUTLEVEL = "">
>
> in db.mv and add the following:
>
> <MvCOMMENT>:::: Start tmp Line Segment ::::</MvCOMMENT>
> <MvASSIGN NAME="tmp_line_order_id" VALUE="{OrderItems.d.order_id}">
> <MvASSIGN NAME="tmp_line_count" VALUE="{l.line_count}">
> <MvASSIGN NAME="tmp_line_bask_line" VALUE="{Baskets.d.line_id}">
> <MvASSIGN NAME="tmp_line_sku" VALUE="{OrderItems.d.code}">
> <MvASSIGN NAME="tmp_line_name" VALUE="{OrderItems.d.name}">
> <MvASSIGN NAME="tmp_line_price" VALUE="{OrderItems.d.price}">
> <MvASSIGN NAME="tmp_line_qty" VALUE="{OrderItems.d.quantity}">
> <MvASSIGN NAME= "function" value="order_lines">
> <MvCALL
> ACTION="http://localhost/process_lines.php?"
> METHOD="GET"
> FIELDS="tmp_line_order_id,
> tmp_line_count,
> tmp_line_bask_line,
> tmp_line_sku,
> tmp_line_name,
> tmp_line_price,
> tmp_line_qty,
> function">
> </MvCALL>
>
> The same approach could be used different functions in db.mv
>
>
> I hope this helps, and please correct me if I am wrong about the db.mv
> references in mmui, as I only am accustomed to OUI.
>
> Ryan Erich Rodkey
> Webmaster
> Ace Mart Restaurant Supply
> 2653 Austin Highway
> San Antonio, Texas 78218
>
> Email: [email protected]
> Phone: (210) 323-4492
> Fax: (210) 323-4404
> Web: <A HREF ="http://www.acemart.com">http://www.acemart.com</A>
>
>
> -----Original Message-----
> From: That Little Something Special, LLC
> [mailto:[email protected]]
> Sent: Monday, January 03, 2005 12:23 PM
> To: [email protected]
> Subject: [mrc] Putting MvCALLs in MMUI
>
>
> I am using MMUI for my Miva store. In some cases, I would like to have Miva
> send certain data to a PHP script which will be written to populate the data
> into my MySQL database. I was told that I can have Miva send data to PHP
> scripts using MvCALL. I could use some assistance from you experts in
> determining where in MMUI I should place these calls.
>
> I would like to use the MvCALL in places where the customer adds, deletes or
> changes items in their basket. I would also like to use the MvCALL during
> the Checkout process, after the customer has confirmed their "Ship To" and
> "Bill To" information and hit Continue.
>
> Can someone tell me where in the MMUI I should place the calls so that they
> will be executed at the times I've mentioned?
>
> Melanie S. Martin
>
>

Putting MvCALLs in MMUI




There's no need to edit the MMUI for this job; you can put your code in
modules, using functions that will be called at the appropriate
times. Editing MMUI would be quicker in the short run, but will make more
work for you if you ever have to deal with upgrades.

Someone else suggested a system extension module, but I would probably make
some different choices. For the add-to-abasket function, I would put the
MvCALL in a logging module. A system extension might be called in cases
where the product doesn't actually end up in the basket, e.g. if it's out
of stock. For checkout, I would use a fulfillment module, so that the
MvCALL would only be executed when the customer completes a
purchase. Otherwise, you might get false reports from customers who get
part-way thru the checkout process, and then abandon the purchase for some
reason.

Hope that helps --



>I am using MMUI for my Miva store. In some cases, I would like to have
>Miva send certain data to a PHP script which will be written to populate
>the data into my MySQL database. I was told that I can have Miva send
>data to PHP scripts using MvCALL. I could use some assistance from you
>experts in determining where in MMUI I should place these calls.
>
>I would like to use the MvCALL in places where the customer adds, deletes
>or changes items in their basket. I would also like to use the MvCALL
>during the Checkout process, after the customer has confirmed their "Ship
>To" and "Bill To" information and hit Continue.
>
>Can someone tell me where in the MMUI I should place the calls so that
>they will be executed at the times I've mentioned?
>
>Melanie S. Martin




Kent Multer | /| P.O.Box 701895, Dallas TX 75370
Magic Metal Productions | / | (214) 570 8264 voice/fax
KOBUSHI taiko drummers | | [email protected]
http://frontpage.dallas.net/~kent

Putting MvCALLs in MMUI



How do I get the source code for the modules?

----- Original Message -----
From: "Kent" <[email protected]>
To: "That Little Something Special, LLC"
<[email protected]>; <[email protected]>
Sent: Monday, January 03, 2005 7:35 PM
Subject: Re: [mrc] Putting MvCALLs in MMUI


>
> There's no need to edit the MMUI for this job; you can put your code in
> modules, using functions that will be called at the appropriate times.
> Editing MMUI would be quicker in the short run, but will make more work
> for you if you ever have to deal with upgrades.
>
> Someone else suggested a system extension module, but I would probably
> make some different choices. For the add-to-abasket function, I would put
> the MvCALL in a logging module. A system extension might be called in
> cases where the product doesn't actually end up in the basket, e.g. if
> it's out of stock. For checkout, I would use a fulfillment module, so
> that the MvCALL would only be executed when the customer completes a
> purchase. Otherwise, you might get false reports from customers who get
> part-way thru the checkout process, and then abandon the purchase for some
> reason.
>
> Hope that helps --
>
>
>
>>I am using MMUI for my Miva store. In some cases, I would like to have
>>Miva send certain data to a PHP script which will be written to populate
>>the data into my MySQL database. I was told that I can have Miva send
>>data to PHP scripts using MvCALL. I could use some assistance from you
>>experts in determining where in MMUI I should place these calls.
>>
>>I would like to use the MvCALL in places where the customer adds, deletes
>>or changes items in their basket. I would also like to use the MvCALL
>>during the Checkout process, after the customer has confirmed their "Ship
>>To" and "Bill To" information and hit Continue.
>>
>>Can someone tell me where in the MMUI I should place the calls so that
>>they will be executed at the times I've mentioned?
>>
>>Melanie S. Martin
>
>
>
>
> Kent Multer | /| P.O.Box 701895, Dallas TX 75370
> Magic Metal Productions | / | (214) 570 8264 voice/fax
> KOBUSHI taiko drummers | | [email protected]
>
> http://frontpage.dallas.net/~kent
>
>

Putting MvCALLs in MMUI




Miva doesn't have the greatest tool set for developers, but you can find
out what you need if you use a bit of creativity. There are sample modules
distributed with some versions of Merchant; if you look in the various
subfolders of the modules folder, you may find an "example.mv" file in some
of them. A common practice is to take one of the existing Miva modules,
whichever is closest to what you need, and then simply customize it.

P.S. On second thought, I think that a logging module could do both of the
jobs you need. There's a LogModule_Action_AuthorizePayment function, which
I think is called only when an order is completed succesfully.



>How do I get the source code for the modules?
>
>----- Original Message ----- From: "Kent" <[email protected]>
>To: "That Little Something Special, LLC"
><[email protected]>; <[email protected]>
>Sent: Monday, January 03, 2005 7:35 PM
>Subject: Re: [mrc] Putting MvCALLs in MMUI
>
>>
>>There's no need to edit the MMUI for this job; you can put your code in
>>modules, using functions that will be called at the appropriate times.
>>Editing MMUI would be quicker in the short run, but will make more work
>>for you if you ever have to deal with upgrades.
>>
>>Someone else suggested a system extension module, but I would probably
>>make some different choices. For the add-to-abasket function, I would
>>put the MvCALL in a logging module. A system extension might be called
>>in cases where the product doesn't actually end up in the basket, e.g. if
>>it's out of stock. For checkout, I would use a fulfillment module, so
>>that the MvCALL would only be executed when the customer completes a
>>purchase. Otherwise, you might get false reports from customers who get
>>part-way thru the checkout process, and then abandon the purchase for
>>some reason.
>>
>>Hope that helps --
>>
>>
>>>I am using MMUI for my Miva store. In some cases, I would like to have
>>>Miva send certain data to a PHP script which will be written to populate
>>>the data into my MySQL database. I was told that I can have Miva send
>>>data to PHP scripts using MvCALL. I could use some assistance from you
>>>experts in determining where in MMUI I should place these calls.
>>>
>>>I would like to use the MvCALL in places where the customer adds,
>>>deletes or changes items in their basket. I would also like to use the
>>>MvCALL during the Checkout process, after the customer has confirmed
>>>their "Ship To" and "Bill To" information and hit Continue.
>>>
>>>Can someone tell me where in the MMUI I should place the calls so that
>>>they will be executed at the times I've mentioned?
>>>
>>>Melanie S. Martin




Kent Multer | /| P.O.Box 701895, Dallas TX 75370
Magic Metal Productions | / | (214) 570 8264 voice/fax
KOBUSHI taiko drummers | | [email protected]
http://frontpage.dallas.net/~kent

Putting MvCALLs in MMUI



I think I may need to consider hiring a programmer to do this for me. I run
a compiled version of Miva (4.23) which makes it difficult for me to work
with modules. Besides, I am not sure I want to invest the time into
learning more about MivaScript when most of what I want to accomplish would
work better for me with the tools I already know (PHP, ASP, etc.).

Are there developers out there who could write something simple for me to
accomplish what I need in Miva?

----- Original Message -----
From: "Kent" <[email protected]>
To: "That Little Something Special, LLC"
<[email protected]>; <[email protected]>
Sent: Tuesday, January 04, 2005 12:11 AM
Subject: Re: [mrc] Putting MvCALLs in MMUI


>
> Miva doesn't have the greatest tool set for developers, but you can find
> out what you need if you use a bit of creativity. There are sample
> modules distributed with some versions of Merchant; if you look in the
> various subfolders of the modules folder, you may find an "example.mv"
> file in some of them. A common practice is to take one of the existing
> Miva modules, whichever is closest to what you need, and then simply
> customize it.
>
> P.S. On second thought, I think that a logging module could do both of
> the jobs you need. There's a LogModule_Action_AuthorizePayment function,
> which I think is called only when an order is completed succesfully.
>
>
>
>>How do I get the source code for the modules?
>>
>>----- Original Message ----- From: "Kent" <[email protected]>
>>To: "That Little Something Special, LLC"
>><[email protected]>; <[email protected]>
>>Sent: Monday, January 03, 2005 7:35 PM
>>Subject: Re: [mrc] Putting MvCALLs in MMUI
>>
>>>
>>>There's no need to edit the MMUI for this job; you can put your code in
>>>modules, using functions that will be called at the appropriate times.
>>>Editing MMUI would be quicker in the short run, but will make more work
>>>for you if you ever have to deal with upgrades.
>>>
>>>Someone else suggested a system extension module, but I would probably
>>>make some different choices. For the add-to-abasket function, I would
>>>put the MvCALL in a logging module. A system extension might be called
>>>in cases where the product doesn't actually end up in the basket, e.g. if
>>>it's out of stock. For checkout, I would use a fulfillment module, so
>>>that the MvCALL would only be executed when the customer completes a
>>>purchase. Otherwise, you might get false reports from customers who get
>>>part-way thru the checkout process, and then abandon the purchase for
>>>some reason.
>>>
>>>Hope that helps --
>>>
>>>
>>>>I am using MMUI for my Miva store. In some cases, I would like to have
>>>>Miva send certain data to a PHP script which will be written to populate
>>>>the data into my MySQL database. I was told that I can have Miva send
>>>>data to PHP scripts using MvCALL. I could use some assistance from you
>>>>experts in determining where in MMUI I should place these calls.
>>>>
>>>>I would like to use the MvCALL in places where the customer adds,
>>>>deletes or changes items in their basket. I would also like to use the
>>>>MvCALL during the Checkout process, after the customer has confirmed
>>>>their "Ship To" and "Bill To" information and hit Continue.
>>>>
>>>>Can someone tell me where in the MMUI I should place the calls so that
>>>>they will be executed at the times I've mentioned?
>>>>
>>>>Melanie S. Martin
>
>
>
>
> Kent Multer | /| P.O.Box 701895, Dallas TX 75370
> Magic Metal Productions | / | (214) 570 8264 voice/fax
> KOBUSHI taiko drummers | | [email protected]
>
> http://frontpage.dallas.net/~kent
>
>

Putting MvCALLs in MMUI



I think I may need to consider hiring a programmer to do this for me. I run
a compiled version of Miva (4.23) which makes it difficult for me to work
with modules. Besides, I am not sure I want to invest the time into
learning more about MivaScript when most of what I want to accomplish would
work better for me with the tools I already know (PHP, ASP, etc.).

Are there developers out there who could write something simple for me to
accomplish what I need in Miva?

----- Original Message -----
From: "Kent" <[email protected]>
To: "That Little Something Special, LLC"
<[email protected]>; <[email protected]>
Sent: Tuesday, January 04, 2005 12:11 AM
Subject: Re: [mrc] Putting MvCALLs in MMUI


>
> Miva doesn't have the greatest tool set for developers, but you can find
> out what you need if you use a bit of creativity. There are sample
> modules distributed with some versions of Merchant; if you look in the
> various subfolders of the modules folder, you may find an "example.mv"
> file in some of them. A common practice is to take one of the existing
> Miva modules, whichever is closest to what you need, and then simply
> customize it.
>
> P.S. On second thought, I think that a logging module could do both of
> the jobs you need. There's a LogModule_Action_AuthorizePayment function,
> which I think is called only when an order is completed succesfully.
>
>
>
>>How do I get the source code for the modules?
>>
>>----- Original Message ----- From: "Kent" <[email protected]>
>>To: "That Little Something Special, LLC"
>><[email protected]>; <[email protected]>
>>Sent: Monday, January 03, 2005 7:35 PM
>>Subject: Re: [mrc] Putting MvCALLs in MMUI
>>
>>>
>>>There's no need to edit the MMUI for this job; you can put your code in
>>>modules, using functions that will be called at the appropriate times.
>>>Editing MMUI would be quicker in the short run, but will make more work
>>>for you if you ever have to deal with upgrades.
>>>
>>>Someone else suggested a system extension module, but I would probably
>>>make some different choices. For the add-to-abasket function, I would
>>>put the MvCALL in a logging module. A system extension might be called
>>>in cases where the product doesn't actually end up in the basket, e.g. if
>>>it's out of stock. For checkout, I would use a fulfillment module, so
>>>that the MvCALL would only be executed when the customer completes a
>>>purchase. Otherwise, you might get false reports from customers who get
>>>part-way thru the checkout process, and then abandon the purchase for
>>>some reason.
>>>
>>>Hope that helps --
>>>
>>>
>>>>I am using MMUI for my Miva store. In some cases, I would like to have
>>>>Miva send certain data to a PHP script which will be written to populate
>>>>the data into my MySQL database. I was told that I can have Miva send
>>>>data to PHP scripts using MvCALL. I could use some assistance from you
>>>>experts in determining where in MMUI I should place these calls.
>>>>
>>>>I would like to use the MvCALL in places where the customer adds,
>>>>deletes or changes items in their basket. I would also like to use the
>>>>MvCALL during the Checkout process, after the customer has confirmed
>>>>their "Ship To" and "Bill To" information and hit Continue.
>>>>
>>>>Can someone tell me where in the MMUI I should place the calls so that
>>>>they will be executed at the times I've mentioned?
>>>>
>>>>Melanie S. Martin
>
>
>
>
> Kent Multer | /| P.O.Box 701895, Dallas TX 75370
> Magic Metal Productions | / | (214) 570 8264 voice/fax
> KOBUSHI taiko drummers | | [email protected]
>
> http://frontpage.dallas.net/~kent
>
>

Putting MvCALLs in MMUI



I think I may need to consider hiring a programmer to do this for me. I run
a compiled version of Miva (4.23) which makes it difficult for me to work
with modules. Besides, I am not sure I want to invest the time into
learning more about MivaScript when most of what I want to accomplish would
work better for me with the tools I already know (PHP, ASP, etc.).

Are there developers out there who could write something simple for me to
accomplish what I need in Miva?

----- Original Message -----
From: "Kent" <[email protected]>
To: "That Little Something Special, LLC"
<[email protected]>; <[email protected]>
Sent: Tuesday, January 04, 2005 12:11 AM
Subject: Re: [mrc] Putting MvCALLs in MMUI


>
> Miva doesn't have the greatest tool set for developers, but you can find
> out what you need if you use a bit of creativity. There are sample
> modules distributed with some versions of Merchant; if you look in the
> various subfolders of the modules folder, you may find an "example.mv"
> file in some of them. A common practice is to take one of the existing
> Miva modules, whichever is closest to what you need, and then simply
> customize it.
>
> P.S. On second thought, I think that a logging module could do both of
> the jobs you need. There's a LogModule_Action_AuthorizePayment function,
> which I think is called only when an order is completed succesfully.
>
>
>
>>How do I get the source code for the modules?
>>
>>----- Original Message ----- From: "Kent" <[email protected]>
>>To: "That Little Something Special, LLC"
>><[email protected]>; <[email protected]>
>>Sent: Monday, January 03, 2005 7:35 PM
>>Subject: Re: [mrc] Putting MvCALLs in MMUI
>>
>>>
>>>There's no need to edit the MMUI for this job; you can put your code in
>>>modules, using functions that will be called at the appropriate times.
>>>Editing MMUI would be quicker in the short run, but will make more work
>>>for you if you ever have to deal with upgrades.
>>>
>>>Someone else suggested a system extension module, but I would probably
>>>make some different choices. For the add-to-abasket function, I would
>>>put the MvCALL in a logging module. A system extension might be called
>>>in cases where the product doesn't actually end up in the basket, e.g. if
>>>it's out of stock. For checkout, I would use a fulfillment module, so
>>>that the MvCALL would only be executed when the customer completes a
>>>purchase. Otherwise, you might get false reports from customers who get
>>>part-way thru the checkout process, and then abandon the purchase for
>>>some reason.
>>>
>>>Hope that helps --
>>>
>>>
>>>>I am using MMUI for my Miva store. In some cases, I would like to have
>>>>Miva send certain data to a PHP script which will be written to populate
>>>>the data into my MySQL database. I was told that I can have Miva send
>>>>data to PHP scripts using MvCALL. I could use some assistance from you
>>>>experts in determining where in MMUI I should place these calls.
>>>>
>>>>I would like to use the MvCALL in places where the customer adds,
>>>>deletes or changes items in their basket. I would also like to use the
>>>>MvCALL during the Checkout process, after the customer has confirmed
>>>>their "Ship To" and "Bill To" information and hit Continue.
>>>>
>>>>Can someone tell me where in the MMUI I should place the calls so that
>>>>they will be executed at the times I've mentioned?
>>>>
>>>>Melanie S. Martin
>
>
>
>
> Kent Multer | /| P.O.Box 701895, Dallas TX 75370
> Magic Metal Productions | / | (214) 570 8264 voice/fax
> KOBUSHI taiko drummers | | [email protected]
>
> http://frontpage.dallas.net/~kent
>
>

Putting MvCALLs in MMUI



One suggestion, you could install the OpenUI, then it'd be pretty easy to
use OpenTokens to add %CALL()% tokens to the Headers of some screens. You
can easily surround this with a contional on the Action field.

Even better, use the OpenDesigner to hook quickly into the LOG functions
that occur whenever one of these actions happen. Then, the %CALL()% would
be easy to add in without the conditionals.

Either way, fairly easy to do without much hassle and without the headache
of writing a module from scratch (or hiring a developer).

Darren Ehlers
OpenUI Developer Consortium
<A HREF ="http://www.openui.org/ ">http://www.openui.org/ </A>

Double the speed of your OpenTokens, only $40!!
<A HREF ="http://www.openui.org/purchase/?pc=OPENUI-TURBO&pn=OpenUI%20Turbo ">http://www.openui.org/purchase/?pc=O...OpenUI%20Turbo </A>

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of That
> Little Something Special, LLC
> Sent: Tuesday, January 04, 2005 7:35 AM
> To: Kent; [email protected]
> Subject: Re: [mrc] Putting MvCALLs in MMUI
>
>
> I think I may need to consider hiring a programmer to do this
> for me. I run
> a compiled version of Miva (4.23) which makes it difficult
> for me to work
> with modules. Besides, I am not sure I want to invest the time into
> learning more about MivaScript when most of what I want to
> accomplish would
> work better for me with the tools I already know (PHP, ASP, etc.).
>
> Are there developers out there who could write something
> simple for me to
> accomplish what I need in Miva?
>
> ----- Original Message -----
> From: "Kent" <[email protected]>
> To: "That Little Something Special, LLC"
> <[email protected]>; <[email protected]>
> Sent: Tuesday, January 04, 2005 12:11 AM
> Subject: Re: [mrc] Putting MvCALLs in MMUI
>
>
> >
> > Miva doesn't have the greatest tool set for developers, but
> you can find
> > out what you need if you use a bit of creativity. There are sample
> > modules distributed with some versions of Merchant; if you
> look in the
> > various subfolders of the modules folder, you may find an
> "example.mv"
> > file in some of them. A common practice is to take one of
> the existing
> > Miva modules, whichever is closest to what you need, and
> then simply
> > customize it.
> >
> > P.S. On second thought, I think that a logging module
> could do both of
> > the jobs you need. There's a
> LogModule_Action_AuthorizePayment function,
> > which I think is called only when an order is completed succesfully.
> >
> >
> >
> >>How do I get the source code for the modules?
> >>
> >>----- Original Message ----- From: "Kent" <[email protected]>
> >>To: "That Little Something Special, LLC"
> >><[email protected]>; <[email protected]>
> >>Sent: Monday, January 03, 2005 7:35 PM
> >>Subject: Re: [mrc] Putting MvCALLs in MMUI
> >>
> >>>
> >>>There's no need to edit the MMUI for this job; you can put
> your code in
> >>>modules, using functions that will be called at the
> appropriate times.
> >>>Editing MMUI would be quicker in the short run, but will
> make more work
> >>>for you if you ever have to deal with upgrades.
> >>>
> >>>Someone else suggested a system extension module, but I
> would probably
> >>>make some different choices. For the add-to-abasket
> function, I would
> >>>put the MvCALL in a logging module. A system extension
> might be called
> >>>in cases where the product doesn't actually end up in the
> basket, e.g. if
> >>>it's out of stock. For checkout, I would use a
> fulfillment module, so
> >>>that the MvCALL would only be executed when the customer
> completes a
> >>>purchase. Otherwise, you might get false reports from
> customers who get
> >>>part-way thru the checkout process, and then abandon the
> purchase for
> >>>some reason.
> >>>
> >>>Hope that helps --
> >>>
> >>>
> >>>>I am using MMUI for my Miva store. In some cases, I
> would like to have
> >>>>Miva send certain data to a PHP script which will be
> written to populate
> >>>>the data into my MySQL database. I was told that I can
> have Miva send
> >>>>data to PHP scripts using MvCALL. I could use some
> assistance from you
> >>>>experts in determining where in MMUI I should place these calls.
> >>>>
> >>>>I would like to use the MvCALL in places where the customer adds,
> >>>>deletes or changes items in their basket. I would also
> like to use the
> >>>>MvCALL during the Checkout process, after the customer
> has confirmed
> >>>>their "Ship To" and "Bill To" information and hit Continue.
> >>>>
> >>>>Can someone tell me where in the MMUI I should place the
> calls so that
> >>>>they will be executed at the times I've mentioned?
> >>>>
> >>>>Melanie S. Martin
> >
> >
> >
> >
> > Kent Multer | /| P.O.Box 701895,
> Dallas TX 75370
> > Magic Metal Productions | / | (214) 570 8264 voice/fax
> > KOBUSHI taiko drummers | | [email protected]
> >
> > http://frontpage.dallas.net/~kent
> >
> >
>
>