Hey Pete,


**
First, you should reply to the list - that way more people could see the links
you posted and out.
**
Oops, my mistake, I thought I did that. Will add a snip at the bottom of this email.

**
It looks like there may be a problem with the form tags - when I look at this
code I see
<form action="process_ecard1.php" method="post" name="mainform"></form>

That looks like you've closed your "mainform" before defining the inputs
**

can you tell me which line you see this? I did a search using that string on top and I couldnt find it... I even did a "form" search and still didnt find both of the form tags side by side..

Thanks again,
R

/// Snip of other mail with links ///
.....but looks like posting links is the best option so will do:

http://www.coinpass.com/test/step2.php (to run the script)
http://www.coinpass.com/test/step2.phps (View the source, its just a html file really)
All Javascript and CSS is in the "http://www.coinpass.com/test/scripts/" directory

The processing script just has
print_r($_REQUEST);
so its useless pointing you to the actual file source.

///// End snip///




__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Ryan S wrote:
> Hey Pete,
>
>
> **
> First, you should reply to the list - that way more people could see the links
> you posted and out.
> **
> Oops, my mistake, I thought I did that. Will add a snip at the bottom of this email.
>
> **
> It looks like there may be a problem with the form tags - when I look at this
> code I see
> <form action="process_ecard1.php" method="post" name="mainform"></form>
>
> That looks like you've closed your "mainform" before defining the inputs
> **
>
> can you tell me which line you see this? I did a search using that string on top and I couldnt find it... I even did a "form" search and still didnt find both of the form tags side by side..
>
> Thanks again,
> R
>
> /// Snip of other mail with links ///
> ....but looks like posting links is the best option so will do:
>
> http://www.coinpass.com/test/step2.php (to run the script)
> http://www.coinpass.com/test/step2.phps (View the source, its just a html file really)
> All Javascript and CSS is in the "http://www.coinpass.com/test/scripts/" directory
>
> The processing script just has
> print_r($_REQUEST);
> so its useless pointing you to the actual file source.
>
> ///// End snip///
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com

Ryan,

You did reply to the list - it appeared in a separate thread in my viewer, so my
bad.


OK, the version with <form ...></form> appeared when I used WebDeveloper toolbar
to view the *generated* source.

When I look at the source code as received by Firefox (which is what the regular
"View source" option does), the closing form-tag is where you expect.

i think I spotted a problem, however. Your original source code looks like it
has a spurious <tr> after the first recipient block.

I think you need to really check the nesting of your tags - try indenting stuff
to make the opening and closing tags line up and see if it gets out of line
somewhere.

Anyway, I suspect what is happening is that Firefox is treating the </form> as a
closing tag for the spurious </tr> and then implicitly closing the original
<form> tag with an empty form.

Your Javascript code also adds a spurious <tr> tag (line 17 of
dynamic_no_of_recipients2.js)

This is not really anything to do with PHP, of course...

--
Peter Ford, Developer phone: 01580 893333 fax: 01580 893399
Justcroft International Ltd. www.justcroft.com
Justcroft House, High Street, Staplehurst, Kent TN12 0AH United Kingdom
Registered in England and Wales: 2297906
Registered office: Stag Gates House, 63/64 The Avenue, Southampton SO17 1XS

Ryan S wrote:
> Hey Pete,
>
>
> **
> First, you should reply to the list - that way more people could see the links
> you posted and out.
> **
> Oops, my mistake, I thought I did that. Will add a snip at the bottom of this email.
>
> **
> It looks like there may be a problem with the form tags - when I look at this
> code I see
> <form action="process_ecard1.php" method="post" name="mainform"></form>
>
> That looks like you've closed your "mainform" before defining the inputs
> **
>
> can you tell me which line you see this? I did a search using that string on top and I couldnt find it... I even did a "form" search and still didnt find both of the form tags side by side..
>
> Thanks again,
> R

While we are on the topic of the <form...>...</form> tags, just a side note. It
is invalid HTML syntax to have any tag between your

<table><ILLEGAL><tr><ILLEGAL><td> ok here </td><ILLEGAL></tr><ILLEGAL></table>

As a note: the only legal tag that I know of that can be placed in between the
above tags is the <caption> tag. oh and the <thead>, <tbody>, and <tfoot> tags.

>
> /// Snip of other mail with links ///
> ....but looks like posting links is the best option so will do:
>
> http://www.coinpass.com/test/step2.php (to run the script)
> http://www.coinpass.com/test/step2.phps (View the source, its just a html file really)
> All Javascript and CSS is in the "http://www.coinpass.com/test/scripts/" directory
>
> The processing script just has
> print_r($_REQUEST);
> so its useless pointing you to the actual file source.
>
> ///// End snip///
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>


--
Jim Lucas

"Some men are born to greatness, some achieve greatness,
and some have greatness thrust upon them."

Twelfth Night, Act II, Scene V
by William Shakespeare

On Apr 9, 2008, at 11:09 AM, Jim Lucas wrote:
> Ryan S wrote:
>> Hey Pete,
>> **
>> First, you should reply to the list - that way more people could
>> see the links you posted and out.
>> **
>> Oops, my mistake, I thought I did that. Will add a snip at the
>> bottom of this email.
>> **
>> It looks like there may be a problem with the form tags - when I
>> look at this code I see
>> <form action="process_ecard1.php" method="post" name="mainform"></
>> form>
>> That looks like you've closed your "mainform" before defining the
>> inputs
>> **
>> can you tell me which line you see this? I did a search using that
>> string on top and I couldnt find it... I even did a "form" search
>> and still didnt find both of the form tags side by side..
>> Thanks again,
>> R
>
> While we are on the topic of the <form...>...</form> tags, just a
> side note. It is invalid HTML syntax to have any tag between your
>
> <table><ILLEGAL><tr><ILLEGAL><td> ok here </td><ILLEGAL></
> tr><ILLEGAL></table>

But something like:
<table><TR><TD>stuff here</TD></TR></table> is okay right? Just wanted
to double check since that's how all my stuff is and it works... but
just because it works doesn't mean it's right


--

Jason Pruim
Raoset Inc.
Technology Manager
MQC Specialist
3251 132nd ave
Holland, MI, 49424-9337
www.raoset.com
japruim@raoset.com

On Wed, Apr 9, 2008 at 11:18 AM, Jason Pruim <japruim@raoset.com> wrote:
> On Apr 9, 2008, at 11:09 AM, Jim Lucas wrote:
> >
> > While we are on the topic of the <form...>...</form> tags, just a side
> note. It is invalid HTML syntax to have any tag between your
> >
> > <table><ILLEGAL><tr><ILLEGAL><td> ok here
> </td><ILLEGAL></tr><ILLEGAL></table>
> >
>
> But something like:
> <table><TR><TD>stuff here</TD></TR></table> is okay right? Just wanted to
> double check since that's how all my stuff is and it works... but just
> because it works doesn't mean it's right

First day with the new eyes, Pruim, or decided to try to forget
and then re-learn English and HTML simultaneously? ;-P

Jim points out the correct XHTML layout, which shows "ok here"
(or, as you have it, "stuff here") between the td/TD tags. Case
doesn't matter, but does make it look sloppy. In addition, case
/should/ matter when matching closing to opening tags. For example,
try to avoid <td></TD> and mix-and-match versions thereof.

Keep in mind, no matter what, even the following will still Just
Work[tm]. It just won't validate when run through a nose-in-the-air
checker. Note the obvious messes, as well as some other issues. It's
ugly, but it works.

<Table>
<FORM method="post">
<!-- An example of an UGLY form! -->
<TR>
<input type="Hidden" name="field1" value="value1">
<td />
<textarea NAME="userfield1"><?=print_r($_SERVER);?></TextArea>
</tD>
</tr>
</table>
<input type="SUBMIT" value="GO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!" />
</form>

--
</Daniel P. Brown>
Ask me about:
Dedicated servers starting @ $59.99/mo., VPS starting @ $19.99/mo.,
and shared hosting starting @ $2.50/mo.
Unmanaged, managed, and fully-managed!

Daniel Brown wrote:
> On Wed, Apr 9, 2008 at 11:18 AM, Jason Pruim <japruim@raoset.com> wrote:
>> On Apr 9, 2008, at 11:09 AM, Jim Lucas wrote:
>>> While we are on the topic of the <form...>...</form> tags, just a side
>> note. It is invalid HTML syntax to have any tag between your
>>> <table><ILLEGAL><tr><ILLEGAL><td> ok here
>> </td><ILLEGAL></tr><ILLEGAL></table>
>> But something like:
>> <table><TR><TD>stuff here</TD></TR></table> is okay right? Just wanted to
>> double check since that's how all my stuff is and it works... but just
>> because it works doesn't mean it's right
>
> First day with the new eyes, Pruim, or decided to try to forget
> and then re-learn English and HTML simultaneously? ;-P
>
> Jim points out the correct XHTML layout, which shows "ok here"
> (or, as you have it, "stuff here") between the td/TD tags. Case
> doesn't matter, but does make it look sloppy. In addition, case
> /should/ matter when matching closing to opening tags. For example,
> try to avoid <td></TD> and mix-and-match versions thereof.
>
> Keep in mind, no matter what, even the following will still Just
> Work[tm]. It just won't validate when run through a nose-in-the-air
> checker. Note the obvious messes, as well as some other issues. It's
> ugly, but it works.
>
> <Table>
> <FORM method="post">
> <!-- An example of an UGLY form! -->
> <TR>
> <input type="Hidden" name="field1" value="value1">
> <td />
> <textarea NAME="userfield1"><?=print_r($_SERVER);?></TextArea>
> </tD>
> </tr>
> </table>
> <input type="SUBMIT" value="GO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!" />
> </form>
>

Yeah, if you used code like that IRL I would slap your hand!

--
Jim Lucas

"Some men are born to greatness, some achieve greatness,
and some have greatness thrust upon them."

Twelfth Night, Act II, Scene V
by William Shakespeare

On Apr 9, 2008, at 11:29 AM, Daniel Brown wrote:
> On Wed, Apr 9, 2008 at 11:18 AM, Jason Pruim <japruim@raoset.com>
> wrote:
>> On Apr 9, 2008, at 11:09 AM, Jim Lucas wrote:
>>>
>>> While we are on the topic of the <form...>...</form> tags, just a
>>> side
>> note. It is invalid HTML syntax to have any tag between your
>>>
>>> <table><ILLEGAL><tr><ILLEGAL><td> ok here
>> </td><ILLEGAL></tr><ILLEGAL></table>
>>>
>>
>> But something like:
>> <table><TR><TD>stuff here</TD></TR></table> is okay right? Just
>> wanted to
>> double check since that's how all my stuff is and it works... but
>> just
>> because it works doesn't mean it's right
>
> First day with the new eyes, Pruim, or decided to try to forget
> and then re-learn English and HTML simultaneously? ;-P

Both of little actually
>
>
> Jim points out the correct XHTML layout, which shows "ok here"
> (or, as you have it, "stuff here") between the td/TD tags. Case
> doesn't matter, but does make it look sloppy. In addition, case
> /should/ matter when matching closing to opening tags. For example,
> try to avoid <td></TD> and mix-and-match versions thereof.

I always used to type my HTML is lower case, but I've been trying to
get switched over to UPPERCASE to separate code from content.
>



--

Jason Pruim
Raoset Inc.
Technology Manager
MQC Specialist
3251 132nd ave
Holland, MI, 49424-9337
www.raoset.com
japruim@raoset.com

On Wed, Apr 9, 2008 at 12:21 PM, Jason Pruim <japruim@raoset.com> wrote:
> > Jim points out the correct XHTML layout, which shows "ok here"
> > (or, as you have it, "stuff here") between the td/TD tags. Case
> > doesn't matter, but does make it look sloppy. In addition, case
> > /should/ matter when matching closing to opening tags. For example,
> > try to avoid <td></TD> and mix-and-match versions thereof.
> >
>
> I always used to type my HTML is lower case, but I've been trying to get
> switched over to UPPERCASE to separate code from content.

You might as well switch back to lowercase, since that's part of the
XHTML 1.0 specs. Even if you don't use XHTML, consistent lowercase
will still work with the previous HTML standards and it prevents you
from having to fix a bunch of stuff if you someday find yourself
having to "upgrade" everything to XHTML for some reason in the future.

http://www.w3.org/TR/xhtml1/#h-4.2

Andrew