Passing data from forms from one page to another
 

Hello,

Does anyone know how to submit forms from one page to another page? If you don' mind can someone explain how, or if they know a good tutorial, either of these would be great. Can this be done in javascript?

Thanks

Re: Passing data from forms from one page to another
 

I believe it's either done using cookies, or by passing (small quantities) of data in the url.

E.g. I use php to pass data on one of my sites: you create an image id number, e.g. 0000001. You link using www.mysite.com/pic.php?imgid=0000001

The second page then reads the variable imgid as having a value of 0000001. It makes a page in my templated style with 0000001.jpg in the middle, 0000001.txt included below it.

This means my one page produces up to a million image preview pages, all in my template.

If you can't get any help with it let me know and I'll see what I can suggest.

Re: Passing data from forms from one page to another
 

You can do it a variety of ways -- one being what DaveSW suggested. In PHP, at least, you don't need to pass it as a URL variable.

Forms using the POST method (which is... well.... yeah, duh)... can send variables to the next page, you just have to write the code to grab them. Easy enough to do. What language do you want to use?

What are you trying to accomplish -- do you have some starter code I can look at? I'd be glad to help.

Re: Passing data from forms from one page to another
 

Well I found an example from another page, but I want to do it in javascript, and here is the code that I got.
This is the form I am working with:

<form name="input" action="">

Username: 

<input type="text" name="user">

<input type="submit" value="Submit">

</form>

I don't know what action to use or if there is any other part that I need for javascript, and I don't know the code for the recieving end page.

Thanks

Re: Passing data from forms from one page to another
 

the said javascript that cooresponds to the submit button, takes on the form: document.formname.submit();

Re: Passing data from forms from one page to another
 

does that go in value
so:

value="document.formname.submit()"

or

does it go in action like this:
action="document.formname.submit()"

Thanks

Re: Passing data from forms from one page to another
 

I would have put it in a function... but you can put it as an action if you want....such as

<input type="button" value="hi" onClick="document.formname.submit();" />

or in a function.. because I like to test the form values with javascript BEFORE submitting it to the server-side.

function check_values()

{

     if (document.formname.sometextbox.value == "") {

          alert("How About A Value in sometextbox buddy!?")

          return;

     } else {

          document.formname.submit();

     }

}

Re: Passing data from forms from one page to another
 

I am not using a server, how do u submit using a cookie

Re: Passing data from forms from one page to another
 

Hi,
I hope its not too late to ask another related question on this. I am also trying to the same thing, passing data from one page to another, using javascript and html. From the replies in this post, I can send data from my input page. But after that I have to display all the sent data (username, address, location etc.) in the new page. How do I do that?
thanks

Re: Passing data from forms from one page to another
 

These are the fuctions you need. I suggest you make a file called cookie.js and include in your html file like this:

[HTML]<script type="text/javascript" src="cookie.js"></script>[/HTML]

and the javascript to place in the cookie.js file:

      //

      //  Cookie Functions -- "Night of the Living Cookie" Version (25-Jul-96)

      //

      //  Written by:  Bill Dortch, hIdaho Design <bdortch@hidaho.com>

      //  The following functions are released to the public domain.

      //

      //  This version takes a more aggressive approach to deleting

      //  cookies.  Previous versions set the expiration date to one

      //  millisecond prior to the current time; however, this method

      //  did not work in Netscape 2.02 (though it does in earlier and

      //  later versions), resulting in "zombie" cookies that would not

      //  die.  DeleteCookie now sets the expiration date to the earliest

      //  usable date (one second into 1970), and sets the cookie's value

      //  to null for good measure.

      //

      //  Also, this version adds optional path and domain parameters to

      //  the DeleteCookie function.  If you specify a path and/or domain

      //  when creating (setting) a cookie**, you must specify the same

      //  path/domain when deleting it, or deletion will not occur.

      //

      //  The FixCookieDate function must now be called explicitly to

      //  correct for the 2.x Mac date bug.  This function should be

      //  called *once* after a Date object is created and before it

      //  is passed (as an expiration date) to SetCookie.  Because the

      //  Mac date bug affects all dates, not just those passed to

      //  SetCookie, you might want to make it a habit to call

      //  FixCookieDate any time you create a new Date object:

      //

      //    var theDate = new Date();

      //    FixCookieDate (theDate);

      //

      //  Calling FixCookieDate has no effect on platforms other than

      //  the Mac, so there is no need to determine the user's platform

      //  prior to calling it.

      //

      //  This version also incorporates several minor coding improvements.

      //

      //  **Note that it is possible to set multiple cookies with the same

      //  name but different (nested) paths.  For example:

      //

      //    SetCookie ("color","red",null,"/outer");

      //    SetCookie ("color","blue",null,"/outer/inner");

      //

      //  However, GetCookie cannot distinguish between these and will return

      //  the first cookie that matches a given name.  It is therefore

      //  recommended that you *not* use the same name for cookies with

      //  different paths.  (Bear in mind that there is *always* a path

      //  associated with a cookie; if you don't explicitly specify one,

      //  the path of the setting document is used.)

      //  

      //  Revision History:

      //

      //    "Toss Your Cookies" Version (22-Mar-96)

      //      - Added FixCookieDate() function to correct for Mac date bug

      //

      //    "Second Helping" Version (21-Jan-96)

      //      - Added path, domain and secure parameters to SetCookie

      //      - Replaced home-rolled encode/decode functions with Netscape's

      //        new (then) escape and unescape functions

      //

      //    "Free Cookies" Version (December 95)

      //

      //

      //  For information on the significance of cookie parameters, 

      //  and on cookies in general, please refer to the official cookie

      //  spec, at:

      //

      //      http://www.netscape.com/newsref/std/cookie_spec.html    

      //

      //******************************************************************

      //

      // "Internal" function to return the decoded value of a cookie

      //

      function getCookieVal (offset) {

         var endstr = document.cookie.indexOf (";", offset);

         if (endstr == -1) {

            endstr = document.cookie.length;

         }

         return unescape(document.cookie.substring(offset, endstr));

      }



      //

      //  Function to correct for 2.x Mac date bug.  Call this function to

      //  fix a date object prior to passing it to SetCookie.

      //  IMPORTANT:  This function should only be called *once* for

      //  any given date object!  See example at the end of this document.

      //

      function FixCookieDate (date) {

         var base = new Date(0);

         var skew = base.getTime(); // dawn of (Unix) time - should be 0

         if (skew > 0) {  // Except on the Mac - ahead of its time

            date.setTime (date.getTime() - skew);

         }

      }



      //

      //  Function to return the value of the cookie specified by "name".

      //    name - String object containing the cookie name.

      //    returns - String object containing the cookie value, or null if

      //      the cookie does not exist.

      //

      function GetCookie (name) {

         var arg = name + "=";

         var alen = arg.length;

         var clen = document.cookie.length;

         var i = 0;

         while (i < clen) {

            var j = i + alen;

            if (document.cookie.substring(i, j) == arg) {

               return getCookieVal (j);

            }

            i = document.cookie.indexOf(" ", i) + 1;

            if (i == 0) {

               break;

            }

         }

         return null;

      }

 

      //

      //  Function to create or update a cookie.

      //    name - String object containing the cookie name.

      //    value - String object containing the cookie value.  May contain

      //      any valid string characters.

      //    [expires] - Date object containing the expiration data of the cookie.  If

      //      omitted or null, expires the cookie at the end of the current session.

      //    [path] - String object indicating the path for which the cookie is valid.

      //      If omitted or null, uses the path of the calling document.

      //    [domain] - String object indicating the domain for which the cookie is

      //      valid. If omitted or null, uses the domain of the calling document.

      //    [secure] - Boolean (true/false) value indicating whether cookie transmission

      //      requires a secure channel (HTTPS).  

      //

      //  The first two parameters are required.  The others, if supplied, must

      //  be passed in the order listed above.  To omit an unused optional field,

      //  use null as a place holder.  For example, to call SetCookie using name,

      //  value and path, you would code:

      //

      //      SetCookie ("myCookieName", "myCookieValue", null, "/");

      //

      //  Note that trailing omitted parameters do not require a placeholder.

      //

      //  To set a secure cookie for path "/myPath", that expires after the

      //  current session, you might code:

      //

      //      SetCookie (myCookieVar, cookieValueVar, null, "/myPath", null, true);

      //

      function SetCookie (name,value,expires,path,domain,secure) {

         document.cookie = name + "=" + escape (value) +

            ((expires) ? "; expires=" + expires.toGMTString() : "") +

            ((path) ? "; path=" + path : "") +

            ((domain) ? "; domain=" + domain : "") +

            ((secure) ? "; secure" : "");

      }

      

      //  Function to delete a cookie. (Sets expiration date to start of epoch)

      //    name -   String object containing the cookie name

      //    path -   String object containing the path of the cookie to delete.  This MUST

      //             be the same as the path used to create the cookie, or null/omitted if

      //             no path was specified when creating the cookie.

      //    domain - String object containing the domain of the cookie to delete.  This MUST

      //             be the same as the domain used to create the cookie, or null/omitted if

      //             no domain was specified when creating the cookie.

      //

      function DeleteCookie (name,path,domain) {

         if (GetCookie(name)) {

            document.cookie = name + "=" +

               ((path) ? "; path=" + path : "") +

               ((domain) ? "; domain=" + domain : "") +

               "; expires=Thu, 01-Jan-70 00:00:01 GMT";

         }

      }

This code has served me well :)

Dance