submit form...created with php

[Bruce Duncan]

I know this isn't a php group but I was wondering if my problem is with my
javascript in my php code. I'm debugging someone else's code and I can't
figure out why this form won't submit.

This code doesn't do anything:
<?PHP
$var1 = "http://localhost/php/index.php";
$varx = "bruce";
echo "<form name='formx3' method='post'>< input type='text'><in put
type=button value=go onclick=documen t.formx3.action ='".$var1."';
document.formx3 .submit();></form>";
?>

This code works, but I want to know why the above code doesn't.
<?PHP
$var1 = "http://localhost/php/index.php";
$varx = "bruce";
echo "<form name='formx2' action='".$var1 ."'><input type='text'><in put
type=button value=go onclick=documen t.formx2.submit ();></form>";
?>

It seems awful weird to even try to assign the forms action and then submit
it all in the onclick event...are you allowed to do this in Javascript?

Thanks in advance...
-Bruce

[kaeli]

In article <10************ *@corp.supernew s.com>,
bruce~w~duncan@ ~hotmail.com enlightened us with...

I know this isn't a php group but I was wondering if my problem is with my
javascript in my php code. I'm debugging someone else's code and I can't
figure out why this form won't submit.

When you are debugging a server-side app and think it's the client-side
script, your best bet is to view the html source of the rendered doc to
see if you got what you thought you should get. I've cought many an
eaten quote that way. ;)

It isn't working because you are missing quotes that are required for
compound onClick.
This code doesn't do anything:
<?PHP
$var1 = "http://localhost/php/index.php";
$varx = "bruce";
echo "<form name='formx3' method='post'>< input type='text'><in put
type=button value=go onclick=documen t.formx3.action ='".$var1."';
document.formx3 .submit();></form>";
?>
The onClick, rendered (view->source), should look like this.
onclick="docume nt.formx3.actio n='someAction'; document.formx3 .submit();">

Note the double quotes that you don't have because your PHP would eat
them. I don't remember the exact way to escape double quotes in PHP, but
assuming it is a backslash, it would look like this in PHP.

echo "<form name='formx3' method='post'>< input type='text'><in put
type=button value=go onclick=\"docum ent.formx3.acti on='".$var1."';
document.formx3 .submit();\"></form>";

It seems awful weird to even try to assign the forms action and then submit
it all in the onclick event...are you allowed to do this in Javascript?

Yup.
Most of us put compound actions in functions and call those, though, for
ease of modification later.
--
--
~kaeli~
You feel stuck with your debt if you can't budge it.
http://www.ipwebdesign.net/wildAtHeart
http://www.ipwebdesign.net/kaelisSpace

[Thomas 'PointedEars' Lahn]

kaeli wrote:

Note the double quotes that you don't have because your PHP would eat
them. I don't remember the exact way to escape double quotes in PHP, but
assuming it is a backslash, it would look like this in PHP.

echo "<form name='formx3' method='post'>< input type='text'><in put
type=button value=go onclick=\"docum ent.formx3.acti on='".$var1."';
document.formx3 .submit();\"></form>";

Both from a J(ava)Script and a PHP hackers point of view, this is a
Bad Thing. As for PHP: Double quotes enforce expansion of variable
references, so if there are none within the string they are highly
inefficient. And as for J(ava)Script, I don't see the necessity of
using (here) error-prone client-side scripting at all. Consider
this instead:

<?php
...
?>
<form action="<?php echo $var1; ?>" name="formx3" method="post">
<input>
<input
type="submit"
value="go">
</form>
<?php
...
?>
PointedEars

[Hywel]

In article <10************ *@corp.supernew s.com>, Bruce Duncan says...

I know this isn't a php group but I was wondering if my problem is with my
javascript in my php code. I'm debugging someone else's code and I can't
figure out why this form won't submit.

This code doesn't do anything:
<?PHP
$var1 = "http://localhost/php/index.php";
$varx = "bruce";
echo "<form name='formx3' method='post'>< input type='text'><in put
type=button value=go onclick=documen t.formx3.action ='".$var1."';
document.formx3 .submit();></form>";
?>

This code works, but I want to know why the above code doesn't.

It's probably because by the time it gets to the browser it's
incorrectly formed.

Your code outputs this as the onclick:
onclick = document.formx3 .action='someth ing'; document.formx3 .submit();

It should be something like this:
onclick = "document.formx 3.action='somet hing'; document.formx3 .submit()"

--
Hywel I do not eat quiche
http://kibo.org.uk/
http://kibo.org.uk/mfaq.php

[Dominique]

try as follows
<?PHP
$var1 = "http://localhost/php/index.php";
$varx = "bruce";
echo "<form name='formx3' method='post'>< input type='text'><in put
type=button value=go document.formx3 .action='".$var 1."';
onclick=documen t.formx3.submit ();></form>";
?>
the action must be defined before onclick I think
i have not tried myself
bye
--
Ce message a ete poste via la plateforme Web club-Internet.fr
This message has been posted by the Web platform club-Internet.fr

http://forums.club-internet.fr/

[Thomas 'PointedEars' Lahn]

Dominique wrote:

try as follows
<?PHP
$var1 = "http://localhost/php/index.php";
$varx = "bruce";
echo "<form name='formx3' method='post'>< input type='text'><in put
type=button value=go document.formx3 .action='".$var 1."';
onclick=documen t.formx3.submit ();></form>";
?>
the action must be defined before onclick I think

Correct, a "form" element without a defined "action" attribute is invalid
HTML. But AFAIS there is no client-side J(ava)Script required at all.
PointedEars

[MJ]

> the action must be defined before onclick I think

i have not tried myself

Actually, that's not true. I often define the action (based on conditions)
after the onclick. However, usually I use a function like:

<script>
function Submit_form(){
if
(document.form. category.option s[document.form.c ategory.selecte dIndex].value
== "option1"){
document.form.a ction = "whatever1.php" ; // Define the action
document.form.s ubmit(); // Submit the page
return true;
} else if
(document.form. category.option s[document.form.c ategory.selecte dIndex].value
== "option2"){
document.formSe arch.action = "whatever2.php" ;
document.formSe arch.submit(); // Submit the page
return true;
} // and so on...
}
</script>

<input name="Search" type="button" id="Search" value="Search"
onClick="return Submit_form();" >

Works like a charm. I think the original poster's problem was improperly
formated code (lack of proper quotes). His onclick code was:

onclick=documen t.formx3.action ='".$var1."'; document.formx3 .submit();

Should have been:

onclick=\"docum ent.formx3.acti on='".$var1."'; document.formx3 .submit();\"

the quotes are escaped for PHP.

[Thomas 'PointedEars' Lahn]

MJ wrote:

the action must be defined before onclick I think
i have not tried myself

Actually, that's not true. I often define the action
(based on conditions) after the onclick. [...]

So you are creating invalid HTML and/or create forms that are useless for
users without client-side J(ava)Script and will malfunction for some with
client-side J(ava)Script (as the "action" is either not changed or not
changed fast enough).
PointedEars

[MJ]

> So you are creating invalid HTML and/or create forms that are useless for

users without client-side J(ava)Script and will malfunction for some with
client-side J(ava)Script (as the "action" is either not changed or not
changed fast enough).
PointedEars

It's only invalid HTML under outdated W3C standards written 7 years ago.
All versions from the past four years of the most popular browsers (IE,
Netscape, Opera, Mozilla) support doing this. I have never heard of any
sort of "malfunctio n" on the client side. I know several extremely high
traffic web sites that use similar functions.

Who doesn't have client-side Javascript these days? I'm sure less than one
half of one percent of all users. If they have Javascript turned off,
that's their tough luck. If their systems don't support Javascript, they
need to update their computers. My sites aren't intended for people with
386's running Windows 3.1.

[Lasse Reichstein Nielsen]

"MJ" <no*****@thank. you> writes:

Who doesn't have client-side Javascript these days?
Statistics differ. They usually put the number at, or just above, 10%
of users. I see now that TheCounter.com has dropped sharply to around
5% at the beginning of the year, suggesting they changed their method
of disvocering Javascript availability. We still don't know what that
method is. Statistics are ... well, statistics (as in "lies, damn
lies, and ..."). It's also all we have.
I'm sure less than one half of one percent of all users.
Based on intuition or any actual research?
If they have Javascript turned off, that's their tough luck.
Not if it's a commercial site. Then it's the competition's luck. Or
the ADA (or similar other-nationality legislation) litigation lawyers'
luck
If their systems don't support Javascript, they need to update their
computers.
Their handheld computers or mobile phones might not be upgradeable.
They are also likely to be more current than any version of Internet
Explorer.
My sites aren't intended for people with 386's running Windows 3.1.

That's your decission. Not a decission I would expect from a competent
web developer, though, as it doesn't take that much extra work to make
pages *usable* without Javascript. After all, the most important part
of a page *is* the content.

/L
--
Lasse Reichstein Nielsen - lr*@hotpop.com
DHTML Death Colors: <URL:http://www.infimum.dk/HTML/rasterTriangleD OM.html>
'Faith without judgement merely degrades the spirit divine.'