W3C Validating Error in Form

attribute "WEBBOT-ACTION" error in form

[Polett]

Hello,
I'm trying to validate my site in the W3.org but keep getting an error on my "Join Us" page.

The error is: Line 53, column 108: there is no attribute "WEBBOT-ACTION"

The actual script on that page is:
<FORM METHOD="POST" action="--WEBBOT-SELF--" name="Membership" onSubmit="location.href='_derived/nortbots.htm';return false;" webbot-onSubmit>
<!--webbot bot="SaveResults" u-file="members.htm" s-format="HTML/BR" s-label-fields="TRUE" b-reverse-chronology="FALSE" u-file="members" s-format="TEXT/PRE" s-label-fields="TRUE" b-reverse-chronology="FALSE" b-email-label-fields="TRUE" b-email-subject-from-field="FALSE" s-email-subject="My Doamin, NEW MEMBER" s-builtin-fields="HTTP_USER_AGENT" u-confirmation-url="confirmation.html" s-email-format="TEXT/PRE" s-email-address="[e-mail]" startspan --><strong>[FrontPage Save Results Component]</strong><!--webbot bot="SaveResults" endspan i-checksum="6561" --><BLOCKQUOTE>
<hr>
<div align="center">
<BR>

Any help is GREATLY appreciated

[iamlost]

Much of MSFT Publisher/Frontpage code will not validate. See:

[w3.org ]

action = uri [CT]
This attribute specifies a form processing agent. User agent behavior for a value other than an HTTP URI is undefined.

Please note that your code is not "wrong" just "undefined". However "undefined" will never validate. It likely will work - at least if published/uploaded by Publisher/Frontpage to a server with the proper proprietary extensions, etc.

You may want to investigate:
[w3.org ]
For current w3c recommendations on writing HTML (4.01).

Many people use a proprietary WYSiWYG program but then open the code in a text editor to rewrite as needed to validate. Others hand code everything in the text editor. Whatever works.

<edit: added>
Sorry.

Welcome to WebmasterWorld, Polett!

[Polett]

So the only way to fix this is creating a CGI script?

[jimbeetle]

If you can live with the fact that you have one attribute that does not validate -- and you know the reason why -- then no, you don't have to fix it. If you need absolutely valid html, then yep, you'll have to go a different route.