Hi all.
I've been a long time user of C::A and I dig it. Until now, the
applications I've written have been pretty simple. They basically
consisted of a form with data passed via GET. A hidden input with the
run mode was all I needed to pass the data off to the right run mode.
Too easy.
The
Michael De Soto wrote:
I had a little bit of trouble passing the POST parameters to the login
run mode. This was solved by stashing them in the app's param during
cgiapp_init. I assume this is how we handle POST parameters. All the
docs I read didn't differentiate between GET and POST. I found
On Wed, Nov 26, 2008 at 4:32 AM, Michael De Soto [EMAIL PROTECTED] wrote:
The above works great for the the authentication aspect of my
application. Advice on the above would be great, but it's not the
primary reason I write now. Now I have trouble with a run mode called
edit_user. This simply
Thanks for the quick reply.
On Tue, Nov 25, 2008 at 12:39 PM, Michael Peters [EMAIL PROTECTED] wrote:
For normal name/value pairs there is no difference between GET and POST
params when handling them in your application. You can get both from
$self-query-param(). Something else is wrong with
