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:
For Grant: Webcatalog 4.0 - When will we be able to betatest it? (2000)
OT: number of options in select menu (2002)
Mass download. (2003)
WebCat2 beta 11 - new prefs ... (1997)
[WebDNA] Basic Search (2008)
Formating found categories (1997)
Registration Form (1998)
Wild WebCat 98 Contest! (1998)
javascript problem copying values (2000)
Search in 2 or more catalogs (1997)
Character limit in [Search]? (1998)
Access Denied! But why? (1997)
WebDNA Solutions ... sorry! (1997)
f2 download problems (1997)
New Command prefs ... (1997)
OT: 800x600 (2003)
Random question (1998)
turning every 5th line red (1998)
Users.db [encrypt seed=????] (1998)
how to get [protect] tag from webcat3b3 to 3.03 on IIS working (1998)