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:
Off Topic: Personal Web Server (1998)
WebCommerce: Folder organization ? (1997)
Nested tags count question (1997)
Re:Can this be done? (1997)
HTML Editors (1997)
[shownext max (1997)
hm. (2002)
Folder Follies (1998)
Line items in table cells (1997)
Blank orders after update to 5.1 (2004)
WebCatalog can't find database (1997)
Date and Time Math (1997)
[OT] Getting a domain listening on port 443 and port80? (2003)
Associative lookup style? (1997)
How do I get WebCatalog to interpret WebDNA tags in .html files? (1997)
Cart Number sequence (1997)
[listfiles] problems (1997)
Clickable maps and WebCatalog? (1996)
[WebDNA] WebDNA future (2010)
More on the email templates (1997)