Databases
StackOverflow2013
Postsdbo
POBack Button Handle A Dynamic Form
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBack Button Handle A Dynamic Form
    primarykey
    data
    text
    <p>I have a form with an array of text fields. The user (through javascript) can add an arbitrary number of text fields to the form. After submitting the form and pressing the back button the form displays only with the fields that were on the original form when it was first rendered (any added text fields are lost). What is the best way to allow the back button to render the form in the state when the user submitted it? Any ideas are welcome, some things I've tried are:</p> <ul> <li>Put the form data in a cookie (this doesn't work great for a couple reasons but the biggest killer for me is that cookies are limited to 4K in size) </li> <li>Put the form data in a session</li> <li>Submit the form via AJAX and then manage the history</li> </ul> <p>Thanks for the help. I've posted a test form on my website at <a href="http://fishtale.org/formtest/f1.php" rel="nofollow noreferrer">http://fishtale.org/formtest/f1.php</a>. Also here is a simple form exhibiting the behavior I mentioned:</p> <pre><code>&lt;form action="f2.php" method="post"&gt; &lt;input type="text" name="text[]" id="text1"/&gt; &lt;input type="submit" name="saveaction" value="submit form" /&gt; &lt;/form&gt; &lt;a href="f2.php" id="add_element"&gt;Add Form Element&lt;/a&gt; &lt;script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.1/jquery.min.js" &gt;&lt;/script&gt; &lt;script type="text/javascript" &gt; $('#add_element').click(function (event) { event.preventDefault(); $('#text1').after('&lt;input type="text" name="text[]" /&gt;'); }); &lt;/script&gt; </code></pre> <p>This is similar to a question I posted a while ago, <a href="https://stackoverflow.com/questions/507793/best-way-for-back-button-to-leave-form-data">Best Way For Back Button To Leave Form Data</a>, however, this form's elements are modified by the user.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USBrian Fisher
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBack Button Handle A Dynamic Form
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBack Button Handle A Dynamic Form
      1. USBrian Fisher
      1. VTFavorite
    3. VO
      singulars
      1. POBack Button Handle A Dynamic Form
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHey Brian, are you opposed to using a temporary cookie to store the values. How many fields would your users generally add? I'll provide code if this even sounds remotely like a good solution.
      singulars
      1. POBack Button Handle A Dynamic Form
      1. USDoug Neiner
    2. COHey Doug, The users are creating a time card, so they can be adding quite a few elements on the order of 100. I'm not sure if I'm opposed to temporary cookies, if they work I'm all for them. I think they may cause issues for the other cookies if the total cookie size exceeds the 4K max. Thanks.
      singulars
      1. POBack Button Handle A Dynamic Form
      1. USBrian Fisher
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload