IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Really scripting, but, internet as well
I've got a simple form:

[link|http://www.cpeonline.com/cpenew/Survey3-finalftp.htm|http://www.cpeonline...vey3-finalftp.htm]

No, I did not create the form, yes, I know the lack of radio buttons is just plain stupid, no, I will not be fixing it or the crappy variables names. I'll just get another one that I'll have to fix again and again.

That form feeds an ASP script, which packages up the variables and emails it to me (for now).

The script is essentially:
<%
txtMessage = "Survey results" & vbCrLf
txtMessage = txtMessage & "Title1 :" & Request.Form("Title1") & vbCrLf
txtMessage = txtMessage & "Title2 :" & Request.Form("Title2") & vbCrLf
txtMessage = txtMessage & "Title3 :" & Request.Form("Title3") & vbCrLf
txtMessage = txtMessage & "Title4 :" & Request.Form("Title4") & vbCrLf
...
(all the variables)
and then email via:
CDONTS.NewMail object.

The wierd part is none of the variable data gets filled in.
I get my email message, and it looks like this:

Survey results
Title1 :
Title2 :
Title3 :
...

I've done this before, it was straight forward.
But now it does not work.

Any hints?
New Submit type
The GET/PUT submit have different methods for variables that are sent as part of the URL vs. variables that are submitted:

    ' Submitted form parameters
    Request.Form("Title1")

    ' URL supplied parameters
    Request.QueryString("Title1")

Actually the better way to do it is:

    Request("Title1")

And let the interpreter figure how the parameter got sent.
New Same results
Thanks for trying.

Anything else?
New Jay has the correct answer
My first guesses never seem correct. Oh, that and you need the target to be an ASP file.

[edit: yes, i looked and it is an asp file. Tried the example on my local server and it works]
Expand Edited by ChrisR Jan. 1, 2005, 09:51:28 PM EST
New tidy has some suggestions:
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 32 column 137 - Warning: entity " " doesn't end in ';'
line 33 column 50 - Warning: entity " " doesn't end in ';'
line 34 column 50 - Warning: entity " " doesn't end in ';'
line 35 column 50 - Warning: entity " " doesn't end in ';'
line 41 column 138 - Warning: entity " " doesn't end in ';'
line 42 column 52 - Warning: entity " " doesn't end in ';'
line 43 column 50 - Warning: entity " " doesn't end in ';'
line 44 column 50 - Warning: entity " " doesn't end in ';'
line 49 column 137 - Warning: entity " " doesn't end in ';'
line 50 column 50 - Warning: entity " " doesn't end in ';'
line 51 column 50 - Warning: entity " " doesn't end in ';'
line 52 column 50 - Warning: entity " " doesn't end in ';'
line 59 column 54 - Warning: entity " " doesn't end in ';'
line 60 column 52 - Warning: entity " " doesn't end in ';'
line 61 column 52 - Warning: entity " " doesn't end in ';'
line 62 column 52 - Warning: entity " " doesn't end in ';'

line 110 column 10 - Warning: <input> missing '>' for end of tag
line 3 column 1 - Warning: inserting missing 'title' element
line 21 column 1 - Warning: <table> lacks "summary" attribute
line 72 column 1 - Warning: <table> proprietary attribute "height"
line 72 column 1 - Warning: <table> lacks "summary" attribute
line 84 column 1 - Warning: <table> proprietary attribute "height"
line 84 column 1 - Warning: <table> lacks "summary" attribute
line 95 column 1 - Warning: <table> proprietary attribute "height"
line 95 column 1 - Warning: <table> lacks "summary" attribute
line 111 column 2 - Warning: <br> proprietary attribute "size"
Info: Document content looks like HTML Proprietary
27 warnings, 0 errors were found!


The table summary attribute should be used to describe
the table structure. It is very helpful for people using
non-visual browsers. The scope and headers attributes for
table cells are useful for specifying which headers apply
to each table cell, enabling non-visual browsers to provide
a meaningful context for each cell.

For further advice on how to make your pages accessible
see [link|http://www.w3.org/WAI/GL|http://www.w3.org/WAI/GL]. You may also want to try
"[link|http://www.cast.org/bobby/|http://www.cast.org/bobby/]" which is a free Web-based
service for checking URLs for accessibility.

To learn more about HTML Tidy see [link|http://tidy.sourceforge.net|http://tidy.sourceforge.net]
Please send bug reports to html-tidy@w3.org
HTML and CSS specifications are available from [link|http://www.w3.org/|http://www.w3.org/]
Lobby your company to join W3C, see [link|http://www.w3.org/Consortium|http://www.w3.org/Consortium]


tidy will fix these automatically, but it may not fix your problem.

[edit] fixed inadvertent html tags
Alex

The trouble with the world is that the stupid are cocksure and the intelligent are full of doubt. -- Bertrand Russell
Expand Edited by a6l6e6x Jan. 2, 2005, 04:10:55 PM EST
New The only thing I see is the enctype
The only things I see at a quick glance is the enctype set to "text/plain". That isn't the default type, and may be screwing it up at either client or server.

value="on" is redundant on a checkbox also, but I don't so how that could be messing you up.

Jay
New The checkk on is throwing me as well
If it it one, shouldn;t I see check marks filled in already?
But I don't.
New Use the checked attribute
<input type='checkbox' name=title1' checked>

New value='on' just says the submit value is the string "on"
which is the default - which is why it's redundant
New I've fixed the missing ';' on the &nbsp entries
The guy giving me this crap is generating it in MS-Word.
New text/plain was it
All better.
Thanks.
New Ignore this
Edit: nevermind, I should have read down all the way before responding
~~~)-Steven----

"I want you to remember that no bastard ever won a war by dying for his country.
He won it by making the other poor dumb bastard die for his country..."

General George S. Patton
Expand Edited by Steven A S Jan. 5, 2005, 10:58:12 AM EST
     Really scripting, but, internet as well - (broomberg) - (11)
         Submit type - (ChrisR) - (3)
             Same results - (broomberg) - (1)
                 Jay has the correct answer - (ChrisR)
             tidy has some suggestions: - (a6l6e6x)
         The only thing I see is the enctype - (JayMehaffey) - (5)
             The checkk on is throwing me as well - (broomberg) - (2)
                 Use the checked attribute - (ChrisR) - (1)
                     value='on' just says the submit value is the string "on" - (ChrisR)
             I've fixed the missing ';' on the &nbsp entries - (broomberg)
             text/plain was it - (broomberg)
         Ignore this - (Steven A S)

Mmm... flame-roasted newbie...
141 ms