Form submit per javascript

[Victor]

Hi everybody!

I am experiencing a strange - at least for me - phenomen.
I have a func containing the following code :

alert (document.forms['photoUpload'].elements['photo_1'].value);

// document.forms['photoUpload'].submit();
document.photoU pload.submit();

This code works perfectly in the FF, but not in the IE. The alert
outputs the proper value of the element photo_1 and then the line with
submit() produces [objectError] - checked by means of try-catch and
displayed with alert(e) in the catch-block. This concerns the both
lines with the submit().

What could be a cause for this problem?

Victor

[Matt Kruse]

Victor wrote:

// document.forms['photoUpload'].submit();
document.photoU pload.submit();

The first form is preferred. Why is it commented out?

This code works perfectly in the FF, but not in the IE. The alert
outputs the proper value of the element photo_1 and then the line with
submit() produces [objectError]

First thing I would check is to make sure you don't have an input named
"submit".

--
Matt Kruse
http://www.JavascriptToolbox.com
http://www.AjaxToolbox.com

[Victor]

Matt Kruse schrieb:

Victor wrote:

// document.forms['photoUpload'].submit();
document.photoU pload.submit();

The first form is preferred. Why is it commented out?

Neither of the both wants to work here. The outcommented line has been
simply copied from the running code, never mind about it.

This code works perfectly in the FF, but not in the IE. The alert
outputs the proper value of the element photo_1 and then the line with
submit() produces [objectError]

First thing I would check is to make sure you don't have an input named
"submit".

No, I don't !

However, I have discovered that the problem gets eliminated when I try
to upload a different form rather than the 'photoUpload', which has
(!!!!) encode='multipa rt/form-data'. Can this be the real source of the
problem? If yes, then how to fix it? And why does it work in the FF?

Regards
Victor

[Malkavian]

"Victor" <bi******@chefm ail.dewrote in message
news:11******** **************@ f1g2000cwa.goog legroups.com...

Hi everybody!

I am experiencing a strange - at least for me - phenomen.
I have a func containing the following code :

alert (document.forms['photoUpload'].elements['photo_1'].value);

// document.forms['photoUpload'].submit();
document.photoU pload.submit();

This code works perfectly in the FF, but not in the IE. The alert
outputs the proper value of the element photo_1 and then the line with
submit() produces [objectError] - checked by means of try-catch and
displayed with alert(e) in the catch-block. This concerns the both
lines with the submit().

What could be a cause for this problem?

Victor

Why do you have "document.f orms['photoUpload'].elements['photo_1'].value" in
the alert but "document.photo Upload"
when you call the submit function? perhaps if you had "document.photo Upload"
in the alert too or
document.forms['photoUpload'].elements['photo_1'].submit, you may get a
different result.

HTH

>

[Matt Kruse]

Victor wrote:

However, I have discovered that the problem gets eliminated when I try
to upload a different form rather than the 'photoUpload', which has
(!!!!) encode='multipa rt/form-data'. Can this be the real source of
the problem?

I don't know.

I would take these steps:
1. Try submitting the form manually, without javascript
2. Try taking elements out of the form until it works, then figure out which
piece made it break
3. Have a non-script fall-back, so even in the event of errors like this,
the form would still get submitted

--
Matt Kruse
http://www.JavascriptToolbox.com
http://www.AjaxToolbox.com

[Victor]

Why do you have "document.f orms['photoUpload'].elements['photo_1'].value" in

the alert but "document.photo Upload" when you call the submit function? if you
had perhaps "document.photo Upload" in the alert too or
document.forms['photoUpload'].elements['photo_1'].submit, you may get a
different result.

I did try it with the 'document.forms['photoUpload']... ' in the alert
and with the 'document.photo Upload.submit() ' without any different
result...

Victor

[Bart Van der Donck]

Victor wrote:

I am experiencing a strange - at least for me - phenomen.
I have a func containing the following code :

alert (document.forms['photoUpload'].elements['photo_1'].value);

// document.forms['photoUpload'].submit();
document.photoU pload.submit();

This code works perfectly in the FF, but not in the IE. The alert
outputs the proper value of the element photo_1 and then the line with
submit() produces [objectError] - checked by means of try-catch and
displayed with alert(e) in the catch-block. This concerns the both
lines with the submit().

What could be a cause for this problem?

I might have reconstructed your problem:

<script type="text/javascript">
function sV() {
alert (document.forms['photoUpload'].elements['photo_1'].value)
document.photoU pload.submit()
}
</script>
<form method="post" action="script. php" id="photoUpload ">
<input type="file" name="photo_1">
<input type="button" value="click me" onClick="sV();" >
</form>

IE says "document.photo Upload is empty or no object".
FF says "document.photo Upload has no properties".

There are a number of things that are not good in this kind of code.

Better:

<form method="post" action="script. php" name="photoUplo ad"
enctype="multip art/form-data" onSubmit="
alert(document. forms['photoUpload'].elements['photo_1'].value)">
<input type="file" name="photo_1">
<input type="submit" value="click me">
</form>

Is the alert only meant for debugging purposes ? Then the
onSubmit-handler can be left out.

--
Bart

[Bart Van der Donck]

Victor wrote:

[...]
However, I have discovered that the problem gets eliminated when I try
to upload a different form rather than the 'photoUpload', which has
(!!!!) encode='multipa rt/form-data'. Can this be the real source of the
problem? If yes, then how to fix it? And why does it work in the FF?

The right syntax is

enctype="multip art/form-data"

and not

encode='multipa rt/form-data'

AFAIK, this should normally not affect the javascript. But it's
necessary to add it for other reasons (to be technical, so that your
parsing program - e.g. PHP, ASP... - knows that the POST-request
consists of multiple parts divided by a defined separator).

--
Bart

[Bart Van der Donck]

Malkavian wrote:

"Victor" <bi******@chefm ail.dewrote in message

>alert (document.forms['photoUpload'].elements['photo_1'].value);
// document.forms['photoUpload'].submit();
document.photo Upload.submit() ;

Why do you have "document.f orms['photoUpload'].elements['photo_1'].value" in
the alert but "document.photo Upload" when you call the submit function?
perhaps if you had "document.photo Upload" in the alert too or
document.forms.['photoUpload'].elements['photo_1'].submit, you may get a
different result.

You can't do

document.forms['photoUpload'].elements['photo_1'].submit()

Perhaps you meant

document.forms['photoUpload'].submit()

The latter is a difference compared to document.photoU pload.submit()
if one uses id="photoUpload " inside the <form>-tag. In my experience
I prefer name="photoUplo ad" . Maybe that's just a habit.

--
Bart

[Malkavian]

"Victor" <bi******@chefm ail.dewrote in message
news:11******** *************@7 9g2000cws.googl egroups.com...

>Why do you have "document.f orms['photoUpload'].elements['photo_1'].value"
in
the alert but "document.photo Upload" when you call the submit function?
if you
had perhaps "document.photo Upload" in the alert too or
document.for ms['photoUpload'].elements['photo_1'].submit, you may get a
different result.

I did try it with the 'document.forms['photoUpload']... ' in the alert
and with the 'document.photo Upload.submit() ' without any different
result...

Victor

I wasn't being picky. It's just that mixing name conventions causes a lot
of headaches.