Re: Self-Process php forms or not?

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 changing any other! > I completely agree with you. changing submit text is as easy as > changing hidden fields, but its less likely for a user to modify a > submit button as compared to a hidden field. moreover it just reduces > my typing load. (This is just my practice) How come an user can modify a hidden field is more likely to change submit button? I don't think an average user will modify anything at all. >>> Also worth noting, you can only successfully check for the name="submit" >>> value if there is only one submit button in your form, as that is then >>> the default (and only) submit that the form can use, so it uses that. If >>> you have more than one submit button (and this includes image input >>> elements) then using the keyboard will use the first submit field it >>> finds I believe. > Cant agree with you on this though. as far as i know using name="" > (names of the two buttons may/may not be unique) is the only way to > track form submission for forms with multiple submit buttons. Please > point out if you think otherwise As everbody has been telling you, if you check an hidden field it will work regardless whether the user clicked on a button or hit enter on a text input. With multiple buttons there is no way (except for using some Javascript) to tell whether it was clicked a button or the user hit enter in a text input. -- Regards, Manuel Lemos Find and post PHP jobs http://www.phpclasses.org/jobs/ PHP Classes - Free ready to use OOP components written in PHP http://www.phpclasses.org/