kumkumapoovu Vrindavanam asianet serials ammakkili ammma Malayalam serials ...

go8pm.com
  • Domain Name
    go8pm.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #36606
  • Page Size
    49.7 KB
  • Ip Address
    204.93.165.101
  • Heading
    H1: 6, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 36 JPG, 0 PNG

Website Meta Analysis

  • Title
    Welcome to Kumkumapoovu Vrindavanam asianet serials ammakkili Amma Malayalam serials
  • Meta Keyword
    kumkumapoovu,ammakkili,amma,josco,Vrindavanam, videos, shows, asianet serials, Asianet, kairali, surya, jeevan, kumkumapoovu serial, malayalam tv, mammoty, mohanlal, asianet news live, malayalam movie actress, new movie download, new movie online, malayalam download, sreenivasan, serial actress, malayalam news,ente manasaputhri,kumkumapoovu online,watch ente manasaputhri,ente manasaputhri latest episode, Autograph,ammakkili,live news,asianet news,malayalam movie online,malayalam movie songs,malayalam movie download,kumkumapoovu latest episode,asianet serial,surya tv,malayalam serial,Kathayallithu Jeevitham latest episode
  • Meta Description
    kumkumapoovu Vrindavanam asianet serials ammakkili ammma Malayalam serials

Technical Analysis

  • Webserver
    Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
  • Ip Address
    204.93.165.101
  • Domain Age
    3 Years, 3 Months, 5 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 01 Mar 2013 06:08:42 GMT
  • server: Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-length: 7991
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for go8pm.com

IP 204.93.165.101 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    San Jose
  • Continent Code
    95134
  • Latitude
    408
  • Longitude
    807
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 204.93.165.101"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=204.93.165.101?showDetails=true&showARIN=false&ext=netref2
    #

    Server Central Network SCN-6 (NET-204-93-128-0-1) 204.93.128.0 - 204.93.255.255
    Mochanin Corp. SCNET-204-93-165-0-24 (NET-204-93-165-0-1) 204.93.165.0 - 204.93.165.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 50 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.5794889923211375
Message Error
  • Error Line 874, Column 13: ID "menuitem" already defined
       <div id="menuitem" align="left">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 867, Column 13: ID "menuitem" first defined here
       <div id="menuitem" align="left">
  • Error Line 875, Column 14: ID "itemheader" already defined
        <div id="itemheader"><h1>User area</h1></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 868, Column 14: ID "itemheader" first defined here
        <div id="itemheader"><h1>Category's</h1></div>
  • Warning Line 878, Column 72: cannot generate system identifier for general entity "done"
    <form  method="post" action="http://www.go8pm.com/index.php?task=login&done=1">

    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 878, Column 72: general entity "done" not defined and no default entity
    <form  method="post" action="http://www.go8pm.com/index.php?task=login&done=1">

    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 878, Column 76: reference not terminated by REFC delimiter
    <form  method="post" action="http://www.go8pm.com/index.php?task=login&done=1">

    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.

  • Warning Line 878, Column 76: reference to external entity in attribute value
    <form  method="post" action="http://www.go8pm.com/index.php?task=login&done=1">

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 878, Column 76: reference to entity "done" for which no system identifier could be generated
    <form  method="post" action="http://www.go8pm.com/index.php?task=login&done=1">

    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 878, Column 71: entity was defined here
    <form  method="post" action="http://www.go8pm.com/index.php?task=login&done=1">
  • Error Line 879, Column 22: end tag for "br" omitted, but OMITTAG NO was specified
      <label>Username<br>

    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 879, Column 18: start tag was here
      <label>Username<br>
  • Error Line 880, Column 65: end tag for "input" omitted, but OMITTAG NO was specified
      <input name="username" type="text" size="15" class="TEXTAREA">

    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 880, Column 3: start tag was here
      <input name="username" type="text" size="15" class="TEXTAREA">
  • Error Line 882, Column 7: end tag for "br" omitted, but OMITTAG NO was specified
      <br>

    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 882, Column 3: start tag was here
      <br>
  • Error Line 883, Column 22: end tag for "br" omitted, but OMITTAG NO was specified
      <label>Password<br>

    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 883, Column 18: start tag was here
      <label>Password<br>
  • Error Line 884, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
      <input name="password" type="password" size="15" class="TEXTAREA">

    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 884, Column 3: start tag was here
      <input name="password" type="password" size="15" class="TEXTAREA">
  • Error Line 885, Column 15: end tag for "br" omitted, but OMITTAG NO was specified
      </label><br><br>

    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 885, Column 11: start tag was here
      </label><br><br>
  • Error Line 885, Column 19: end tag for "br" omitted, but OMITTAG NO was specified
      </label><br><br>

    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 885, Column 15: start tag was here
      </label><br><br>
  • Error Line 887, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
      <input type="submit" name="Submit" value="Login" class="btn">

    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 887, Column 3: start tag was here
      <input type="submit" name="Submit" value="Login" class="btn">
  • Error Line 900, Column 13: ID "menuitem" already defined
       <div id="menuitem" align="left">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 867, Column 13: ID "menuitem" first defined here
       <div id="menuitem" align="left">
  • Error Line 901, Column 14: ID "itemheader" already defined
        <div id="itemheader"><h1>Comments</h1></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 868, Column 14: ID "itemheader" first defined here
        <div id="itemheader"><h1>Category's</h1></div>
  • Error Line 905, Column 13: ID "menuitem" already defined
       <div id="menuitem" align="left">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 867, Column 13: ID "menuitem" first defined here
       <div id="menuitem" align="left">
  • Error Line 906, Column 14: ID "itemheader" already defined
        <div id="itemheader"><h1>Chat</h1></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 868, Column 14: ID "itemheader" first defined here
        <div id="itemheader"><h1>Category's</h1></div>
  • Error Line 909, Column 48: document type does not allow element "a" here; assuming missing "li" start-tag
    <a href="http://www.go8pm.com/" target="_blank">
  • Error Line 918, Column 27: end tag for "img" omitted, but OMITTAG NO was specified
        style="border: 0;"></a>

    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 915, Column 16: start tag was here
                  ><img src="http://i45.tinypic.com/2cnxz6b.jpg"
  • Error Line 920, Column 53: required attribute "type" not specified
    <script src="http://widgets.twimg.com/j/2/widget.js"></script>

    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 921, Column 8: required attribute "type" not specified
    <script>

    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 951, Column 4: end tag for element "a" which is not open
    </a>

    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 952, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 909, Column 1: start tag was here
    <a href="http://www.go8pm.com/" target="_blank">
  • Error Line 954, Column 13: ID "menuitem" already defined
       <div id="menuitem" align="left">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 867, Column 13: ID "menuitem" first defined here
       <div id="menuitem" align="left">
  • Error Line 955, Column 14: ID "itemheader" already defined
        <div id="itemheader"><h1>Most Popular</h1></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 868, Column 14: ID "itemheader" first defined here
        <div id="itemheader"><h1>Category's</h1></div>
  • Error Line 963, Column 13: ID "menuitem" already defined
       <div id="menuitem" align="left">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 867, Column 13: ID "menuitem" first defined here
       <div id="menuitem" align="left">
  • Error Line 964, Column 14: ID "itemheader" already defined
        <div id="itemheader"><h1>Links</h1></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 868, Column 14: ID "itemheader" first defined here
        <div id="itemheader"><h1>Category's</h1></div>
  • Error Line 970, Column 13: end tag for element "ul" which is not open
      </div></ul>

    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 982, Column 80: document type does not allow element "td" here
                 <td width="100" height="150" rowspan="2" valign="top" align="left">

    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 983, Column 233: end tag for element "br" which is not open
    … height="150" class="movieicon" /></br>Minto Gol Comedy Stars S2 - 24 Feb 2013…

    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 985, Column 80: document type does not allow element "td" here
                 <td width="100" height="150" rowspan="2" valign="top" align="left">

    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 986, Column 248: end tag for element "br" which is not open
    … height="150" class="movieicon" /></br>C C L Kerala Strikers Vs Bengal  Tigers…

    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 988, Column 80: document type does not allow element "td" here
                 <td width="100" height="150" rowspan="2" valign="top" align="left">

    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 989, Column 207: end tag for element "br" which is not open
    …th="120" height="150" class="movieicon" /></br>Ustad Hotel (2012)</a></td>     

    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 991, Column 80: document type does not allow element "td" here
                 <td width="100" height="150" rowspan="2" valign="top" align="left">

    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 992, Column 187: end tag for element "br" which is not open
    …h="120" height="150" class="movieicon" /></br>Mr.Marumakan (2012)</a></td>     

    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 994, Column 80: document type does not allow element "td" here
                 <td width="100" height="150" rowspan="2" valign="top" align="left">

    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 995, Column 236: end tag for element "br" which is not open
    … height="150" class="movieicon" /></br>Vodafone Comedy Stars Season 2 24 Feb 2…

    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 997, Column 80: document type does not allow element "td" here
                 <td width="100" height="150" rowspan="2" valign="top" align="left">

    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 998, Column 190: end tag for element "br" which is not open
    …"" width="120" height="150" class="movieicon" /></br>Samar (2013)</a></td>     

    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 1092, Column 7: end tag for "center" 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 1002, Column 8: start tag was here
           <center>
  • Error Line 1102, Column 30: required attribute "type" not specified
    <script language="javascript"> 

    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 1120, Column 18: there is no attribute "LANGUAGE"
    <SCRIPT LANGUAGE="JavaScript1.1" SRC="http://bdv.bidvertiser.com/BidVertiser.db…

    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 1120, Column 38: there is no attribute "SRC"
    <SCRIPT LANGUAGE="JavaScript1.1" SRC="http://bdv.bidvertiser.com/BidVertiser.db…

    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 1120, Column 93: cannot generate system identifier for general entity "bid"
    …rtiser.com/BidVertiser.dbm?pid=384971&bid=1085675" type="text/javascript"></SC…

    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 1120, Column 93: general entity "bid" not defined and no default entity
    …rtiser.com/BidVertiser.dbm?pid=384971&bid=1085675" type="text/javascript"></SC…

    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 1120, Column 96: reference not terminated by REFC delimiter
    …ser.com/BidVertiser.dbm?pid=384971&bid=1085675" type="text/javascript"></SCRIP…

    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.

  • Warning Line 1120, Column 96: reference to external entity in attribute value
    …ser.com/BidVertiser.dbm?pid=384971&bid=1085675" type="text/javascript"></SCRIP…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 1120, Column 96: reference to entity "bid" for which no system identifier could be generated
    …ser.com/BidVertiser.dbm?pid=384971&bid=1085675" type="text/javascript"></SCRIP…

    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 1120, Column 92: entity was defined here
    …ertiser.com/BidVertiser.dbm?pid=384971&bid=1085675" type="text/javascript"></S…
  • Error Line 1120, Column 111: there is no attribute "type"
    …er.com/BidVertiser.dbm?pid=384971&bid=1085675" type="text/javascript"></SCRIPT>

    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 1120, Column 128: element "SCRIPT" undefined
    …er.com/BidVertiser.dbm?pid=384971&bid=1085675" type="text/javascript"></SCRIPT>

    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 1121, Column 10: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <noscript><a href="http://www.bidvertiser.com/bdv/BidVertiser/bdv_publisher.dbm…

    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 1125, Column 6: end tag for "p" 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 1118, Column 56: start tag was here
    <a id="displayText" href="javascript:toggle();">[X]</a><p> 
  • Error Line 1139, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 854, Column 1: start tag was here
    <div id="wrap">

Visitor Analysis

Daily Visitor
  • 4.433 visits
Daily Visitor