Yes, the id on the form element.
If I remove that, then var_dump $_POST, I'm definitely getting my form
info, for example here's a var_dump of my latest search:
array(2) { ["search_field"]=> string(7) "leopard" ["search_button"]
=> string(2) "Go" }
But then I already knew that because without the id I can write
submitted form values to the server.
With the id on the form element, I'm just not getting my PHP executed
(which reads/writes the submitted form values to the server).
On Dec 15, 6:59 pm, Mike Alsup <[email protected]> wrote:
> > > You should never have an element with an id value that does not match
> > > its name value. Get that straightened out and you'll be fine.
>
> > That's not true at all. Do you have a reference for that?
>
> > The id attr. is solely for the DOM, while name is passed to the server.
>
> Yes, that's quite true. But using different values on the same
> element is a very bad idea.
>
> http://msdn.microsoft.com/en-us/library/ms536437(VS.85).aspx
>
> There are other issues in addition to the problems with getElementById
> mentioned in the linked article above. For example, both the id and
> name values on form controls are promoted to properties on the form
> element. This quickly leads to debugging nightmares.
>
> To the OP's question, I don't think I fully understand your question.
> Are you referring to the id on the form element?
