Re: [WebDNA] PayPal Instant Payment Notification Guide

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 103395
interpreted = N
texte = --Boundary-00=_WVtjKC+pueTwVkz Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit > I'm not sure about any of it ... Okay thanks, I thought you had referred to some documentation that said to put the cmd paraneter after everything else, but the PDF I read said to put it first. Maybe it makes no difference either way. > Putting the cmd > param at the end of the [formvariables] loop allowed me > to take advantage of the trailing ampersand left over > from the loop. If I put the param at the beginning of the > loop then I may have needed to code out the trailing > ampersand ... Trailing ampersands do not break anything, but it is really easy to do it this way if you're worried about it: cmd=whatever[formvariables]&[name]=[value][/formvariables] I'm going to do it this way when I test my code so I can see if it works with the cmd parameter prepended since that's what the PDF says to do. Probably won't test until next week though. > Thanks for checking my work I'm doing the same thing at the same time so I had a good reason ... :) Sincerely, Ken Grome --Boundary-00=_WVtjKC+pueTwVkz Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: 7bit > I'm not sure about any of it ...


Okay thanks, I thought you had referred to some documentation that said to put the cmd paraneter after everything else, but the PDF I read said to put it first. Maybe it makes no difference either way.



> Putting the cmd
> param at the end of the [formvariables] loop allowed me
> to take advantage of the trailing ampersand left over
> from the loop. If I put the param at the beginning of the
> loop then I may have needed to code out the trailing
> ampersand ...


Trailing ampersands do not break anything, but it is really easy to do it this way if you're worried about it:


cmd=whatever[formvariables]&[name]=[value][/formvariables]


I'm going to do it this way when I test my code so I can see if it works with the cmd parameter prepended since that's what the PDF says to do. Probably won't test until next week though.



> Thanks for checking my work


I'm doing the same thing at the same time so I had a good reason ... :)


Sincerely,
Ken Grome




--Boundary-00=_WVtjKC+pueTwVkz-- Associated Messages, from the most recent to the oldest:

    
--Boundary-00=_WVtjKC+pueTwVkz Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit > I'm not sure about any of it ... Okay thanks, I thought you had referred to some documentation that said to put the cmd paraneter after everything else, but the PDF I read said to put it first. Maybe it makes no difference either way. > Putting the cmd > param at the end of the [formvariables] loop allowed me > to take advantage of the trailing ampersand left over > from the loop. If I put the param at the beginning of the > loop then I may have needed to code out the trailing > ampersand ... Trailing ampersands do not break anything, but it is really easy to do it this way if you're worried about it: cmd=whatever[formvariables]&[name]=[value][/formvariables] I'm going to do it this way when I test my code so I can see if it works with the cmd parameter prepended since that's what the PDF says to do. Probably won't test until next week though. > Thanks for checking my work I'm doing the same thing at the same time so I had a good reason ... :) Sincerely, Ken Grome --Boundary-00=_WVtjKC+pueTwVkz Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: 7bit > I'm not sure about any of it ...


Okay thanks, I thought you had referred to some documentation that said to put the cmd paraneter after everything else, but the PDF I read said to put it first. Maybe it makes no difference either way.



> Putting the cmd
> param at the end of the [formvariables] loop allowed me
> to take advantage of the trailing ampersand left over
> from the loop. If I put the param at the beginning of the
> loop then I may have needed to code out the trailing
> ampersand ...


Trailing ampersands do not break anything, but it is really easy to do it this way if you're worried about it:


cmd=whatever[formvariables]&[name]=[value][/formvariables]


I'm going to do it this way when I test my code so I can see if it works with the cmd parameter prepended since that's what the PDF says to do. Probably won't test until next week though.



> Thanks for checking my work


I'm doing the same thing at the same time so I had a good reason ... :)


Sincerely,
Ken Grome




--Boundary-00=_WVtjKC+pueTwVkz-- 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:

Using Plug-In while running 1.6.1 (1997) Generating unique SKU from [cart] - Still Stumped... (1997) blank page from template (1997) Just Testing (1997) WebDNA5 & XML (2003) [Webcat 2]Next (1997) Sorting by date (1997) HomePage Caution (1997) [WebDNA] Pages dying (2008) Don't tick me off :) [elaspedtime] (1997) Where is the linux 4.02b5 FTP download located? (2000) customizing the color of user's pages (1997) ERROR in docs (2003) Append (1999) Country & Ship-to address & other fields ? (1997) WebCat2final1 crashes (1997) SiteEdit Pro, DataBase Helper and Europe (2000) no global [username] or [password] displayed ... (1997) bug in [SendMail] (1997) Shipping Via Actual UPS/FEDEX Zones (1999)