Re: WebDNA tags in WebMerchant email templates ...
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 15760
interpreted = N
texte = >>1 - Assign serial numbers at the time of the WebCat $purchase >>command, and hope that the cc approval actually takes place. But that >>means whenever an attempted approval fails, I will have to go into my >>serialnumbers.db file and manually *reverse* the changes made by >>WebCat for those failed purchases ...>While I agree that it would be great to have WebDNA available to >WebMerchant, there might be a way to get what you need to do done. > >>From what I can tell, you can access anything inside the shopping cart >from WebMerchant. So, if at the time of purchase, you put a serial# >inside a header field of the shopping cart, you will be able to send this >in a message after credit card approval. > >Haven't tried it, but it seems like it should work. Thanks for the idea, Sandy.Yes, I know I can pass the SN thru to WebMerchant using one of the header fields (or the textA-E lineitem fields). I also know that WebMerchant will put this data into its approved email message that gets sent to the buyer if I want it to.But that still doesn't solve my problem ...Because before I can put those SN's into the order file in the first place, I have to *assign* them to that order ... which basically means removing them from the SN database (or flagging them as unavailable for future purchases) ... BEFORE they are paid for.That means every time a cc purchase fails, I have to go into the SN database and *un-issue* the SN's which were improperly issued to the failed purchase.Basically, this is the wrong way to go about it. Not that it won't work, but the fact is that SN's should not be assigned until AFTER the appropriate credit card charges are authorized ... right?All I want is to assign the SN's AFTER cc approval, not before, so I don't have to go into the SN database every time an attempted software purchase fails, just to reverse WebCat's assignment of SN's that should never have been assigned in the first place.That's the function that WebCat and WebMerchant cannot handle together ... :(I think WebMerchant should have a feature that lets us CHOOSE WHICH APPLICATION we want to process our approved and sorry email templates.If we could simply choose to have *WebCatalog* process the approved email template, for example, that means we could use all the standard WebDNA contexts we want to use in that template -- because WebCatalog can handle standard WebDNA contexts while WebMerchant cannot.When I look at the reasons why people choose to use WebMerchant, I do not see any real value in having WebMerchant process the approved and sorry email templates itself -- not when Webcatalog is sitting right there, capable of far more powerful email template processing than WebMerchant.All WebMerchant really MUST do is identify the particular response coming from MacAuthorize when a cc is submitted. Then, instead of processing its own email templates, it could tell WebCatalog to process similar templates -- ones with embedded WebDNA contexts in them to take care of the WebDNA tasks that need to be taken care of only AFTER a cc order is approved or denied by Macauthorize ... :)Sincerely, Ken Grome ken@iav.com 808-737-6499 WebDNA Solutions http://webdna.net/
Associated Messages, from the most recent to the oldest:
>>1 - Assign serial numbers at the time of the WebCat $purchase >>command, and hope that the cc approval actually takes place. But that >>means whenever an attempted approval fails, I will have to go into my >>serialnumbers.db file and manually *reverse* the changes made by >>WebCat for those failed purchases ...>While I agree that it would be great to have WebDNA available to >WebMerchant, there might be a way to get what you need to do done. > >>From what I can tell, you can access anything inside the shopping cart >from WebMerchant. So, if at the time of purchase, you put a serial# >inside a header field of the shopping cart, you will be able to send this >in a message after credit card approval. > >Haven't tried it, but it seems like it should work. Thanks for the idea, Sandy.Yes, I know I can pass the SN thru to WebMerchant using one of the header fields (or the textA-E lineitem fields). I also know that WebMerchant will put this data into its approved email message that gets sent to the buyer if I want it to.But that still doesn't solve my problem ...Because before I can put those SN's into the
order file in the first place, I have to *assign* them to that order ... which basically means removing them from the SN database (or flagging them as unavailable for future purchases) ... BEFORE they are paid for.That means every time a cc purchase fails, I have to go into the SN database and *un-issue* the SN's which were improperly issued to the failed purchase.Basically, this is the wrong way to go about it. Not that it won't work, but the fact is that SN's should not be assigned until AFTER the appropriate credit card charges are authorized ... right?All I want is to assign the SN's AFTER cc approval, not before, so I don't have to go into the SN database every time an attempted software purchase fails, just to reverse WebCat's assignment of SN's that should never have been assigned in the first place.That's the function that WebCat and WebMerchant cannot handle together ... :(I think WebMerchant should have a feature that lets us CHOOSE WHICH APPLICATION we want to process our approved and sorry email templates.If we could simply choose to have *WebCatalog* process the approved email template, for example, that means we could use all the standard WebDNA contexts we want to use in that template -- because WebCatalog can handle standard WebDNA contexts while WebMerchant cannot.When I look at the reasons why people choose to use WebMerchant, I do not see any real value in having WebMerchant process the approved and sorry email templates itself -- not when Webcatalog is sitting right there, capable of far more powerful email template processing than WebMerchant.All WebMerchant really MUST do is identify the particular response coming from MacAuthorize when a cc is submitted. Then, instead of processing its own email templates, it could tell WebCatalog to process similar templates -- ones with embedded WebDNA contexts in them to take care of the WebDNA tasks that need to be taken care of only AFTER a cc order is approved or denied by Macauthorize ... :)Sincerely, Ken Grome ken@iav.com 808-737-6499 WebDNA Solutions http://webdna.net/
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Problems passing [SKU] with $Replace in 2.0 (1997)
ACGI processing for .html (1997)
Need some Java Script Code (2003)
RE: WebDNA-Talk searchable? (1997)
Applescript, WebDNA, and PDF (1997)
2.1 Stuff (1998)
WC2.0 Memory Requirements (1997)
carriage returns in data (1997)
Exclude by date - multiple (1997)
Virtual hosting and webcatNT (1997)
Attention all list readers (1997)
[WebDNA] WebDNA on a cPanel server? Maybe not ... (2019)
Change in Host? (1999)
Random Command (1997)
Flash Stores (2003)
Un[url]ize (1999)
Dark Horse Comics success story (1997)
Weird bug, or is there something amiss? (1997)
math on date? (1997)
Help name our technology! (1997)