<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://www.webmaster-forums.net/crss/node/1039028" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title></title>
    <link>https://www.webmaster-forums.net/crss/node/1039028</link>
    <description></description>
    <language>en</language>
          <item>
    <title></title>
    <link>https://www.webmaster-forums.net/html-css-and-javascript/how-handle-multipage-forms#comment-1221841</link>
    <description> &lt;p&gt;When I have to do it, I use the &lt;a href=&quot;http://us.php.net/manual/en/ref.session.php&quot; class=&quot;bb-url&quot;&gt;$_SESSION&lt;/a&gt; variable.  Every time a page is submitted, I use the &lt;a href=&quot;http://us.php.net/manual/en/function.array-merge.php&quot; class=&quot;bb-url&quot;&gt;array_merge()&lt;/a&gt; function to merge $_POST with $_SESSION[&#039;form&#039;].  Then, when the last page is submitted, all data is inserted at once.  I don&#039;t like the idea of inserting the data into the DB page-by-page because you always have the people that bail out before submitting the last page and you have to worry about cleaning out half-completed forms.&lt;/p&gt;
&lt;p&gt;Also, if data is validated on every page, remember to validate &lt;strong&gt;all&lt;/strong&gt; data at the end even if it was validated before on previous pages.&lt;/p&gt;
 </description>
     <pubDate>Thu, 19 Jul 2007 04:40:45 +0000</pubDate>
 <dc:creator>pr0gr4mm3r</dc:creator>
 <guid isPermaLink="false">comment 1221841 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/html-css-and-javascript/how-handle-multipage-forms#comment-1221827</link>
    <description> &lt;blockquote class=&quot;bb-quote-body&quot;&gt;&lt;p&gt;&lt;strong&gt;brady.k;221826 wrote:&lt;/strong&gt; As forr using &quot;hidden&quot; fields, as opposed to PHP variables... that&#039;s generally a terrible idea for anything involving personal information.  Use them to keep track of what&#039;s being submitted if you want, but not the data itself.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;That&#039;s actually why I proposed simply using the first name and email address as the information being stored.  I can see the email address being personal, but a first name can not directly identify anyone (except maybe Prince or Cher...&lt;img src=&quot;https://www.webmaster-forums.net/misc/smileys/tongue.png&quot; title=&quot;Sticking out tongue&quot; alt=&quot;Sticking out tongue&quot; class=&quot;smiley-content&quot; /&gt;).  &lt;/p&gt;
&lt;p&gt;Anywho, it&#039;s simply a hypothetical situation, and perhaps, not even worth being discussed, but it was an event that popped in my head.&lt;/p&gt;
 </description>
     <pubDate>Thu, 19 Jul 2007 02:13:20 +0000</pubDate>
 <dc:creator>mscreashuns</dc:creator>
 <guid isPermaLink="false">comment 1221827 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/html-css-and-javascript/how-handle-multipage-forms#comment-1221826</link>
    <description> &lt;p&gt;Well, there&#039;s a few answers.&lt;/p&gt;
&lt;p&gt;The quick and easy one, in my mind, is that updating the MySQL as you go would be a better choice, if only because you don&#039;t have to track numerous variables across many pages.  Using sessions or cookies for something like that would be kind of overkill, I think, unless you&#039;re talking about a shopping cart.  And with the speed of MySQL, no-one would ever know.&lt;/p&gt;
&lt;p&gt;As for using &quot;hidden&quot; fields, as opposed to PHP variables... that&#039;s generally a terrible idea for anything involving personal information.  Use them to keep track of what&#039;s being submitted if you want, but not the data itself.&lt;/p&gt;
&lt;p&gt;The ultimate answer is....&lt;/p&gt;
&lt;p&gt;Don&#039;t do it.&lt;/p&gt;
&lt;p&gt;Either create a one-page form, or create a dynamic page.  If you create a dynamic page that uses AJAX, you then have the ability to process as you go (aka insert/update db rows)... but also without the page refreshes.  Or, you could have a one-page form with a bunch of portions hidden until certain fields or parameters are selected/filled out.&lt;/p&gt;
&lt;p&gt;I didn&#039;t directly answer your question...  but knowing more has never killed anyone, I guess...&lt;/p&gt;
 </description>
     <pubDate>Thu, 19 Jul 2007 02:08:32 +0000</pubDate>
 <dc:creator>brady.k</dc:creator>
 <guid isPermaLink="false">comment 1221826 at https://www.webmaster-forums.net</guid>
  </item>
  </channel>
</rss>
