I'm in the process of looking that up now, some say it's a security issue, but no one seems to give a detailed explanation... I have simple code that posts the form to itself validates or displays errors if needed. It all works fine except that it requires selfposting; but the code is good. THX, D!J!X! _____ From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of qubit Sent: Saturday, May 29, 2010 12:52 AM To: programmingblind@xxxxxxxxxxxxx Subject: Re: PHP Forms And self posting Hi djx -- I did a form that pretty much put everything in one php file which was invoked as the action for whatever forms were on the page, so it could fill in the values. It worked well for my purposes, but the logic was a bit harry and the code kind of unnatural. I think it would have been better to pull apart the php and not do it all on onne page, but that being said, I didn't want to copy the common code for each of the pages. I am curious: What are the pros and cons of writing a page that way (calling itself)? Just wondering. Happy hacking. --le ----- Original Message ----- From: D!J!X! <mailto:megamansuperior@xxxxxxxxxxx> To: programmingblind@xxxxxxxxxxxxx Sent: Friday, May 28, 2010 11:01 PM Subject: PHP Forms And self posting Hey guys, i'm finishing up a site here and was just wondering, i've been reading online and it seems that some people strongly suggest against having php forms post back to themselves for error displaying and correction and processing. I can sort of understand why, but then again it seems that a lot of people are using it and recommend it, w3c included. Does anybody have any comments/opinions they can share that would help me shed some light on this matter? Self posting would make my life easier, but i have a solution that separates processing from the actual form page, except that there's a bit of code involved to redisplay the form with values filled in, error messages displayed etc. Any thoughts, comments, articles on the topic? THX, D!J!X!