Im trying to understand the advantages behind opting by using a
Self-Process PHP Form, instead of having a form and then point the action of
the form to another .php page.
Can anyone point me some resources about this. Why using one instead of
another. What are the main advantages?
Regard
quot;
To: "'PHP-General List'"
Sent: Friday, April 24, 2009 2:34 PM
Subject: [PHP] Self-Process php forms or not?
I'm trying to understand the advantages behind opting by using a
Self-Process PHP Form, instead of having a form and then point the action of
the form to anot
are.hu]
> Sent: sexta-feira, 24 de Abril de 2009 13:53
> To: 'PHP-General List'
> Subject: Re: [PHP] Self-Process php forms or not?
>
> I think the main advantage is that if something goes wrong processing
> the
> datas, you can show the form again without redirecting a
From: "MEM"
To: "'PHP-General List'"
Sent: Friday, April 24, 2009 2:34 PM
Subject: [PHP] Self-Process php forms or not?
I'm trying to understand the advantages behind opting by using a
Self-Process PHP Form, instead of having a form and then point the
[snip] What about the moto: "let's separate business from presentation?"[/snip]
This depends on how strictly you're following any given model like MVC. IMHO
you should use the right tool for the job.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/uns
t;'Sándor Tamás (HostWare Kft.)'" ;
"'PHP-General List'"
Sent: Friday, April 24, 2009 3:03 PM
Subject: RE: [PHP] Self-Process php forms or not?
So, on your opinion, we can call that method, on some circumstances, a good
practice?
What about the moto: "le
moto: "let's separate business from presentation?"
>
>
> Thanks once again,
> Márcio
> -Original Message-
> From: Sándor Tamás (HostWare Kft.) [mailto:sandorta...@hostware.hu]
> Sent: sexta-feira, 24 de Abril de 2009 13:53
> To: 'PHP-General List'
&
ril de 2009 14:20
> To: php-general@lists.php.net
> Subject: Re: [PHP] Self-Process php forms or not?
>
> Having a script that is self executing - when it posts back to itself
> instead of a separate script - has absolutely nothing to do with the
> separation of business and pr
Kft.) [mailto:sandorta...@hostware.hu]
> Sent: Friday, April 24, 2009 8:53 AM
> To: 'PHP-General List'
> Subject: Re: [PHP] Self-Process php forms or not?
>
> I think the main advantage is that if something goes wrong processing
> the
> datas, you can show the form
May be it is best time to for you to start using Zend Framework -> Zend_Form
-Original Message-
From: MEM [mailto:tal...@gmail.com]
Sent: Thursday, October 01, 2009 3:01 PM
To: 'Bob McConnell'; 'PHP-General List'
Subject: RE: [PHP] Self-Process php forms or not?
On 10/1/09 8:00 AM, "MEM" wrote:
> One last question about this:
>
> I've done a self submit form, after hearing all the advantages expressed
> here.
> But how could we relate, without using javascript, a self submit form with a
> "success page" or a "confirmation page" that doesn't show the fo
ent: 01 October 2009 13:01
To: 'Bob McConnell'; 'PHP-General List'
Subject: RE: [PHP] Self-Process php forms or not?
One last question about this:
I've done a self submit form, after hearing all the advantages expressed
here.
But how could we relate, without using javasc
Original Message
> From: Mert Oztekin
> To: MEM ; Bob McConnell ; PHP-General List
>
> Sent: Thursday, October 1, 2009 5:16:40 AM
> Subject: RE: [PHP] Self-Process php forms or not?
>
> May be it is best time to for you to start using Zend Framework -> Zend
At 1:00 PM +0100 10/1/09, MEM wrote:
One last question about this:
I've done a self submit form, after hearing all the advantages expressed
here.
But how could we relate, without using javascript, a self submit form with a
"success page" or a "confirmation page" that doesn't show the form?
Can
On Thu, 2009-10-01 at 09:30 -0400, Tom Worster wrote:
> On 10/1/09 8:00 AM, "MEM" wrote:
>
> > One last question about this:
> >
> > I've done a self submit form, after hearing all the advantages expressed
> > here.
> > But how could we relate, without using javascript, a self submit form with
On 10/1/09 10:13 AM, "tedd" wrote:
> At 1:00 PM +0100 10/1/09, MEM wrote:
>> One last question about this:
>>
>> I've done a self submit form, after hearing all the advantages expressed
>> here.
>> But how could we relate, without using javascript, a self submit form with a
>> "success page" or
7;
> Subject: Re: [PHP] Self-Process php forms or not?
>
> On 10/1/09 10:13 AM, "tedd" wrote:
>
> > At 1:00 PM +0100 10/1/09, MEM wrote:
> >> One last question about this:
> >>
> >> I've done a self submit form, after hearing all the advant
Hello,
on 10/01/2009 09:00 AM MEM said the following:
> One last question about this:
>
> I've done a self submit form, after hearing all the advantages expressed
> here.
> But how could we relate, without using javascript, a self submit form with a
> "success page" or a "confirmation page" that
I try to avoid the use of hidden form elements as much as possible,
especially for tracking whether a user has submitted a form or not...
I use name="submit" for the submit button instead, that will pass the
value of the submit button to the action script.
above all i use a template engine, smart
Hello,
on 10/02/2009 04:41 AM kranthi said the following:
> I try to avoid the use of hidden form elements as much as possible,
> especially for tracking whether a user has submitted a form or not...
>
> I use name="submit" for the submit button instead, that will pass the
> value of the submit b
>> That only works if the user clicks on that submit button. If the user
>> hits the enter key in a text input, the form is submitted but the submit
>> input variable is not set. That is why an hidden input is a safer solution.
i doubt that, because i use the above mentioned method in nearly all
o
and yes i forgot to mention... i avoid hidden form elements because
they can be modified very easily and hence pose a security threat.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Fri, 2009-10-02 at 13:55 +0530, kranthi wrote:
> and yes i forgot to mention... i avoid hidden form elements because
> they can be modified very easily and hence pose a security threat.
>
You say you don't use hidden fields because they can be modified too
easily, yet you say you check for the
>> You say you don't use hidden fields because they can be modified too
>> easily, yet you say you check for the submit button? Which out of the
>> two do you do, as last time I checked, modifying one form field is as
>> easy as changing any other!
I completely agree with you. changing submit text
k
> Cc: Manuel Lemos; php-general@lists.php.net; MEM; Bob McConnell
> Subject: Re: [PHP] Self-Process php forms or not?
>
> >> You say you don't use hidden fields because they can be modified too
> >> easily, yet you say you check for the submit button? Which out o
At 1:55 PM +0530 10/2/09, kranthi wrote:
and yes i forgot to mention... i avoid hidden form elements because
they can be modified very easily and hence pose a security threat.
That depends upon how sloppy you are in coding.
NONE of my hidden variables pose any security problems whatsoever.
Ch
At 3:06 PM +0100 10/2/09, MEM wrote:
I want to apologize to you all. I have mentioned two things on the same
basket, but it was not appropriate. Since a confirmation page is not the
same thing as a success page.
Let's forget about the confirmation page, since it's not required.
I'm now understa
> You can set it up any number of ways. There is no
> absolute need for a redirect. Everything can be
> done in one form, or not -- your choice.
>
> Cheers,
>
> tedd
Yes. But since I don't want to display a success information + form fields,
but only the success information,
I believe the only w
At 3:35 PM +0100 10/2/09, MEM wrote:
> You can set it up any number of ways. There is no
absolute need for a redirect. Everything can be
done in one form, or not -- your choice.
Cheers,
tedd
Yes. But since I don't want to display a success information + form fields,
but only the success
> Yes. But since I don't want to display a success information + form fields,
> but only the success information,
> I believe the only way we have to do this is by either use javascript and
> update a div or similar, or using only php, by redirecting to another page.
>
> Is this correct?
Whether o
Hello,
on 10/02/2009 05:23 AM kranthi said the following:
>>> That only works if the user clicks on that submit button. If the user
>>> hits the enter key in a text input, the form is submitted but the submit
>>> input variable is not set. That is why an hidden input is a safer solution.
>
> i do
Hello,
on 10/02/2009 05:25 AM kranthi said the following:
> and yes i forgot to mention... i avoid hidden form elements because
> they can be modified very easily and hence pose a security threat.
How can hidden field be changed in a way that submit buttons can't? I do
not see any security threa
Hello,
on 10/02/2009 07:11 AM kranthi said the following:
>>> You say you don't use hidden fields because they can be modified too
>>> easily, yet you say you check for the submit button? Which out of the
>>> two do you do, as last time I checked, modifying one form field is as
>>> easy as changin
On 10/2/09 10:24 AM, "tedd" wrote:
> At 1:55 PM +0530 10/2/09, kranthi wrote:
>> and yes i forgot to mention... i avoid hidden form elements because
>> they can be modified very easily and hence pose a security threat.
>
> That depends upon how sloppy you are in coding.
>
> NONE of my hidden va
At 7:11 PM +0100 10/2/09, MEM wrote:
I don't want to take another path. The hidden fields seems the way to go.
However, you gave me the example above, and I'm not understanding how can I
pass from your example: A multi-step form.
To what I was looking form: 1 step form with a success page that sh
At 9:42 AM -0400 10/3/09, Tom Worster wrote:
On 10/2/09 10:24 AM, "tedd" wrote:
At 1:55 PM +0530 10/2/09, kranthi wrote:
and yes i forgot to mention... i avoid hidden form elements because
they can be modified very easily and hence pose a security threat.
That depends upon how sloppy yo
On 10/2/09 10:06 AM, "MEM" wrote:
> I'm now understanding that even if the form is submitted to self, we can
> still use a redirect to a "success_message_page.php". However, we must do
> this redirect, AFTER the form has submitted to himself. It's the only thing
> that we have to pay attention he
Thanks a lot. To all.
For the moment, I'm with the redirect solution that others have pointed.
But after seen tedd example and watch Manuel videos, I'm starting to
understand how the hidden field solution work as well. Well... I'm
*starting* to understand I've not fully understand it yet, despit
On 10/4/09 9:25 AM, "MEM" wrote:
> Thanks a lot. To all.
> For the moment, I'm with the redirect solution that others have pointed.
>
> But after seen tedd example and watch Manuel videos, I'm starting to
> understand how the hidden field solution work as well. Well... I'm
> *starting* to unders
> i don't think so. if the user requests the page "a_form.php" then the
> server
> will normally execute the a_form.php script regardless whether the form
> was
> submitted or not.
>
> to display a blank form, the user probably requests a_form.php with the
> GET
> method and probably without any G
At 3:39 PM +0100 10/4/09, MEM wrote:
> i don't think so. if the user requests the page "a_form.php" then the
server
will normally execute the a_form.php script regardless whether the form
was
submitted or not.
to display a blank form, the user probably requests a_form.php with the
GET
m
On 10/4/09 10:39 AM, "MEM" wrote:
>> i don't think so. if the user requests the page "a_form.php" then the
>> server
>> will normally execute the a_form.php script regardless whether the form
>> was
>> submitted or not.
>>
>> to display a blank form, the user probably requests a_form.php with th
On 10/4/09 10:55 AM, "tedd" wrote:
> At 3:39 PM +0100 10/4/09, MEM wrote:
>>> i don't think so. if the user requests the page "a_form.php" then the
>>> server
>>> will normally execute the a_form.php script regardless whether the form
>>> was
>>> submitted or not.
>>>
>>> to display a blank
> i agree that it does seem a bit as though Márcio is in such a hurry to
> make
> something work that the tasks of learning and understanding the
> fundamentals
> are being left aside. while that's maybe understandable, it's a bit
> frustrating when we're trying to explain the fundamentals.
Thank
At 7:25 PM +0100 10/4/09, MEM wrote:
Unfortunately, I'm really REALLY on a rush.
I saw a bumper sticker the other day which read:
Humpty Dumpty was rushed
Cheers,
tedd
--
---
http://sperling.com http://ancientstones.com http://earthstones.com
--
PHP General Mailing List (http://www.
On Oct 2, 2009, at 3:00 AM, Manuel Lemos wrote:
Hello,
on 10/02/2009 04:41 AM kranthi said the following:
I try to avoid the use of hidden form elements as much as possible,
especially for tracking whether a user has submitted a form or not...
I use name="submit" for the submit button instead
Hello,
on 10/05/2009 03:02 PM Philip Thompson said the following:
>>> I try to avoid the use of hidden form elements as much as possible,
>>> especially for tracking whether a user has submitted a form or not...
>>>
>>> I use name="submit" for the submit button instead, that will pass the
>>> valu
On Oct 5, 2009, at 7:42 PM, Manuel Lemos wrote:
Hello,
on 10/05/2009 03:02 PM Philip Thompson said the following:
I try to avoid the use of hidden form elements as much as possible,
especially for tracking whether a user has submitted a form or
not...
I use name="submit" for the submit but
48 matches
Mail list logo
