Discover thousands of free patterns to download. You'll find free patterns for crochet, knitting, sewing, quilting, cross-stitch, plastic canvas, beading and more! ...

freepatterns.com
  • Domain Name
    freepatterns.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #52150
  • Page Size
    34.3 KB
  • Ip Address
    208.40.241.105
  • Heading
    H1: 1, H2: 5, H3: 5, H4: 1, H5: 0, H6: 0
  • Images
    5 GIF, 8 JPG, 1 PNG

Website Meta Analysis

  • Title
    Free Patterns - Download Free Patterns
  • Meta Keyword
    free crochet patterns, free knit patterns, free knitting patterns, free sewing patterns, free quilting patterns, free cross-stitch patterns, free plastic canvas patterns, free beading patterns, free craft downloads, free craft patterns
  • Meta Description
    Discover thousands of free patterns to download. You'll find free patterns for crochet, knitting, sewing, quilting, cross-stitch, plastic canvas, beading and more!

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    208.40.241.105
  • Domain Age
    14 Years, 0 Months, 3 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 23 Aug 2013 16:07:36 GMT
  • server: Apache
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: public
  • pragma: no-cache
  • p3p: CP="DSP IDC CUR ADM PSA PSDi OTPi DELi STP NAV COM UNI INT PHY DEM"
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 6598
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: freepatterns.com

Administrative Contact:
DRG Texas LP
Hollie Hollis ( email )
+1.8775898741
Fax:
306 E. Parr Rd.
Berne, IN 46711
US

Technical Contact:
DRG Texas LP
Hollie Hollis ( email )
+1.8775898741
Fax:
306 E. Parr Rd.
Berne, IN 46711
US

Registrant:
DRG Texas LP
Hollie Hollis ()

Fax:
306 E. Parr Rd.
Berne, IN 46711
US

Domain Status: Locked

Name Servers:
dns1.name-services.com
dns2.name-services.com
dns3.name-services.com
dns4.name-services.com
dns5.name-services.com

Created: 04 Aug 1999 23:04:42
Expires: 04 Aug 2012 23:04:00

DNS Analysis


DNS servers
dns1.name-services.com [98.124.192.1]
dns2.name-services.com [98.124.197.1]
dns3.name-services.com [98.124.193.1]
dns4.name-services.com [98.124.194.1]
dns5.name-services.com [98.124.196.1]


DNS Records

Answer records
freepatterns.com NS  dns2.name-services.com 3600s
freepatterns.com MX
preference: 10
exchange: mail.drgnetwork.com
1800s
freepatterns.com NS  dns1.name-services.com 3600s
freepatterns.com TXT google-site-verification=IDpYTi7H3v9BsNiVjKdE6z145NvP2Mtu1b3MF_KFXZg 1800s
freepatterns.com NS  dns5.name-services.com 3600s
freepatterns.com TXT v=spf1 ip4:63.76.155.0/25 ip4:67.238.120.128/25 ip4:208.40.241.64/26 ip4:66.231.87.126 include:drgnetwork.com include:qtropnews.com -all 1800s
freepatterns.com SOA
server: dns1.name-services.com
email: info@name-services.com
serial: 2002050701
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
1800s
freepatterns.com NS  dns4.name-services.com 3600s
freepatterns.com NS  dns3.name-services.com 3600s
freepatterns.com A 208.40.241.105 1800s

Authority records

Additional records

IP 208.40.241.105 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Carmel
  • Continent Code
    46032
  • Latitude
    317
  • Longitude
    527
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 208.40.241.105"
    #
    # Use "?" to get help.
    #

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

    Dynamic Resources Group NFRAME (NET-208-40-241-64-1) 208.40.241.64 - 208.40.241.127
    nFrame NFRAME (NET-208-40-224-0-1) 208.40.224.0 - 208.40.255.255


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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 47 Errors
  • 25 Warnings
Ratio Text/Html
  • 0.6034580821294506
Message Error
  • Error Line 6, Column 39: there is no attribute "XMLNS:FB"
    <!--[if gt IE 9]><!--> <html xmlns:fb="http://ogp.me/ns/fb#" class="no-js"> <!-…

    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 6, Column 68: there is no attribute "CLASS"
    … 9]><!--> <html xmlns:fb="http://ogp.me/ns/fb#" class="no-js"> <!--<![endif]-->

    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 15, Column 76: required attribute "TYPE" not specified
    …ript src="//ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js"></script>

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

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

  • Warning Line 18, Column 85: NET-enabling start-tag requires SHORTTAG YES
    …el="stylesheet" href="/modals/thickbox.css" type="text/css" media="screen" />		

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 35, Column 84: document type does not allow element "LINK" here
    …nk rel="stylesheet" type="text/css" href="/styles/global.css?v=01" media="all">

    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 36, Column 76: document type does not allow element "LINK" here
    <link rel="stylesheet" type="text/css" href="/styles/1_col.css" media="all">

    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 41, Column 107: document type does not allow element "LINK" here
    …="application/rss+xml" title="Free Pattern of the Day" href="/feeds/fpotd.xml">

    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 55, Column 10: end tag for element "HEAD" which is not open
    			</head>

    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 56, Column 8: document type does not allow element "BODY" here
    	<body >

    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).

  • Warning Line 97, Column 95: cannot generate system identifier for general entity "offset"
    …: 5px;"><a href="/list.html?mode=list&offset=0&limit=21&criteria=1212"><img sr…

    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 97, Column 95: general entity "offset" not defined and no default entity
    …: 5px;"><a href="/list.html?mode=list&offset=0&limit=21&criteria=1212"><img sr…

    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.

  • Error Line 97, Column 101: reference to entity "offset" for which no system identifier could be generated
    …"><a href="/list.html?mode=list&offset=0&limit=21&criteria=1212"><img src="/im…

    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 97, Column 94: entity was defined here
    …m: 5px;"><a href="/list.html?mode=list&offset=0&limit=21&criteria=1212"><img s…
  • Warning Line 97, Column 104: cannot generate system identifier for general entity "limit"
    …a href="/list.html?mode=list&offset=0&limit=21&criteria=1212"><img src="/image…

    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 97, Column 104: general entity "limit" not defined and no default entity
    …a href="/list.html?mode=list&offset=0&limit=21&criteria=1212"><img src="/image…

    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.

  • Error Line 97, Column 109: reference to entity "limit" for which no system identifier could be generated
    …f="/list.html?mode=list&offset=0&limit=21&criteria=1212"><img src="/images/mis…

    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 97, Column 103: entity was defined here
    …<a href="/list.html?mode=list&offset=0&limit=21&criteria=1212"><img src="/imag…
  • Warning Line 97, Column 113: cannot generate system identifier for general entity "criteria"
    …list.html?mode=list&offset=0&limit=21&criteria=1212"><img src="/images/misc/fr…

    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 97, Column 113: general entity "criteria" not defined and no default entity
    …list.html?mode=list&offset=0&limit=21&criteria=1212"><img src="/images/misc/fr…

    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.

  • Error Line 97, Column 121: reference to entity "criteria" for which no system identifier could be generated
    …l?mode=list&offset=0&limit=21&criteria=1212"><img src="/images/misc/freepatter…

    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 97, Column 112: entity was defined here
    …/list.html?mode=list&offset=0&limit=21&criteria=1212"><img src="/images/misc/f…
  • Warning Line 97, Column 214: NET-enabling start-tag requires SHORTTAG YES
    …isc/freepatterns_100added.png" border="0" alt="New Free Patterns!" /></a></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 134, Column 130: NET-enabling start-tag requires SHORTTAG YES
    …mages/misc/icon-twitter.gif" border="0" alt="Follow us on Twitter!" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 135, Column 209: NET-enabling start-tag requires SHORTTAG YES
    … src="/images/misc/icon-facebook.gif" border="0" alt="Facebook Us!" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 136, Column 202: NET-enabling start-tag requires SHORTTAG YES
    …sc/icon-pinterest.gif" border="0" alt="Follow us on Pinterest!" /></a></td>				

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 168, Column 59: cannot generate system identifier for general entity "cat_id"
    …l"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/s…

    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 168, Column 59: general entity "cat_id" not defined and no default entity
    …l"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/s…

    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.

  • Error Line 168, Column 65: reference to entity "cat_id" for which no system identifier could be generated
    …href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/small/2…

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 169, Column 61: reference to entity "cat_id" for which no system identifier could be generated
    …href="/detail.html?code=FC00007&cat_id=297">Picot Stitch Baby Blanket</a></div…

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 176, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    … href="/detail.html?code=FC00007&cat_id=297">Picot Stitch Baby Blanket</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 177, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FQ00118&cat_id=434">Spring Flower Runner</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 178, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FC01181&cat_id=297">Heart Strings Afghan</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 179, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FC00793&cat_id=297">Boy Wrapper</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 180, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    … href="/detail.html?code=FC01135&cat_id=297">Zigzag Shells Baby Afghan</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 181, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FC00907&cat_id=318">Easter Table Topper</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 182, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FC00794&cat_id=2">Rainbow Baby Jacket</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 183, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FC00809&cat_id=329">Mary Janes</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 184, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    …href="/detail.html?code=FC00691&cat_id=333">Canine Comfort Dog Sweater</a></li…

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 185, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FQ00107&cat_id=434">Garden Pathways</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Warning Line 200, Column 105: NET-enabling start-tag requires SHORTTAG YES
    …pe="checkbox" id="newsletter-awf" name="newsletter_id[AWF]" value="AWF" /></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 211, Column 105: NET-enabling start-tag requires SHORTTAG YES
    …pe="checkbox" id="newsletter-cwd" name="newsletter_id[CWD]" value="CWD" /></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 232, Column 51: value of attribute "TYPE" cannot be "EMAIL"; must be one of "TEXT", "PASSWORD", "CHECKBOX", "RADIO", "SUBMIT", "RESET", "FILE", "HIDDEN", "IMAGE", "BUTTON"
    …="newsletter_email"><input type="email" name="newsletter_email" autocapitalize…

    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 92: there is no attribute "AUTOCAPITALIZE"
    …ame="newsletter_email" autocapitalize="none" maxlength="80" placeholder="Enter…

    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 232, Column 126: there is no attribute "PLACEHOLDER"
    …ize="none" maxlength="80" placeholder="Enter your email address" value="" /></…

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

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

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

  • Warning Line 232, Column 162: NET-enabling start-tag requires SHORTTAG YES
    …="none" maxlength="80" placeholder="Enter your email address" value="" /></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 233, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …ame="submit" src="/images/misc/button-subscribe.gif" value="Subscribe" /></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 234, Column 52: NET-enabling start-tag requires SHORTTAG YES
    		<input type="hidden" name="mode" value="process" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 235, Column 55: NET-enabling start-tag requires SHORTTAG YES
    		<input type="hidden" name="source" value="multibox" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 326, Column 65: reference to entity "cat_id" for which no system identifier could be generated
    …href="/detail.html?code=FQ00460&cat_id=443"><img src="/images/patterns/small/3…

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 330, Column 61: reference to entity "cat_id" for which no system identifier could be generated
    …"><a href="/detail.html?code=FQ00460&cat_id=443">Scrappy Heart Jacket</a></div>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 355, Column 40: ID "NEWSLETTER_SIGNUP" already defined
    				<div style="margin-top: 16px;" id="newsletter_signup">

    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 192, Column 36: ID "NEWSLETTER_SIGNUP" first defined here
    <div style="margin-top: 16px;" id="newsletter_signup">
  • Error Line 363, Column 51: ID "NEWSLETTER-AWF" already defined
    …lign="top"><input type="checkbox" id="newsletter-awf" name="newsletter_id[AWF]…

    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 200, Column 51: ID "NEWSLETTER-AWF" first defined here
    …lign="top"><input type="checkbox" id="newsletter-awf" name="newsletter_id[AWF]…
  • Warning Line 363, Column 105: NET-enabling start-tag requires SHORTTAG YES
    …pe="checkbox" id="newsletter-awf" name="newsletter_id[AWF]" value="AWF" /></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 374, Column 51: ID "NEWSLETTER-CWD" already defined
    …lign="top"><input type="checkbox" id="newsletter-cwd" name="newsletter_id[CWD]…

    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 211, Column 51: ID "NEWSLETTER-CWD" first defined here
    …lign="top"><input type="checkbox" id="newsletter-cwd" name="newsletter_id[CWD]…
  • Warning Line 374, Column 105: NET-enabling start-tag requires SHORTTAG YES
    …pe="checkbox" id="newsletter-cwd" name="newsletter_id[CWD]" value="CWD" /></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 395, Column 51: value of attribute "TYPE" cannot be "EMAIL"; must be one of "TEXT", "PASSWORD", "CHECKBOX", "RADIO", "SUBMIT", "RESET", "FILE", "HIDDEN", "IMAGE", "BUTTON"
    …="newsletter_email"><input type="email" name="newsletter_email" autocapitalize…

    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.

  • Warning Line 395, Column 162: NET-enabling start-tag requires SHORTTAG YES
    …="none" maxlength="80" placeholder="Enter your email address" value="" /></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 396, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …ame="submit" src="/images/misc/button-subscribe.gif" value="Subscribe" /></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 397, Column 52: NET-enabling start-tag requires SHORTTAG YES
    		<input type="hidden" name="mode" value="process" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 398, Column 55: NET-enabling start-tag requires SHORTTAG YES
    		<input type="hidden" name="source" value="multibox" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 415, Column 168: NET-enabling start-tag requires SHORTTAG YES
    …r="0" alt="Download Pattern" src="/images/misc/button-download.gif"/></a></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 430, Column 69: reference to entity "cat_id" for which no system identifier could be generated
    …href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/small/2…

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 436, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    … href="/detail.html?code=FC00007&cat_id=297">Picot Stitch Baby Blanket</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 437, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FQ00118&cat_id=434">Spring Flower Runner</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 438, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FC01181&cat_id=297">Heart Strings Afghan</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 439, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FC00793&cat_id=297">Boy Wrapper</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 440, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    … href="/detail.html?code=FC01135&cat_id=297">Zigzag Shells Baby Afghan</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 441, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FC00907&cat_id=318">Easter Table Topper</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 442, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FC00794&cat_id=2">Rainbow Baby Jacket</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 443, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FC00809&cat_id=329">Mary Janes</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 444, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    …href="/detail.html?code=FC00691&cat_id=333">Canine Comfort Dog Sweater</a></li…

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 445, Column 46: reference to entity "cat_id" for which no system identifier could be generated
    <li><a href="/detail.html?code=FQ00107&cat_id=434">Garden Pathways</a></li>

    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 168, Column 58: entity was defined here
    …il"><a href="/detail.html?code=FC00007&cat_id=297"><img src="/images/patterns/…
  • Error Line 467, Column 115: end tag for element "P" which is not open
    …wnload, gather your supplies and start enjoying your favorite crafts!</p></div>

    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.

  • Warning Line 596, Column 157: NET-enabling start-tag requires SHORTTAG YES
    …="/images/misc/btn-supplies_yarn.jpg" /></a><a href="http://www.anniescatalog.…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 596, Column 157: required attribute "ALT" not specified
    …="/images/misc/btn-supplies_yarn.jpg" /></a><a href="http://www.anniescatalog.…

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

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

  • Warning Line 596, Column 307: NET-enabling start-tag requires SHORTTAG YES
    …/images/misc/btn-supplies_fabric.jpg" /></a><a href="http://www.AnniesCatalog.…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 596, Column 307: required attribute "ALT" not specified
    …/images/misc/btn-supplies_fabric.jpg" /></a><a href="http://www.AnniesCatalog.…

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

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

  • Warning Line 596, Column 483: NET-enabling start-tag requires SHORTTAG YES
    …SP" target="_blank"><img src="/images/misc/btn-supplies_card_making.jpg" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 596, Column 483: required attribute "ALT" not specified
    …SP" target="_blank"><img src="/images/misc/btn-supplies_card_making.jpg" /></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>.

Visitor Analysis

Daily Visitor
  • 1.167 visits