eVow.com, a leading online dating site for singles looking for long term relationships ...

evow.com
  • Domain Name
    evow.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #25465
  • Page Size
    32 KB
  • Ip Address
    199.182.216.175
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 1 JPG, 12 PNG

Website Meta Analysis

  • Title
    eVow Online Dating Site – For Relationships
  • Meta Keyword
    online dating, singles, dating, personals, matchmaker, matchmaking, love, evow, dating site, evow.com, free personals, christian singles, black singles, asian singles, jewish singles, local singles
  • Meta Description
    eVow.com, a leading online dating site for singles looking for long term relationships

Technical Analysis

  • Webserver
    Microsoft-IIS/8.0
  • Ip Address
    199.182.216.175
  • Domain Age
    13 Years, 8 Months, 26 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from evow.com.

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/8.0
  • x-aspnet-version: 4.0.30319
  • x-powered-by: ASP.NET
  • date: Thu, 12 Sep 2013 05:56:14 GMT
  • content-length: 8551
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Plentyoffish Media Inc
555 Hastings Street West
Suite 2625
Vancouver, British Columbia V6B4N5
Canada
Domain Domain Name: EVOW.COM
Created: 28-Dec-99
Expires: 28-Dec-17
Updated: 26-Sep-11
Administrative Contact:
Frind, Markus email
Plentyoffish Media Inc
2625 555 west hastings street
Vancouver, British Columbia v6b4n5
Canada
+1.6046922542 Fax -
Technical Contact:
Frind, Markus email
Plentyoffish Media Inc
2625 555 west hastings street
Vancouver, British Columbia v6b4n5
Canada
+1.6046922542 Fax -
Name Servers:
USW4.AKAM.NET
USW1.AKAM.NET
USE5.AKAM.NET
NS1-177.AKAM.NET
NS1-131.AKAM.NET
EUR5.AKAM.NET
ASIA2.AKAM.NET

IP 199.182.216.175 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 199.182.216.175

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 144 Errors
  • 22 Warnings
Ratio Text/Html
  • 0.5414288766136661
Message Error
  • Error Line 3, Column 109: DTD did not contain element declaration for document type name
    …/DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

    A DOCTYPE declares the version of the language used, as well as what the root (top) element of your document will be. For example, if the top element of your document is <html>, the DOCTYPE declaration will look like: "<!DOCTYPE html".

    In most cases, it is safer not to type or edit the DOCTYPE declaration at all, and preferable to let a tool include it, or copy and paste it from a trusted list of DTDs.

  • Error Line 4, Column 43: document type does not allow element "html" here
    <html xmlns="http://www.w3.org/1999/xhtml">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 12, Column 18: there is no attribute "HTTP-EQUIV"
    <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 12, Column 42: there is no attribute "CONTENT"
    <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 12, Column 52: element "META" undefined
    <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 13, Column 45: element "META" undefined
    <META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 15, Column 64: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="icon" href="Images/favicon.ico" type="image/x-icon">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 15, Column 1: start tag was here
    <link rel="icon" href="Images/favicon.ico" type="image/x-icon">
  • Warning Line 35, Column 28: character "<" is the first character of a delimiter but occurred as data
            if (now.getHours() < 10) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 43, Column 30: character "<" is the first character of a delimiter but occurred as data
            if (now.getMinutes() < 10) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 53, Column 73: cannot generate system identifier for general entity "args"
    …X_Common.ashx?fnName=validateUserName&args=' + name.value, validateUserNameHan…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 53, Column 73: general entity "args" not defined and no default entity
    …X_Common.ashx?fnName=validateUserName&args=' + name.value, validateUserNameHan…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 53, Column 77: reference not terminated by REFC delimiter
    …mmon.ashx?fnName=validateUserName&args=' + name.value, validateUserNameHandler…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 53, Column 77: reference to entity "args" for which no system identifier could be generated
    …mmon.ashx?fnName=validateUserName&args=' + name.value, validateUserNameHandler…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 53, Column 72: entity was defined here
    …AX_Common.ashx?fnName=validateUserName&args=' + name.value, validateUserNameHa…
  • Error Line 292, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 13, Column 1: start tag was here
    <META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">
  • Error Line 292, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 12, Column 1: start tag was here
    <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">
  • Error Line 301, Column 72: there is no attribute "align"
    …Images/landing/new_logo_v2.png" align="middle" style="width: 170px; height: au…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 301, Column 136: required attribute "alt" not specified
    …ng" align="middle" style="width: 170px; height: auto; margin-right:25px" /></a>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 302, Column 7: element "stong" undefined
    <stong><i>Already a member?</i></strong>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 302, Column 40: end tag for element "strong" which is not open
    <stong><i>Already a member?</i></strong>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 303, Column 6: end tag for "stong" omitted, but OMITTAG NO was specified
    </div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 302, Column 1: start tag was here
    <stong><i>Already a member?</i></strong>
  • Error Line 317, Column 8: element "center" undefined
    <center>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 319, Column 13: there is no attribute "color"
    <font color="green">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A dating site for…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 319, Column 20: element "font" undefined
    <font color="green">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A dating site for…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 320, Column 27: there is no attribute "style"
    <font color="green" style="font-size:14px"></font>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 320, Column 43: element "font" undefined
    <font color="green" style="font-size:14px"></font>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 323, Column 77: required attribute "alt" not specified
    … style="float:right"><img src="Images/reg_couple_v2.jpg" width="330px" /></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 333, Column 20: character "<" is the first character of a delimiter but occurred as data
    if (now.getHours() < 10) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 341, Column 22: character "<" is the first character of a delimiter but occurred as data
    if (now.getMinutes() < 10) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 348, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 348, Column 29: character "\" is not allowed in the value of attribute "type"
    document.write('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 348, Column 29: value of attribute "type" cannot be "\'hidden\'"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    document.write('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 348, Column 46: an attribute value must be a literal unless it contains only name characters
    …t.write('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=\'time…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 348, Column 50: character "+" not allowed in attribute specification list
    …ite('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=\'time\'/>…
  • Error Line 348, Column 50: document type does not allow element "input" here
    …ite('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=\'time\'/>…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 348, Column 51: end tag for "input" omitted, but OMITTAG NO was specified
    …te('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=\'time\'/>'…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 348, Column 17: start tag was here
    document.write('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=…
  • Error Line 351, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 351, Column 29: character "\" is not allowed in the value of attribute "type"
    document.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 351, Column 29: value of attribute "type" cannot be "\'hidden\'"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    document.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 351, Column 46: an attribute value must be a literal unless it contains only name characters
    …ment.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/>');

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 351, Column 50: character "+" not allowed in attribute specification list
    …ment.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/>');
  • Error Line 351, Column 50: document type does not allow element "input" here
    …ment.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 351, Column 51: end tag for "input" omitted, but OMITTAG NO was specified
    …ment.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/>');

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 351, Column 17: start tag was here
    document.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/…
  • Error Line 363, Column 5: end tag for "tr" which is not finished
    </tr>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 369, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <input name="lrikkula"  maxlength=25 id="lrikkula" class="tb" type="text" value…
  • Error Line 372, Column 15: there is no attribute "name"
    <td><img name="confirmation_Username" id="confirmation_username" alt="tick" src…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 379, Column 117: character "&" is the first character of a delimiter but occurred as data
    …r="if (registrationValid.vEmpty(this) && registrationValid.vPassword(this, 0x0…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 379, Column 118: character "&" is the first character of a delimiter but occurred as data
    …="if (registrationValid.vEmpty(this) && registrationValid.vPassword(this, 0x00…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 390, Column 44: character "&" is the first character of a delimiter but occurred as data
    …r= "if(registrationValid.vEmpty(this) && registrationValid.vPassword(this, 0x0…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 390, Column 45: character "&" is the first character of a delimiter but occurred as data
    …= "if(registrationValid.vEmpty(this) && registrationValid.vPassword(this, 0x00…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 390, Column 93: character "&" is the first character of a delimiter but occurred as data
    …tionValid.vPassword(this, 0x00000005) && registrationValid.vValMatch(this, $(v…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 390, Column 94: character "&" is the first character of a delimiter but occurred as data
    …ionValid.vPassword(this, 0x00000005) && registrationValid.vValMatch(this, $(vk…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 398, Column 100: character "&" is the first character of a delimiter but occurred as data
    …"if(registrationValid.vSelected(this) && registrationValid.vSelected($('seekin…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 398, Column 101: character "&" is the first character of a delimiter but occurred as data
    …if(registrationValid.vSelected(this) && registrationValid.vSelected($('seeking…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 399, Column 18: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    <option selected value="-1">Select</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Warning Line 404, Column 104: character "&" is the first character of a delimiter but occurred as data
    …"if(registrationValid.vSelected(this) && registrationValid.vSelected($('gender…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 404, Column 105: character "&" is the first character of a delimiter but occurred as data
    …if(registrationValid.vSelected(this) && registrationValid.vSelected($('gender'…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 405, Column 18: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    <option selected value="-1">Select</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 418, Column 21: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    <option  selected   value="-1">Month</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 433, Column 20: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    <option  selected  value="-1">Day</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 467, Column 20: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    <option  selected  value="-1">Year</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Warning Line 504, Column 112: character "&" is the first character of a delimiter but occurred as data
    …ur="if(registrationValid.vEmpty(this) && registrationValid.vEmail(this)) showC…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 504, Column 113: character "&" is the first character of a delimiter but occurred as data
    …r="if(registrationValid.vEmpty(this) && registrationValid.vEmail(this)) showCo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 515, Column 46: character "&" is the first character of a delimiter but occurred as data
    … " if (registrationValid.vEmpty(this) && registrationValid.vEmail(this) && reg…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 515, Column 47: character "&" is the first character of a delimiter but occurred as data
    …" if (registrationValid.vEmpty(this) && registrationValid.vEmail(this) && regi…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 515, Column 80: character "&" is the first character of a delimiter but occurred as data
    …is) && registrationValid.vEmail(this) && registrationValid.vValMatch(this, $(v…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 515, Column 81: character "&" is the first character of a delimiter but occurred as data
    …s) && registrationValid.vEmail(this) && registrationValid.vValMatch(this, $(vi…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 521, Column 12: there is no attribute "height"
    <td height="25" colspan="3" align="left" style="padding-left: 30px;font-size: 1…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 523, Column 44: there is no attribute "target"
    …ee to the <a href="terms.aspx" target="_blank"> Terms &amp; Conditions of eVow…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 528, Column 73: "img" is not a member of a group specified for any attribute
    …gin-top:40px"><input type="image" img src="Images/create_profile_v2.jpg" name=…
  • Error Line 528, Column 128: there is no attribute "width"
    …e_profile_v2.jpg" name="Submit" width="240px" style="margin-bottom:60px"/></di…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 539, Column 138: required attribute "alt" not specified
    … margin-left: 10px"><img src="Images/couples_row_v2.jpg" width="230px" /></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 540, Column 10: there is no attribute "align"
    <p align="left">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 541, Column 4: document type does not allow element "h1" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h1><span class="blue_header_v2" style="margin-top:60px">ONLINE DATING AT EVOW.…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 550, Column 73: required attribute "alt" not specified
    <img src="Images/grass_v2.png" align="left" style="margin-right: 15px" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 584, Column 49: required attribute "alt" not specified
    <img src="Images/couples_v2.jpg" width="300px" /></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 591, Column 51: character "&" is the first character of a delimiter but occurred as data
    … class="blue_header_v2">FREE TO VIEW MATCHES & FREE DATING SEARCHES</span></h3>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 616, Column 49: required attribute "alt" not specified
    <img src="Images/flowers_V2.png" width="150px" /></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 619, Column 78: end tag for element "h2" which is not open
    …lass="blue_header_v2">LIFETIME OF LOVE WITH SOMEONE SPECIAL</span></h2> Finding

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 629, Column 45: element "u" undefined
    …dvantage of all of eVow’s features. <u><strong><a class="nav" href="https://ww…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 630, Column 20: element "font" undefined
    <font color="green">REGISTER NOW!</font></a></strong></u><br />

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 635, Column 6: end tag for "h4" omitted, but OMITTAG NO was specified
    </div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 618, Column 1: start tag was here
    <h4>
  • Warning Line 656, Column 20: character "<" is the first character of a delimiter but occurred as data
    if (now.getHours() < 10) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 664, Column 22: character "<" is the first character of a delimiter but occurred as data
    if (now.getMinutes() < 10) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 671, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 671, Column 29: character "\" is not allowed in the value of attribute "type"
    document.write('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 671, Column 29: value of attribute "type" cannot be "\'hidden\'"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    document.write('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 671, Column 46: an attribute value must be a literal unless it contains only name characters
    …t.write('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=\'time…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 671, Column 50: character "+" not allowed in attribute specification list
    …ite('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=\'time\'/>…
  • Error Line 671, Column 50: document type does not allow element "input" here
    …ite('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=\'time\'/>…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 671, Column 51: end tag for "input" omitted, but OMITTAG NO was specified
    …te('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=\'time\'/>'…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 671, Column 17: start tag was here
    document.write('<input type=\'hidden\' value=\'' + then + '\' id=\'time\' name=…
  • Error Line 674, Column 29: an attribute value must be a literal unless it contains only name characters
    document.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 674, Column 29: character "\" is not allowed in the value of attribute "type"
    document.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 674, Column 29: value of attribute "type" cannot be "\'hidden\'"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    document.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 674, Column 46: an attribute value must be a literal unless it contains only name characters
    …ment.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/>');

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 674, Column 50: character "+" not allowed in attribute specification list
    …ment.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/>');
  • Error Line 674, Column 50: document type does not allow element "input" here
    …ment.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/>');

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 674, Column 51: end tag for "input" omitted, but OMITTAG NO was specified
    …ment.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/>');

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 674, Column 17: start tag was here
    document.write('<input type=\'hidden\' value=\'' + temp + '\' name=\'toffset\'/…
  • Error Line 700, Column 6: end tag for "form" omitted, but OMITTAG NO was specified
    </div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 648, Column 1: start tag was here
    <form action="default.aspx" method="post" onsubmit="generateTimeStamp(); return…
  • Error Line 720, Column 3: no document element
      

Visitor Analysis

Daily Visitor
  • 7.583 visits