Background Running: current stable of mp2 and libapreq-devel
Problem:
I'm allowing GET style urls to forms for pre-population
If the POST action is dirty though, i get cross contamination of
vars IF there was a NULL action in the form
ie:
url:
[EMAIL PROTECTED]&su
typo. i'm not in good typing mode today - i strained something in my
neck, and have having trouble motivating myself to work, much less
perform correctly.
thanks for the note.
On Oct 31, 2005, at 6:18 PM, Philip M. Gollucci wrote:
I assume this is a typo, but that should be method="POST"
On Oct 31, 2005, at 6:29 PM, Joe Schaefer wrote:
pulling POST or GET data for a given fieldname
In place of param(), use the body() or args() methods, respectively.
Simple and stupid enough. Many thanks!
Jonathan <[EMAIL PROTECTED]> writes:
> but, can i hope (can i? seriously.) that there is some mechanism in
> mp2/libapreq that will let me explcitly choose whether param is
> pulling POST or GET data for a given fieldname
In place of param(), use the body() or args() methods, respectively.
-
Jonathan wrote:
{form action="" method=POST"}
I assume this is a typo, but that should be method="POST"
just to state the obvious. ^
--
END
What doesn't kill us can only make us stronger.
Background Running: current stable of mp2 and libapreq-devel
Problem:
I'm allowing GET style urls to forms for pre-population
If the POST action is dirty though, i get cross contamination of
vars IF there was a NULL action in the form
ie:
url:
[EMAIL PROTECTED]&s