Sid Roth's It's Supernatural! and Messianic Vision Official Website. We are a ministry dedicated to reaching out with the good news of the Messiah, "to the Jew first" (Romans 1:16) and all people ...

sidroth.org
  • Domain Name
    sidroth.org
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #84418
  • Page Size
    56.4 KB
  • Ip Address
    66.45.103.33
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 11, H5: 3, H6: 0
  • Images
    27 GIF, 51 JPG, 7 PNG

Website Meta Analysis

  • Title
    It's Supernatural - Sid Roth - It's Supernatural
  • Meta Keyword
    yeshua, messianic vision, one new man, messiah,its supernatural, it's supernatural, supernatural, messianic
  • Meta Description
    Sid Roth's It's Supernatural! and Messianic Vision Official Website. We are a ministry dedicated to reaching out with the good news of the Messiah, "to the Jew first" (Romans 1:16) and all people through television, radio, speaking, publications and the Internet.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    66.45.103.33
  • Domain Age
    14 Years, 11 Months, 9 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from sidroth.org.

HTML Analysis

  • date: Thu, 27 Jun 2013 12:13:00 GMT
  • server: Apache
  • cache-control: private
  • content-type: text/html
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Access to .ORG WHOIS information is provided to assist persons in
determining the contents of a domain name registration record in the
Public Interest Registry registry database. The data in this record is provided by
Public Interest Registry for informational purposes only, and Public Interest Registry does not
guarantee its accuracy. This service is intended only for query-based
access. You agree that you will use this data only for lawful purposes
and that, under no circumstances will you use this data to: (a) allow,
enable, or otherwise support the transmission by e-mail, telephone, or
facsimile of mass unsolicited, commercial advertising or solicitations
to entities other than the data recipient's own existing customers; or
(b) enable high volume, automated, electronic processes that send
queries or data to the systems of Registry Operator, a Registrar, or
Afilias except as reasonably necessary to register domain names or
modify existing registrations. All rights reserved. Public Interest Registry reserves
the right to modify these terms at any time. By submitting this query,
you agree to abide by this policy.

Domain ID:D1512844-LROR
Domain Name:SIDROTH.ORG
Created On:03-Mar-1998 05:00:00 UTC
Last Updated On:03-May-2012 14:53:55 UTC
Expiration Date:02-Mar-2022 05:00:00 UTC
Sponsoring Registrar:Network Solutions, LLC (R63-LROR)
Status:CLIENT TRANSFER PROHIBITED
Registrant ID:25372331-NSI
Registrant Name:Messianic Vision
Registrant Organization:Messianic Vision
Registrant Street1:P.O. Box 1918
Registrant Street2:
Registrant Street3:
Registrant City:Brunswick
Registrant State/Province:GA
Registrant Postal Code:31521
Registrant Country:US
Registrant Phone:+1.912265250
Registrant Phone Ext.:
Registrant FAX:+1.912265373
Registrant FAX Ext.:
Registrant Email: email
Admin ID:25372332-NSI
Admin Name:Bob Duvall
Admin Organization:Messianic Vision
Admin Street1:P.O. Box 39222
Admin Street2:
Admin Street3:
Admin City:Charlotte
Admin State/Province:NC
Admin Postal Code:28278
Admin Country:US
Admin Phone:+1.7049436500
Admin Phone Ext.:
Admin FAX:+1.7049436501
Admin FAX Ext.:
Admin Email: email
Tech ID:44007828-NSI
Tech Name:Bob DuVall
Tech Street1:P.O. Box 1918
Tech Street2:
Tech Street3:
Tech City:Brunswick
Tech State/Province:GA
Tech Postal Code:31521
Tech Country:US
Tech Phone:+1.9122652500
Tech Phone Ext.:
Tech FAX:+1.9122653735
Tech FAX Ext.:
Tech Email: email
Name Server:NS21.WORLDNIC.COM
Name Server:NS22.WORLDNIC.COM
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
DNSSEC:Unsigned


DNS Analysis


DNS servers
ns21.worldnic.com [205.178.190.11]
ns22.worldnic.com [206.188.198.11]


DNS Records

Answer records
sidroth.org TXT v=spf1 +mx +include:outboundmail.convio.net ?all 86400s
sidroth.org A 66.45.103.33 7200s
sidroth.org MX
preference: 10
exchange: mx1.emailsrvr.com
7200s
sidroth.org MX
preference: 20
exchange: mx2.emailsrvr.com
7200s
sidroth.org NS  ns21.worldnic.com 7200s
sidroth.org SOA
server: NS21.WORLDNIC.COM
email: namehost@WORLDNIC.COM
serial: 109101211
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
7200s
sidroth.org NS  ns22.worldnic.com 7200s

Authority records

Additional records

IP 66.45.103.33 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Austin
  • Continent Code
    78758
  • Latitude
    512
  • Longitude
    635
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 66.45.103.33"
    #
    # Use "?" to get help.
    #

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

    Inflow Inc. NFLO-AR-2 (NET-66-45-0-0-1) 66.45.0.0 - 66.45.127.255
    Convio, Inc. CONVIO (NET-66-45-103-0-1) 66.45.103.0 - 66.45.103.127


    #
    # 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
  • 220 Errors
  • 35 Warnings
Ratio Text/Html
  • 0.585659645904363
Message Error
  • Error Line 86, Column 86: NET-enabling start-tag not immediately followed by null end-tag
    …l="image_src" href="http://www.sidroth.org/images/PW/2009/fb-thumbnail.jpg" / >

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 86, Column 86: end tag for "link" omitted, but OMITTAG NO was specified
    …l="image_src" href="http://www.sidroth.org/images/PW/2009/fb-thumbnail.jpg" / >

    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 86, Column 1: start tag was here
    <link rel="image_src" href="http://www.sidroth.org/images/PW/2009/fb-thumbnail.…
  • Error Line 86, Column 87: character data is not allowed here
    …l="image_src" href="http://www.sidroth.org/images/PW/2009/fb-thumbnail.jpg" / >

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 118, Column 117: document type does not allow element "a" here
    …block; margin: 15px; cursor: pointer;"><img src="../images/buy_now_below.png" …

    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 118, Column 158: required attribute "alt" not specified
    …argin: 15px; cursor: pointer;"><img src="../images/buy_now_below.png" /></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 152, Column 77: there is no attribute "displayText"
    …class='st_facebook_large' displayText=''></span><span class='st_twitter_large'…

    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 152, Column 79: document type does not allow element "span" here
    …ass='st_facebook_large' displayText=''></span><span class='st_twitter_large' d…

    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 152, Column 132: document type does not allow element "span" here
    …lass='st_twitter_large' displayText=''></span><span class='st_email_large' dis…

    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 152, Column 183: document type does not allow element "span" here
    … class='st_email_large' displayText=''></span><span class='st_sharethis_large'…

    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 152, Column 238: document type does not allow element "span" here
    …isplayText=''></span><span class='st_sharethis_large' displayText=''></span>");

    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 195, Column 14: there is no attribute "marginheight"
    marginheight="0"

    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 198, Column 13: there is no attribute "marginwidth"
    marginwidth="0"

    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 216, Column 83: required attribute "alt" not specified
    … <td id="bg-w"><img src="../images/PW/2009/w.jpg" width="10" height="770"></td>

    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 216, Column 88: end tag for "img" omitted, but OMITTAG NO was specified
    … <td id="bg-w"><img src="../images/PW/2009/w.jpg" width="10" height="770"></td>

    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 216, Column 25: start tag was here
              <td id="bg-w"><img src="../images/PW/2009/w.jpg" width="10" height="7…
  • Error Line 219, Column 289: end tag for "img" omitted, but OMITTAG NO was specified
    …" title="Sid Roth's It's Supernatural!&trade; &amp; Messianic Vision"></a></td>

    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 219, Column 88: start tag was here
    …rg/site/PageServer?pagename=homepage"><img src="../images/sp.gif" alt="Sid Rot…
  • Error Line 224, Column 86: end tag for element "string" which is not open
    …ont-size:10px;"><strong>IT&rsquo;S SUPERNATURAL! NETWORK&trade;</string></span>

    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 224, Column 93: end tag for "strong" omitted, but OMITTAG NO was specified
    …ont-size:10px;"><strong>IT&rsquo;S SUPERNATURAL! NETWORK&trade;</string></span>

    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 224, Column 31: start tag was here
    <span style="font-size:10px;"><strong>IT&rsquo;S SUPERNATURAL! NETWORK&trade;</…
  • Error Line 227, Column 110: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …lass="fontsizer" id="fontsizer_up" title="Increase Text Size"><div>A</div></a> 

    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 228, Column 111: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ass="fontsizer" id="fontsizer_down" title="Decrease Text Size"><div>A</div></a>

    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 229, Column 85: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …pt:resetFontSize();" class="fontsizer" title="Reset Text Size"><div>R</div></a>

    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 232, Column 56: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …ey_1400" id="survey_1400" method="POST" action="http://www.sidroth.org/site/Su…

    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 232, Column 111: there is no attribute "onSubmit"
    …www.sidroth.org/site/Survey" onSubmit="return checkDoubleClick1400();" style="…

    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 234, Column 151: end tag for "img" omitted, but OMITTAG NO was specified
    …" height="25" style="margin: 42px 9px 0px;" title="Receive Weekly Updates"><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 234, Column 9: start tag was here
            <img src="../images/sp.gif" alt="Receive Weekly Updates" width="183" he…
  • Error Line 234, Column 155: end tag for "br" omitted, but OMITTAG NO was specified
    …" height="25" style="margin: 42px 9px 0px;" title="Receive Weekly Updates"><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 234, Column 151: start tag was here
    …" height="25" style="margin: 42px 9px 0px;" title="Receive Weekly Updates"><br>
  • Error Line 235, Column 129: there is no attribute "onFocus"
    …ue="Enter your email address" onFocus="if(this.value=='Enter your email addres…

    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 235, Column 244: there is no attribute "onBlur"
    …_email', 'color', '#373735');" onBlur="if(this.value=='') this.value='Enter yo…

    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 235, Column 304: end tag for "input" omitted, but OMITTAG NO was specified
    …735');" onBlur="if(this.value=='') this.value='Enter your email address';"><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 235, Column 9: start tag was here
            <input type="text" name="cons_email" id="cons_email" size="45" maxlengt…
  • Error Line 235, Column 308: end tag for "br" omitted, but OMITTAG NO was specified
    …735');" onBlur="if(this.value=='') this.value='Enter your email address';"><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 235, Column 304: start tag was here
    …735');" onBlur="if(this.value=='') this.value='Enter your email address';"><br>
  • Error Line 241, Column 60: value of attribute "id" invalid: "1" cannot start a name
    …checkbox" name="1850_1400_2_1501" id="1850_1400_2_1501_1" class="checkbox" val…

    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 242, Column 60: value of attribute "id" invalid: "1" cannot start a name
    …checkbox" name="1850_1400_2_1501" id="1850_1400_2_1501_2" class="checkbox" val…

    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 244, Column 235: end tag for "input" omitted, but OMITTAG NO was specified
    …alt="Click to Sign up" title="Click to Sign up" style="margin: 3px 0 0 132px;">

    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 244, Column 9: start tag was here
            <input type="image" name="ACTION_SUBMIT_SURVEY_RESPONSE" id="ACTION_SUB…
  • Error Line 264, Column 261: end tag for "img" omitted, but OMITTAG NO was specified
    …="0" title="TELL A FRIEND &raquo;"></a><a href="http://www.facebook.com/sharer…

    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 264, Column 125: start tag was here
    …llafriend" style="margin-right: 3px;"><img src="../images/PW/2009/btn-TAF.png"…
  • Warning Line 264, Column 337: cannot generate system identifier for general entity "t"
    …er.php?u=http%3A%2F%2Fwww.sidroth.org&t=Sid+Roth%27s+%26quot%3BIt%27s+Supernat…

    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 264, Column 337: general entity "t" not defined and no default entity
    …er.php?u=http%3A%2F%2Fwww.sidroth.org&t=Sid+Roth%27s+%26quot%3BIt%27s+Supernat…

    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 264, Column 338: reference not terminated by REFC delimiter
    …r.php?u=http%3A%2F%2Fwww.sidroth.org&t=Sid+Roth%27s+%26quot%3BIt%27s+Supernatu…

    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 264, Column 338: reference to external entity in attribute value
    …r.php?u=http%3A%2F%2Fwww.sidroth.org&t=Sid+Roth%27s+%26quot%3BIt%27s+Supernatu…

    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 264, Column 338: reference to entity "t" for which no system identifier could be generated
    …r.php?u=http%3A%2F%2Fwww.sidroth.org&t=Sid+Roth%27s+%26quot%3BIt%27s+Supernatu…

    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 264, Column 336: entity was defined here
    …rer.php?u=http%3A%2F%2Fwww.sidroth.org&t=Sid+Roth%27s+%26quot%3BIt%27s+Superna…
  • Error Line 264, Column 620: end tag for "img" omitted, but OMITTAG NO was specified
    …rder="0" title="Share on Facebook"></a><a href="http://twitter.com/?status=Sid…

    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 264, Column 484: start tag was here
    …+show." target="_blank" id="facebook"><img src="../images/PW/2009/btn-facebook…
  • Error Line 264, Column 919: end tag for "img" omitted, but OMITTAG NO was specified
    …are on Twitter" width="20" height="20" border="0" title="Share on Twitter"></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 264, Column 786: start tag was here
    …oth.org" target="_blank" id="twitter"><img src="../images/PW/2009/btn-twitter-…
  • Error Line 268, Column 17: there is no attribute "size"
    <g:plusone size="medium" annotation="none"></g:plusone>

    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 268, Column 37: there is no attribute "annotation"
    <g:plusone size="medium" annotation="none"></g:plusone>

    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 268, Column 43: element "g:plusone" undefined
    <g:plusone size="medium" annotation="none"></g:plusone>

    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 281, Column 356: there is no attribute "allowTransparency"
    … overflow:hidden; width:450px; height:21px;" allowTransparency="true"></iframe>

    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 284, Column 5: 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 284, Column 1: start tag was here
    <br>
  • Warning Line 294, Column 143: cannot generate system identifier for general entity "d"
    …ite/PageServer?pagename=mobile_donate&d=https://secure2.convio.net/srmv/site/D…

    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 294, Column 143: general entity "d" not defined and no default entity
    …ite/PageServer?pagename=mobile_donate&d=https://secure2.convio.net/srmv/site/D…

    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 294, Column 144: reference not terminated by REFC delimiter
    …te/PageServer?pagename=mobile_donate&d=https://secure2.convio.net/srmv/site/Do…

    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 294, Column 144: reference to external entity in attribute value
    …te/PageServer?pagename=mobile_donate&d=https://secure2.convio.net/srmv/site/Do…

    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 294, Column 144: reference to entity "d" for which no system identifier could be generated
    …te/PageServer?pagename=mobile_donate&d=https://secure2.convio.net/srmv/site/Do…

    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 294, Column 142: entity was defined here
    …site/PageServer?pagename=mobile_donate&d=https://secure2.convio.net/srmv/site/…
  • Warning Line 294, Column 202: character "&" is the first character of a delimiter but occurred as data
    …secure2.convio.net/srmv/site/Donation2?df_id=1180&1180.donation=form1&s_src=B">

    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 294, Column 223: cannot generate system identifier for general entity "s_src"
    …secure2.convio.net/srmv/site/Donation2?df_id=1180&1180.donation=form1&s_src=B">

    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 294, Column 223: general entity "s_src" not defined and no default entity
    …secure2.convio.net/srmv/site/Donation2?df_id=1180&1180.donation=form1&s_src=B">

    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 294, Column 228: reference not terminated by REFC delimiter
    …secure2.convio.net/srmv/site/Donation2?df_id=1180&1180.donation=form1&s_src=B">

    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 294, Column 228: reference to external entity in attribute value
    …secure2.convio.net/srmv/site/Donation2?df_id=1180&1180.donation=form1&s_src=B">

    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 294, Column 228: reference to entity "s_src" for which no system identifier could be generated
    …secure2.convio.net/srmv/site/Donation2?df_id=1180&1180.donation=form1&s_src=B">

    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 294, Column 222: entity was defined here
    …secure2.convio.net/srmv/site/Donation2?df_id=1180&1180.donation=form1&s_src=B">
  • Error Line 295, Column 144: end tag for "img" omitted, but OMITTAG NO was specified
    …Now &raquo;" width="152" height="54" border="0" title="Donate Now &raquo;"></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 295, Column 10: start tag was here
             <img src="../images/PW/2009/btn-donate.gif" alt="Donate Now &raquo;" w…
  • Error Line 298, Column 14: 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 298, Column 10: start tag was here
             <br>
  • Error Line 308, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …border="0" title="ABOUT: Sid Roth"></a><a href="PageServer?pagename=art_mostre…

    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 308, Column 72: start tag was here
    …ef="PageServer?pagename=sid_aboutSid"><img src="../images/PW/2009/nav_sid.gif"…
  • Error Line 308, Column 378: end tag for "img" omitted, but OMITTAG NO was specified
    …r="0" title="ARTICLES: Learn More"></a><a href="PageServer?pagename=rad_aboutm…

    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 308, Column 243: start tag was here
    …="PageServer?pagename=art_mostrecent"><img src="../images/PW/2009/nav_art.gif"…
  • Error Line 308, Column 575: end tag for "img" omitted, but OMITTAG NO was specified
    …0" title="RADIO: Messianic Vision"></a><a href="PageServer?pagename=tv_itssupe…

    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 308, Column 434: start tag was here
    …er?pagename=rad_aboutmessianicvision"><img src="../images/PW/2009/nav_rad.gif"…
  • Error Line 308, Column 779: end tag for "img" omitted, but OMITTAG NO was specified
    …e="TELEVISION: It's Supernatural!"></a><a href="PageServer?pagename=catalog"><…

    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 308, Column 625: start tag was here
    …geServer?pagename=tv_itssupernatural"><img src="../images/PW/2009/nav_tv.gif" …
  • Error Line 308, Column 967: end tag for "img" omitted, but OMITTAG NO was specified
    …width="203" height="46" border="0" title="RESOURCES: Shop the Store"></a></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 308, Column 818: start tag was here
    …<a href="PageServer?pagename=catalog"><img src="../images/PW/2009/nav_catalog.…
  • Warning Line 357, Column 16: character "<" is the first character of a delimiter but occurred as data
    	for(var i=0;i < ca.length;i++) {

    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 380, Column 23: document type does not allow element "style" here
    <style type="text/css">

    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 391, Column 260: end tag for "br" omitted, but OMITTAG NO was specified
    …le="color:#7d3084;">watch a very short video from Sid Roth</a></strong> and<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 391, Column 256: start tag was here
    …le="color:#7d3084;">watch a very short video from Sid Roth</a></strong> and<br>
  • Error Line 392, Column 80: end tag for "br" omitted, but OMITTAG NO was specified
    …e of God, see miracles in your own<br> life and fulfill your divine destiny.</…

    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 392, Column 76: start tag was here
    …sence of God, see miracles in your own<br> life and fulfill your divine destin…
  • Error Line 392, Column 126: end tag for "br" omitted, but OMITTAG NO was specified
    …acles in your own<br> life and fulfill your divine destiny.</p><br><br><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 392, Column 122: start tag was here
    …acles in your own<br> life and fulfill your divine destiny.</p><br><br><br><br>
  • Error Line 392, Column 130: end tag for "br" omitted, but OMITTAG NO was specified
    …acles in your own<br> life and fulfill your divine destiny.</p><br><br><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 392, Column 126: start tag was here
    …acles in your own<br> life and fulfill your divine destiny.</p><br><br><br><br>
  • Error Line 392, Column 134: end tag for "br" omitted, but OMITTAG NO was specified
    …acles in your own<br> life and fulfill your divine destiny.</p><br><br><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 392, Column 130: start tag was here
    …acles in your own<br> life and fulfill your divine destiny.</p><br><br><br><br>
  • Error Line 392, Column 138: end tag for "br" omitted, but OMITTAG NO was specified
    …acles in your own<br> life and fulfill your divine destiny.</p><br><br><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 392, Column 134: start tag was here
    …acles in your own<br> life and fulfill your divine destiny.</p><br><br><br><br>
  • Error Line 393, Column 185: required attribute "alt" not specified
    …ges/content/pagebuilder/btn-watch-video.jpg" width="306" height="35"></a></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 393, Column 189: end tag for "img" omitted, but OMITTAG NO was specified
    …ges/content/pagebuilder/btn-watch-video.jpg" width="306" height="35"></a></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 393, Column 101: start tag was here
    …erver?pagename=homepage_new_visitors"><img src="../images/content/pagebuilder/…
  • Error Line 394, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><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 394, Column 1: start tag was here
    <br><br><br>
  • Error Line 394, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><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 394, Column 5: start tag was here
    <br><br><br>
  • Error Line 394, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    <br><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 394, Column 9: start tag was here
    <br><br><br>
  • Error Line 399, Column 23: document type does not allow element "style" here
    <style type="text/css"><!--

    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 579, Column 25: there is no attribute "ID"
    <td width="631"><DIV ID="banner"><DIV ID="slide1"><table border="0" cellspacing…

    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 579, Column 33: element "DIV" undefined
    <td width="631"><DIV ID="banner"><DIV ID="slide1"><table border="0" cellspacing…

    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 579, Column 50: element "DIV" undefined
    …631"><DIV ID="banner"><DIV ID="slide1"><table border="0" cellspacing="0" cellp…

    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 595, Column 24: there is no attribute "CLASS"
    <DIV ID="slide2" CLASS="hide"><table border="0" cellspacing="0" cellpadding="0">

    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 595, Column 30: element "DIV" undefined
    <DIV ID="slide2" CLASS="hide"><table border="0" cellspacing="0" cellpadding="0">

    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 606, Column 30: element "DIV" undefined
    <DIV ID="slide3" CLASS="hide"><table border="0" cellspacing="0" cellpadding="0">

    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 619, Column 30: element "DIV" undefined
    <DIV ID="slide4" CLASS="hide"><TABLE BORDER="0" CELLPADDING="0" CELLSPACING="0">

    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 619, Column 45: there is no attribute "BORDER"
    <DIV ID="slide4" CLASS="hide"><TABLE BORDER="0" CELLPADDING="0" CELLSPACING="0">

    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 619, Column 61: there is no attribute "CELLPADDING"
    <DIV ID="slide4" CLASS="hide"><TABLE BORDER="0" CELLPADDING="0" CELLSPACING="0">

    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 619, Column 77: there is no attribute "CELLSPACING"
    <DIV ID="slide4" CLASS="hide"><TABLE BORDER="0" CELLPADDING="0" CELLSPACING="0">

    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 619, Column 80: element "TABLE" undefined
    <DIV ID="slide4" CLASS="hide"><TABLE BORDER="0" CELLPADDING="0" CELLSPACING="0">

    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 620, Column 5: element "TR" undefined
    	<TR><TD><A HREF="PageServer?pagename=art_mostrecent"><IMG SRC="../images/pages…

    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 620, Column 9: element "TD" undefined
    	<TR><TD><A HREF="PageServer?pagename=art_mostrecent"><IMG SRC="../images/pages…

    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 620, Column 18: there is no attribute "HREF"
    	<TR><TD><A HREF="PageServer?pagename=art_mostrecent"><IMG SRC="../images/pages…

    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 620, Column 54: element "A" undefined
    …F="PageServer?pagename=art_mostrecent"><IMG SRC="../images/pages/homepage/bann…

    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 620, Column 64: there is no attribute "SRC"
    …ver?pagename=art_mostrecent"><IMG SRC="../images/pages/homepage/banner/article…

    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 620, Column 120: there is no attribute "ALT"
    …omepage/banner/articles/left.jpg" ALT="Ready to dig  deeper? Discover exciting…

    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 620, Column 299: there is no attribute "WIDTH"
    …d and more!  Read articles now" WIDTH="458" HEIGHT="229" BORDER="0" TITLE="Rea…

    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 620, Column 312: there is no attribute "HEIGHT"
    …Read articles now" WIDTH="458" HEIGHT="229" BORDER="0" TITLE="Ready to dig  de…

    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 620, Column 325: there is no attribute "BORDER"
    … now" WIDTH="458" HEIGHT="229" BORDER="0" TITLE="Ready to dig  deeper? Discove…

    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 620, Column 335: there is no attribute "TITLE"
    …H="458" HEIGHT="229" BORDER="0" TITLE="Ready to dig  deeper? Discover exciting…

    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 620, Column 507: element "IMG" undefined
    …, how to experience the presence of God and more!  Read articles now"></A></TD>

    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 620, Column 511: end tag for "IMG" omitted, but OMITTAG NO was specified
    …, how to experience the presence of God and more!  Read articles now"></A></TD>

    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 620, Column 55: start tag was here
    …="PageServer?pagename=art_mostrecent"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 621, Column 9: element "TD" undefined
        	<TD><A HREF="PageServer?pagename=art_howtoexperience"><IMG SRC="../images/…

    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 621, Column 59: element "A" undefined
    …geServer?pagename=art_howtoexperience"><IMG SRC="../images/pages/homepage/bann…

    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 621, Column 198: element "IMG" undefined
    …nce of God" WIDTH="172" HEIGHT="49" BORDER="0" TITLE="Presence of God"></A><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 621, Column 202: end tag for "IMG" omitted, but OMITTAG NO was specified
    …nce of God" WIDTH="172" HEIGHT="49" BORDER="0" TITLE="Presence of God"></A><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 621, Column 60: start tag was here
    …eServer?pagename=art_howtoexperience"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 621, Column 206: element "BR" undefined
    …nce of God" WIDTH="172" HEIGHT="49" BORDER="0" TITLE="Presence of God"></A><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 622, Column 58: element "A" undefined
    …PageServer?pagename=art_israelupdates"><IMG SRC="../images/pages/homepage/bann…

    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 622, Column 195: element "IMG" undefined
    …ael Updates" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Israel Updates"></A><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 622, Column 199: end tag for "IMG" omitted, but OMITTAG NO was specified
    …ael Updates" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Israel Updates"></A><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 622, Column 59: start tag was here
    …ageServer?pagename=art_israelupdates"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 622, Column 203: element "BR" undefined
    …ael Updates" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Israel Updates"></A><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 623, Column 64: element "A" undefined
    …rver?pagename=art_supernaturalhealing"><IMG SRC="../images/pages/homepage/bann…

    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 623, Column 213: element "IMG" undefined
    …aling" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Supernatural Healing"></A><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 623, Column 217: end tag for "IMG" omitted, but OMITTAG NO was specified
    …aling" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Supernatural Healing"></A><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 623, Column 65: start tag was here
    …ver?pagename=art_supernaturalhealing"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 623, Column 221: element "BR" undefined
    …aling" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Supernatural Healing"></A><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 624, Column 56: element "A" undefined
    …="PageServer?pagename=art_jewishroots"><IMG SRC="../images/pages/homepage/bann…

    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 624, Column 189: element "IMG" undefined
    …"Jewish Roots" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Jewish Roots"></A><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 624, Column 193: end tag for "IMG" omitted, but OMITTAG NO was specified
    …"Jewish Roots" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Jewish Roots"></A><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 624, Column 57: start tag was here
    …"PageServer?pagename=art_jewishroots"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 624, Column 197: element "BR" undefined
    …"Jewish Roots" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Jewish Roots"></A><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 625, Column 54: element "A" undefined
    …EF="PageServer?pagename=art_onenewman"><IMG SRC="../images/pages/homepage/bann…

    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 625, Column 185: element "IMG" undefined
    …="One New Man" WIDTH="172" HEIGHT="84" BORDER="0" TITLE="One New Man"></A></TD>

    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 625, Column 189: end tag for "IMG" omitted, but OMITTAG NO was specified
    …="One New Man" WIDTH="172" HEIGHT="84" BORDER="0" TITLE="One New Man"></A></TD>

    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 625, Column 55: start tag was here
    …F="PageServer?pagename=art_onenewman"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 625, Column 194: end tag for "BR" omitted, but OMITTAG NO was specified
    …="One New Man" WIDTH="172" HEIGHT="84" BORDER="0" TITLE="One New Man"></A></TD>

    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 624, Column 194: start tag was here
    …"Jewish Roots" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Jewish Roots"></A><BR>
  • Error Line 625, Column 194: end tag for "BR" omitted, but OMITTAG NO was specified
    …="One New Man" WIDTH="172" HEIGHT="84" BORDER="0" TITLE="One New Man"></A></TD>

    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 623, Column 218: start tag was here
    …aling" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Supernatural Healing"></A><BR>
  • Error Line 625, Column 194: end tag for "BR" omitted, but OMITTAG NO was specified
    …="One New Man" WIDTH="172" HEIGHT="84" BORDER="0" TITLE="One New Man"></A></TD>

    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 622, Column 200: start tag was here
    …ael Updates" WIDTH="172" HEIGHT="32" BORDER="0" TITLE="Israel Updates"></A><BR>
  • Error Line 625, Column 194: end tag for "BR" omitted, but OMITTAG NO was specified
    …="One New Man" WIDTH="172" HEIGHT="84" BORDER="0" TITLE="One New Man"></A></TD>

    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 621, Column 203: start tag was here
    …nce of God" WIDTH="172" HEIGHT="49" BORDER="0" TITLE="Presence of God"></A><BR>
  • Error Line 628, Column 30: element "DIV" undefined
    <DIV ID="slide5" CLASS="hide">

    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 50: element "TABLE" undefined
    <TABLE BORDER="0" CELLPADDING="0" CELLSPACING="0">

    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 631, Column 13: there is no attribute "VALIGN"
    	<TR VALIGN="TOP"><TD><IMG SRC="../images/pages/homepage/banner/exclusive_conte…

    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 631, Column 18: element "TR" undefined
    	<TR VALIGN="TOP"><TD><IMG SRC="../images/pages/homepage/banner/exclusive_conte…

    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 631, Column 22: element "TD" undefined
    	<TR VALIGN="TOP"><TD><IMG SRC="../images/pages/homepage/banner/exclusive_conte…

    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 631, Column 619: element "IMG" undefined
    …? And don't miss our teaching newsletter and book of Jewish testimonies!"></TD>

    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 631, Column 624: end tag for "IMG" omitted, but OMITTAG NO was specified
    …? And don't miss our teaching newsletter and book of Jewish testimonies!"></TD>

    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 631, Column 23: start tag was here
    	<TR VALIGN="TOP"><TD><IMG SRC="../images/pages/homepage/banner/exclusive_conte…
  • Error Line 632, Column 5: element "TD" undefined
    	<TD><A HREF="PageServer?pagename=sid_overviewfromSid"><IMG SRC="../images/page…

    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 632, Column 55: element "A" undefined
    …geServer?pagename=sid_overviewfromSid"><IMG SRC="../images/pages/homepage/bann…

    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 632, Column 275: element "IMG" undefined
    …BORDER="0" TITLE="Like our new site design?  Learn more about it here"></A><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 632, Column 279: end tag for "IMG" omitted, but OMITTAG NO was specified
    …BORDER="0" TITLE="Like our new site design?  Learn more about it here"></A><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 632, Column 56: start tag was here
    …eServer?pagename=sid_overviewfromSid"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 632, Column 283: element "BR" undefined
    …BORDER="0" TITLE="Like our new site design?  Learn more about it here"></A><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 633, Column 54: element "A" undefined
    …PageServer?pagename=art_othervideos#1"><IMG SRC="../images/pages/homepage/bann…

    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 633, Column 194: element "IMG" undefined
    …T="Sid's Story" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Sid's Story"></A><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 633, Column 198: end tag for "IMG" omitted, but OMITTAG NO was specified
    …T="Sid's Story" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Sid's Story"></A><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 633, Column 55: start tag was here
    …ageServer?pagename=art_othervideos#1"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 633, Column 202: element "BR" undefined
    …T="Sid's Story" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Sid's Story"></A><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 634, Column 59: element "A" undefined
    …erver?pagename=upd_ministrynewsletter"><IMG SRC="../images/pages/homepage/bann…

    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 634, Column 197: element "IMG" undefined
    …ALT="Newsletter" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Newsletter"></A><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 634, Column 201: end tag for "IMG" omitted, but OMITTAG NO was specified
    …ALT="Newsletter" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Newsletter"></A><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 634, Column 60: start tag was here
    …rver?pagename=upd_ministrynewsletter"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 634, Column 205: element "BR" undefined
    …ALT="Newsletter" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Newsletter"></A><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 59: element "A" undefined
    …erver?pagename=t_testimonials_archive"><IMG SRC="../images/pages/homepage/bann…

    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 199: element "IMG" undefined
    …T="Testimonies" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Testimonies"></A><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 203: end tag for "IMG" omitted, but OMITTAG NO was specified
    …T="Testimonies" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Testimonies"></A><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 635, Column 60: start tag was here
    …rver?pagename=t_testimonials_archive"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 635, Column 207: element "BR" undefined
    …T="Testimonies" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Testimonies"></A><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 636, Column 54: element "A" undefined
    …PageServer?pagename=art_othervideos#3"><IMG SRC="../images/pages/homepage/bann…

    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 636, Column 200: element "IMG" undefined
    …ring Yeshua" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Sharing Yeshua"></A><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 636, Column 204: end tag for "IMG" omitted, but OMITTAG NO was specified
    …ring Yeshua" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Sharing Yeshua"></A><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 636, Column 55: start tag was here
    …ageServer?pagename=art_othervideos#3"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 636, Column 208: element "BR" undefined
    …ring Yeshua" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Sharing Yeshua"></A><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 637, Column 54: element "A" undefined
    …PageServer?pagename=art_othervideos#2"><IMG SRC="../images/pages/homepage/bann…

    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 637, Column 198: element "IMG" undefined
    …o is Jesus?" WIDTH="167" HEIGHT="56" BORDER="0" TITLE="Who is Jesus?"></A></TD>

    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 637, Column 202: end tag for "IMG" omitted, but OMITTAG NO was specified
    …o is Jesus?" WIDTH="167" HEIGHT="56" BORDER="0" TITLE="Who is Jesus?"></A></TD>

    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 637, Column 55: start tag was here
    …ageServer?pagename=art_othervideos#2"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 637, Column 207: end tag for "BR" omitted, but OMITTAG NO was specified
    …o is Jesus?" WIDTH="167" HEIGHT="56" BORDER="0" TITLE="Who is Jesus?"></A></TD>

    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 636, Column 205: start tag was here
    …ring Yeshua" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Sharing Yeshua"></A><BR>
  • Error Line 637, Column 207: end tag for "BR" omitted, but OMITTAG NO was specified
    …o is Jesus?" WIDTH="167" HEIGHT="56" BORDER="0" TITLE="Who is Jesus?"></A></TD>

    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 635, Column 204: start tag was here
    …T="Testimonies" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Testimonies"></A><BR>
  • Error Line 637, Column 207: end tag for "BR" omitted, but OMITTAG NO was specified
    …o is Jesus?" WIDTH="167" HEIGHT="56" BORDER="0" TITLE="Who is Jesus?"></A></TD>

    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 634, Column 202: start tag was here
    …ALT="Newsletter" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Newsletter"></A><BR>
  • Error Line 637, Column 207: end tag for "BR" omitted, but OMITTAG NO was specified
    …o is Jesus?" WIDTH="167" HEIGHT="56" BORDER="0" TITLE="Who is Jesus?"></A></TD>

    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 633, Column 199: start tag was here
    …T="Sid's Story" WIDTH="167" HEIGHT="32" BORDER="0" TITLE="Sid's Story"></A><BR>
  • Error Line 637, Column 207: end tag for "BR" omitted, but OMITTAG NO was specified
    …o is Jesus?" WIDTH="167" HEIGHT="56" BORDER="0" TITLE="Who is Jesus?"></A></TD>

    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 632, Column 280: start tag was here
    …BORDER="0" TITLE="Like our new site design?  Learn more about it here"></A><BR>
  • Error Line 641, Column 5: element "DIV" undefined
    <DIV>

    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 642, Column 51: element "A" undefined
    …ascript:stopBanner();showBanner('1');"><IMG SRC="../images/pages/homepage/bann…

    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 642, Column 145: there is no attribute "NAME"
    …gif" ALT="It's Supernatural! TV" NAME="btn1" WIDTH="126" HEIGHT="32" BORDER="0…

    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 642, Column 190: there is no attribute "ID"
    …WIDTH="126" HEIGHT="32" BORDER="0" ID="btn1"></A><A HREF="javascript:stopBanne…

    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 642, Column 196: element "IMG" undefined
    …"126" HEIGHT="32" BORDER="0" ID="btn1"></A><A HREF="javascript:stopBanner();sh…

    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 642, Column 200: end tag for "IMG" omitted, but OMITTAG NO was specified
    …" HEIGHT="32" BORDER="0" ID="btn1"></A><A HREF="javascript:stopBanner();showBa…

    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 642, Column 52: start tag was here
    …script:stopBanner();showBanner('1');"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 642, Column 251: element "A" undefined
    …ascript:stopBanner();showBanner('2');"><IMG SRC="../images/pages/homepage/bann…

    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 642, Column 393: element "IMG" undefined
    …"126" HEIGHT="32" BORDER="0" ID="btn2"></A><A HREF="javascript:stopBanner();sh…

    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 642, Column 397: end tag for "IMG" omitted, but OMITTAG NO was specified
    …" HEIGHT="32" BORDER="0" ID="btn2"></A><A HREF="javascript:stopBanner();showBa…

    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 642, Column 252: start tag was here
    …script:stopBanner();showBanner('2');"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 642, Column 448: element "A" undefined
    …ascript:stopBanner();showBanner('3');"><IMG SRC="../images/pages/homepage/bann…

    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 642, Column 581: element "IMG" undefined
    …"126" HEIGHT="32" BORDER="0" ID="btn3"></A><A HREF="javascript:stopBanner();sh…

    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 642, Column 585: end tag for "IMG" omitted, but OMITTAG NO was specified
    …" HEIGHT="32" BORDER="0" ID="btn3"></A><A HREF="javascript:stopBanner();showBa…

    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 642, Column 449: start tag was here
    …script:stopBanner();showBanner('3');"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 642, Column 636: element "A" undefined
    …ascript:stopBanner();showBanner('4');"><IMG SRC="../images/pages/homepage/bann…

    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 642, Column 768: element "IMG" undefined
    …"125" HEIGHT="32" BORDER="0" ID="btn4"></A><A HREF="javascript:stopBanner();sh…

    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 642, Column 772: end tag for "IMG" omitted, but OMITTAG NO was specified
    …" HEIGHT="32" BORDER="0" ID="btn4"></A><A HREF="javascript:stopBanner();showBa…

    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 642, Column 637: start tag was here
    …script:stopBanner();showBanner('4');"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 642, Column 823: element "A" undefined
    …ascript:stopBanner();showBanner('5');"><IMG SRC="../images/pages/homepage/bann…

    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 642, Column 964: element "IMG" undefined
    …xclusive Content" NAME="btn5" WIDTH="127" HEIGHT="32" BORDER="0" ID="btn5"></A>

    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 642, Column 968: end tag for "IMG" omitted, but OMITTAG NO was specified
    …xclusive Content" NAME="btn5" WIDTH="127" HEIGHT="32" BORDER="0" ID="btn5"></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 642, Column 824: start tag was here
    …script:stopBanner();showBanner('5');"><IMG SRC="../images/pages/homepage/banne…
  • Error Line 645, Column 18: there is no attribute "LANGUAGE"
    <SCRIPT LANGUAGE="JAVASCRIPT">

    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 645, Column 30: element "SCRIPT" undefined
    <SCRIPT LANGUAGE="JAVASCRIPT">

    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 756, Column 96: there is no attribute "SRC"
    …Server?pagename=join_joinus"><img SRC="../images/content/pagebuilder/mentored-…

    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 756, Column 153: there is no attribute "ALT"
    …pagebuilder/mentored-monthly.gif" ALT="Be Mentored Monthly" WIDTH="304" HEIGHT…

    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 756, Column 181: there is no attribute "WIDTH"
    ….gif" ALT="Be Mentored Monthly" WIDTH="304" HEIGHT="261" TITLE="Be Mentored Mo…

    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 756, Column 194: there is no attribute "HEIGHT"
    …"Be Mentored Monthly" WIDTH="304" HEIGHT="261" TITLE="Be Mentored Monthly"></a>

    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 756, Column 206: there is no attribute "TITLE"
    …"Be Mentored Monthly" WIDTH="304" HEIGHT="261" TITLE="Be Mentored Monthly"></a>

    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 756, Column 227: required attribute "src" not specified
    …"Be Mentored Monthly" WIDTH="304" HEIGHT="261" TITLE="Be Mentored Monthly"></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 756, Column 227: required attribute "alt" not specified
    …"Be Mentored Monthly" WIDTH="304" HEIGHT="261" TITLE="Be Mentored Monthly"></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 756, Column 231: end tag for "img" omitted, but OMITTAG NO was specified
    …"Be Mentored Monthly" WIDTH="304" HEIGHT="261" TITLE="Be Mentored Monthly"></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 756, Column 87: start tag was here
    …site/PageServer?pagename=join_joinus"><img SRC="../images/content/pagebuilder/…
  • Error Line 762, Column 23: document type does not allow element "style" here
    <style type="text/css"><!--

    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 971, Column 39: document type does not allow element "style" here
    <td width="305"><style type="text/css"><!--

    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 1001, Column 80: end tag for "img" omitted, but OMITTAG NO was specified
      <img src="../images/content/pagebuilder/project_77_10-12.png" alt="Give now">

    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 1001, Column 3: start tag was here
      <img src="../images/content/pagebuilder/project_77_10-12.png" alt="Give now">
  • Warning Line 1004, Column 285: reference not terminated by REFC delimiter
    …Fpagename%3Dproject_77_mobile_donate&d=https%3A%2F%2Fsecure2.convio.net%2Fsrmv…

    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 1004, Column 285: reference to external entity in attribute value
    …Fpagename%3Dproject_77_mobile_donate&d=https%3A%2F%2Fsecure2.convio.net%2Fsrmv…

    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 1004, Column 285: reference to entity "d" for which no system identifier could be generated
    …Fpagename%3Dproject_77_mobile_donate&d=https%3A%2F%2Fsecure2.convio.net%2Fsrmv…

    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 294, Column 142: entity was defined here
    …site/PageServer?pagename=mobile_donate&d=https://secure2.convio.net/srmv/site/…
  • Warning Line 1005, Column 215: reference not terminated by REFC delimiter
    …Fpagename%3Dproject_77_mobile_donate&d=https%3A%2F%2Fsecure2.convio.net%2Fsrmv…

    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 1005, Column 215: reference to external entity in attribute value
    …Fpagename%3Dproject_77_mobile_donate&d=https%3A%2F%2Fsecure2.convio.net%2Fsrmv…

    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 1005, Column 215: reference to entity "d" for which no system identifier could be generated
    …Fpagename%3Dproject_77_mobile_donate&d=https%3A%2F%2Fsecure2.convio.net%2Fsrmv…

    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 294, Column 142: entity was defined here
    …site/PageServer?pagename=mobile_donate&d=https://secure2.convio.net/srmv/site/…
  • Error Line 1044, Column 83: required attribute "alt" not specified
    … <td id="bg-e"><img src="../images/PW/2009/e.jpg" width="10" height="770"></td>

    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 1044, Column 88: end tag for "img" omitted, but OMITTAG NO was specified
    … <td id="bg-e"><img src="../images/PW/2009/e.jpg" width="10" height="770"></td>

    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 1044, Column 25: start tag was here
              <td id="bg-e"><img src="../images/PW/2009/e.jpg" width="10" height="7…
  • Error Line 1047, Column 73: required attribute "alt" not specified
              <td><img src="../images/PW/2009/sw.gif" width="10" height="14"></td>

    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 1047, Column 78: end tag for "img" omitted, but OMITTAG NO was specified
              <td><img src="../images/PW/2009/sw.gif" width="10" height="14"></td>

    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 1047, Column 15: start tag was here
              <td><img src="../images/PW/2009/sw.gif" width="10" height="14"></td>
  • Error Line 1048, Column 73: required attribute "alt" not specified
              <td id="s"><img src="../images/sp.gif" width="940" height="14"></td>

    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 1048, Column 78: end tag for "img" omitted, but OMITTAG NO was specified
              <td id="s"><img src="../images/sp.gif" width="940" height="14"></td>

    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 1048, Column 22: start tag was here
              <td id="s"><img src="../images/sp.gif" width="940" height="14"></td>
  • Error Line 1049, Column 73: required attribute "alt" not specified
              <td><img src="../images/PW/2009/se.gif" width="10" height="14"></td>

    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 1049, Column 78: end tag for "img" omitted, but OMITTAG NO was specified
              <td><img src="../images/PW/2009/se.gif" width="10" height="14"></td>

    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 1049, Column 15: start tag was here
              <td><img src="../images/PW/2009/se.gif" width="10" height="14"></td>
  • Error Line 1052, Column 65: required attribute "alt" not specified
              <td><img src="../images/sp.gif" width="10" height="10"></td>

    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 1052, Column 70: end tag for "img" omitted, but OMITTAG NO was specified
              <td><img src="../images/sp.gif" width="10" height="10"></td>

    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 1052, Column 15: start tag was here
              <td><img src="../images/sp.gif" width="10" height="10"></td>
  • Error Line 1059, Column 138: end tag for "input" omitted, but OMITTAG NO was specified
    …e="GO" src="../images/PW/2009/btn-search.gif" alt="Search" title="Search"></td>

    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 1059, Column 17: start tag was here
                <td><input class="btn-search" type="image" value="GO" src="../image…
  • Error Line 1070, Column 80: ID "facebook" already defined
    …rnatural?fref=ts" target="_blank" id="facebook" style="padding:0;"><img src=".…

    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 264, Column 474: ID "facebook" first defined here
    …t%3B+radio+show." target="_blank" id="facebook"><img src="../images/PW/2009/bt…
  • Error Line 1070, Column 245: end tag for "img" omitted, but OMITTAG NO was specified
    …e on Facebook" width="20" height="20" border="0" title="Share on Facebook"></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 1070, Column 109: start tag was here
    …ank" id="facebook" style="padding:0;"><img src="../images/PW/2009/btn-facebook…
  • Error Line 1071, Column 139: required attribute "alt" not specified
    …tn-twitter.jpg" width="21" height="21"></a></td><td><iframe scrolling="no" fra…

    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 1071, Column 143: end tag for "img" omitted, but OMITTAG NO was specified
    …witter.jpg" width="21" height="21"></a></td><td><iframe scrolling="no" framebo…

    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 1071, Column 80: start tag was here
    …" target="_blank" style="padding:0;" ><img src="../images/btn-twitter.jpg" wid…
  • Error Line 1071, Column 210: there is no attribute "allowtransparency"
    …no" frameborder="0" allowtransparency="true" src="https://www.facebook.com/plu…

    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 1077, Column 30: end tag for "br" omitted, but OMITTAG NO was specified
        <br style="clear: both;">

    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 1077, Column 5: start tag was here
        <br style="clear: both;">
  • Error Line 1090, Column 258: end tag for "img" omitted, but OMITTAG NO was specified
    …0" style="border: 0px none #897e76;" title="powered by Convio&trade;"></a></td>

    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 1090, Column 57: start tag was here
    …ttp://www.convio.com" target="_blank"><img src="../images/powered_by_convio.gi…
  • Error Line 1091, Column 215: end tag for element "noscript" which is not open
    …ratmark.png" alt="STRATMARK" title="STRATMARK" border="0" /></a><br></noscript>

    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 1091, Column 215: end tag for "br" omitted, but OMITTAG NO was specified
    …ratmark.png" alt="STRATMARK" title="STRATMARK" border="0" /></a><br></noscript>

    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 1091, Column 201: start tag was here
    …ratmark.png" alt="STRATMARK" title="STRATMARK" border="0" /></a><br></noscript>
  • Error Line 1132, Column 65: required attribute "alt" not specified
              <td><img src="../images/sp.gif" width="10" height="10"></td>

    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 1132, Column 70: end tag for "img" omitted, but OMITTAG NO was specified
              <td><img src="../images/sp.gif" width="10" height="10"></td>

    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 1132, Column 15: start tag was here
              <td><img src="../images/sp.gif" width="10" height="10"></td>
  • Error Line 1152, Column 82: there is no attribute "async"
    …/javascript" src="//s3.amazonaws.com/ki.js/32017/6Rq.js" async="true"></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.

Visitor Analysis

Daily Visitor
  • 1.517 visits
Daily Visitor