<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16788" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=267594919-03022009><FONT face=Arial
color=#0000ff size=2>The most compelling reason aside form being more
maintainable, is that drupal forms api implements cross-site scripting
vulnerability protections that may not have been taken care of in the original
code. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=267594919-03022009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=267594919-03022009><FONT face=Arial
color=#0000ff size=2>Dave</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> support-bounces@drupal.org
[mailto:support-bounces@drupal.org] <B>On Behalf Of </B>Shai
Gluskin<BR><B>Sent:</B> Tuesday, February 03, 2009 11:45 AM<BR><B>To:</B>
support@drupal.org<BR><B>Subject:</B> [support] HTML forms not Drupal's Forms
API -- Badness ExplanationNeeded<BR></FONT><BR></DIV>
<DIV></DIV>Gang,<BR><BR>I've red-flagged for a potential client (abandoned by
former Drupal developer) an event registration page on their site that uses an
html form to deliver some variables to a Paypal page. Looks like the code came
from a Paypal help page.<BR><BR>I'm proposing using a combination of the signup
and signup_pay modules to handle this functionality. I'd like to give the client
a little more detail on why it is bad to use regular html forms in addition to
"It's more stable," or "it's the Drupal way." On the "It's more stable"
argument, I need some more detail on why and what are some bad things that
can.<BR><BR>Any help would be most
appreciated.<BR><BR>Thanks,<BR><BR>Shai<BR></BODY></HTML>