The Sisterhood of the Shrinking Jeans LLC Eating Right Because Our Jeans Are Too Tight Home Challenge Deets Welcome! About Current Challenge Button Up! Writers Christy Melissa Heather Lisa Nancy Mary Melissa S. ...

shrinkingjeans.net
  • Domain Name
    shrinkingjeans.net
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #305135
  • Page Size
    116.5 KB
  • Ip Address
    216.70.83.156
  • Heading
    H1: 0, H2: 12, H3: 33, H4: 0, H5: 0, H6: 0
  • Images
    6 GIF, 32 JPG, 20 PNG

Website Meta Analysis

  • Title
    The Sisterhood of the Shrinking Jeans LLC - Eating Right Because Our Jeans Are Too Tight
  • Meta Keyword
  • Meta Description
    The Sisterhood of the Shrinking Jeans LLC Eating Right Because Our Jeans Are Too Tight Home Challenge Deets Welcome! About Current Challenge Button Up! Writers Christy Melissa Heather Lisa Nancy Mary Melissa S. Jodi Ann Bari Run the ‘Hood Reviews ...

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    216.70.83.156
  • Domain Age
    4 Years, 11 Months, 25 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from shrinkingjeans.net.

HTML Analysis

  • server: nginx
  • date: Fri, 30 Aug 2013 02:40:11 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-pingback: http://shrinkingjeans.net/xmlrpc.php
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for shrinkingjeans.net

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
shrinkingjeans.net MX
preference: 5
exchange: alt2.aspmx.l.google.com
1800s
shrinkingjeans.net A 216.70.83.156 1800s
shrinkingjeans.net NS  dns5.name-services.com 3600s
shrinkingjeans.net NS  dns3.name-services.com 3600s
shrinkingjeans.net SOA
server: dns1.name-services.com
email: [email protected]
serial: 2002050701
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
1800s
shrinkingjeans.net MX
preference: 10
exchange: aspmx3.googlemail.com
1800s
shrinkingjeans.net NS  dns1.name-services.com 3600s
shrinkingjeans.net MX
preference: 10
exchange: aspmx2.googlemail.com
1800s
shrinkingjeans.net NS  dns4.name-services.com 3600s
shrinkingjeans.net MX
preference: 1
exchange: aspmx.l.google.com
1800s
shrinkingjeans.net NS  dns2.name-services.com 3600s

Authority records

Additional records
dns3.name-services.com A 98.124.193.1 300s
dns1.name-services.com A 98.124.192.1 300s
dns5.name-services.com A 98.124.196.1 300s
dns2.name-services.com A 98.124.197.1 300s
dns4.name-services.com A 98.124.194.1 300s

IP 216.70.83.156 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Culver City
  • Continent Code
    90232
  • Latitude
    310
  • Longitude
    803
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 216.70.83.156"
    #
    # Use "?" to get help.
    #

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

    NetRange: 216.70.64.0 - 216.70.127.255
    CIDR: 216.70.64.0/18
    OriginAS:
    NetName: MEDIATEMPLE-102
    NetHandle: NET-216-70-64-0-1
    Parent: NET-216-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2005-06-22
    Updated: 2012-03-20
    Ref: http://whois.arin.net/rest/net/NET-216-70-64-0-1

    OrgName: Media Temple, Inc.
    OrgId: MEDIAT-10
    Address: 8520 National Blvd.
    Address: Building B
    City: Culver City
    StateProv: CA
    PostalCode: 90232
    Country: US
    RegDate: 2001-05-15
    Updated: 2010-06-29
    Ref: http://whois.arin.net/rest/org/MEDIAT-10

    OrgTechHandle: NA230-ARIN
    OrgTechName: NOC Hosting Operations
    OrgTechPhone: +1-877-578-4000
    OrgTechEmail: dnsadmin@mediatemple.net
    OrgTechRef: http://whois.arin.net/rest/poc/NA230-ARIN

    OrgAbuseHandle: ABUSE418-ARIN
    OrgAbuseName: Abuse Desk
    OrgAbusePhone: +1-877-578-4000
    OrgAbuseEmail: abuse@mediatemple.net
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE418-ARIN

    RTechHandle: NA230-ARIN
    RTechName: NOC Hosting Operations
    RTechPhone: +1-877-578-4000
    RTechEmail: dnsadmin@mediatemple.net
    RTechRef: http://whois.arin.net/rest/poc/NA230-ARIN

    #
    # 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
  • 91 Errors
  • 51 Warnings
Ratio Text/Html
  • 0.6993453094481654
Message Error
  • Error Line 173, Column 16: there is no attribute "property"
    <meta property='shareaholic:site_name' content='The Sisterhood of the Shrinking…

    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 208, Column 8: document type does not allow element "center" here; assuming missing "object" start-tag
    <center>
  • Warning Line 223, Column 81: cannot generate system identifier for general entity "cb"
    …/d.adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_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 223, Column 81: general entity "cb" not defined and no default entity
    …/d.adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_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 223, Column 83: reference not terminated by REFC delimiter
    ….adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 223, Column 83: reference to external entity in attribute value
    ….adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 223, Column 83: reference to entity "cb" for which no system identifier could be generated
    ….adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 223, Column 80: entity was defined here
    …//d.adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_…
  • Warning Line 223, Column 185: reference not terminated by REFC delimiter
    …dsbyisocket.com/avw.php?zoneid=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' 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 223, Column 185: reference to external entity in attribute value
    …dsbyisocket.com/avw.php?zoneid=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' 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 223, Column 185: reference to entity "cb" for which no system identifier could be generated
    …dsbyisocket.com/avw.php?zoneid=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' 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 223, Column 80: entity was defined here
    …//d.adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_…
  • Warning Line 223, Column 212: cannot generate system identifier for general entity "n"
    …eid=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' border='0' alt='' /></a></no…

    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 223, Column 212: general entity "n" not defined and no default entity
    …eid=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' border='0' alt='' /></a></no…

    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 223, Column 213: reference not terminated by REFC delimiter
    …id=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' border='0' alt='' /></a></nos…

    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 223, Column 213: reference to external entity in attribute value
    …id=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' border='0' alt='' /></a></nos…

    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 223, Column 213: reference to entity "n" for which no system identifier could be generated
    …id=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' border='0' alt='' /></a></nos…

    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 223, Column 211: entity was defined here
    …neid=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' border='0' alt='' /></a></n…
  • Error Line 270, Column 72: document type does not allow element "meta" here
    <meta name="msvalidate.01" content="0EF8A311666E35175E8C6D5CEA879914" />

    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 274, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 208, Column 1: start tag was here
    <center>
  • Error Line 292, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …1.png" border="0" alt="Sisterhood of the Shrinking Jeans DietBet"></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 292, Column 65: start tag was here
    …t.com/shrinkingjeans" target="_blank"><img src="http://shrinkingjeans.net/file…
  • Error Line 517, Column 194: end tag for "img" omitted, but OMITTAG NO was specified
    …8Ad1.png" border="0" alt="Sisterhood of the Shrinking Jeans DietBet"></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 517, Column 62: start tag was here
    …t.com/shrinkingjeans" target="_blank"><img src="http://shrinkingjeans.net/file…
  • Error Line 544, Column 225: there is no attribute "rel"
    …eck-in}"><span class="dsq-postid" rel="21784 http://shrinkingjeans.net/?p=2178…

    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 1365, Column 156: end tag for "img" omitted, but OMITTAG NO was specified
    …et.com/albums/w418/shrinkingkitchen/email.png" border="0" alt="Email us!t"></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 1365, Column 46: start tag was here
    …="mailto: support@shrinkingjeans.net"><img src="http://i1074.photobucket.com/a…
  • Error Line 1367, Column 179: end tag for "img" omitted, but OMITTAG NO was specified
    …ucket.com/albums/w418/shrinkingkitchen/flickr.png" border="0" alt="Flickr"></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 1367, Column 72: start tag was here
    …oups/shrinkingjeans/" target="_blank"><img src="http://i1074.photobucket.com/a…
  • Warning Line 1385, Column 83: reference not terminated by REFC delimiter
    ….adsbyisocket.com/ck.php?n=a8e8895a&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 1385, Column 83: reference to external entity in attribute value
    ….adsbyisocket.com/ck.php?n=a8e8895a&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 1385, Column 83: reference to entity "cb" for which no system identifier could be generated
    ….adsbyisocket.com/ck.php?n=a8e8895a&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 223, Column 80: entity was defined here
    …//d.adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_…
  • Warning Line 1385, Column 185: reference not terminated by REFC delimiter
    …dsbyisocket.com/avw.php?zoneid=7062&cb=INSERT_RANDOM_NUMBER_HERE&n=a8e8895a' 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 1385, Column 185: reference to external entity in attribute value
    …dsbyisocket.com/avw.php?zoneid=7062&cb=INSERT_RANDOM_NUMBER_HERE&n=a8e8895a' 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 1385, Column 185: reference to entity "cb" for which no system identifier could be generated
    …dsbyisocket.com/avw.php?zoneid=7062&cb=INSERT_RANDOM_NUMBER_HERE&n=a8e8895a' 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 223, Column 80: entity was defined here
    …//d.adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_…
  • Warning Line 1385, Column 213: reference not terminated by REFC delimiter
    …id=7062&cb=INSERT_RANDOM_NUMBER_HERE&n=a8e8895a' border='0' alt='' /></a></nos…

    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 1385, Column 213: reference to external entity in attribute value
    …id=7062&cb=INSERT_RANDOM_NUMBER_HERE&n=a8e8895a' border='0' alt='' /></a></nos…

    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 1385, Column 213: reference to entity "n" for which no system identifier could be generated
    …id=7062&cb=INSERT_RANDOM_NUMBER_HERE&n=a8e8895a' border='0' alt='' /></a></nos…

    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 223, Column 211: entity was defined here
    …neid=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' border='0' alt='' /></a></n…
  • Warning Line 1387, Column 171: cannot generate system identifier for general entity "c"
    …rnetwork.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Coll…

    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 1387, Column 171: general entity "c" not defined and no default entity
    …rnetwork.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Coll…

    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 1387, Column 172: reference not terminated by REFC delimiter
    …network.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Colle…

    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 1387, Column 172: reference to external entity in attribute value
    …network.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Colle…

    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 1387, Column 172: reference to entity "c" for which no system identifier could be generated
    …network.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Colle…

    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 1387, Column 170: entity was defined here
    …ernetwork.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Col…
  • Warning Line 1387, Column 175: cannot generate system identifier for general entity "s"
    …work.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collecti…

    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 1387, Column 175: general entity "s" not defined and no default entity
    …work.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collecti…

    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 1387, Column 176: reference not terminated by REFC delimiter
    …ork.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collectiv…

    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 1387, Column 176: reference to external entity in attribute value
    …ork.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collectiv…

    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 1387, Column 176: reference to entity "s" for which no system identifier could be generated
    …ork.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collectiv…

    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 1387, Column 174: entity was defined here
    …twork.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collect…
  • Warning Line 1387, Column 179: cannot generate system identifier for general entity "u"
    ….com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collective M…

    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 1387, Column 179: general entity "u" not defined and no default entity
    ….com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collective M…

    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 1387, Column 180: reference not terminated by REFC delimiter
    …com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collective Me…

    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 1387, Column 180: reference to external entity in attribute value
    …com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collective Me…

    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 1387, Column 180: reference to entity "u" for which no system identifier could be generated
    …com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collective Me…

    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 1387, Column 178: entity was defined here
    …k.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collective …
  • Error Line 1387, Column 233: required attribute "alt" not specified
    …title='Clever Girls Collective Member Badge' /></a><!-- END CGC Badge --></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 1391, Column 112: there is no attribute "data-client"
    …			<div class="textwidget"><div id="nmWidgetContainer" data-client="358"></div>

    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 1393, Column 48: required attribute "type" not specified
    <script src="http://cdn.nmcdn.us/js/connect.js"></script>

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

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

  • Error Line 1566, Column 270: end tag for "img" omitted, but OMITTAG NO was specified
    …s.net/files/2013/01/C25K-Badge.png" border="0" alt="Couch-to-5K Challenge"></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 1566, Column 162: start tag was here
    …couch-to-5k-move-it/" target="_blank"><img src="http://shrinkingjeans.net/file…
  • Error Line 1567, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1567, Column 1: start tag was here
    <br><br>
  • Error Line 1567, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1567, Column 5: start tag was here
    <br><br>
  • Error Line 1568, Column 256: end tag for "img" omitted, but OMITTAG NO was specified
    …491003405.png" border="0" alt="Fab Abs January Fitness Calendar Challenge"></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 1568, Column 103: start tag was here
    …ly-workout-calendar/" target="_blank"><img src="http://shrinkingjeans.net/file…
  • Warning Line 1585, Column 83: reference not terminated by REFC delimiter
    ….adsbyisocket.com/ck.php?n=aa2e121b&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 1585, Column 83: reference to external entity in attribute value
    ….adsbyisocket.com/ck.php?n=aa2e121b&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 1585, Column 83: reference to entity "cb" for which no system identifier could be generated
    ….adsbyisocket.com/ck.php?n=aa2e121b&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 223, Column 80: entity was defined here
    …//d.adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_…
  • Warning Line 1585, Column 185: reference not terminated by REFC delimiter
    …dsbyisocket.com/avw.php?zoneid=7063&cb=INSERT_RANDOM_NUMBER_HERE&n=aa2e121b' 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 1585, Column 185: reference to external entity in attribute value
    …dsbyisocket.com/avw.php?zoneid=7063&cb=INSERT_RANDOM_NUMBER_HERE&n=aa2e121b' 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 1585, Column 185: reference to entity "cb" for which no system identifier could be generated
    …dsbyisocket.com/avw.php?zoneid=7063&cb=INSERT_RANDOM_NUMBER_HERE&n=aa2e121b' 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 223, Column 80: entity was defined here
    …//d.adsbyisocket.com/ck.php?n=ac43b79d&cb=INSERT_RANDOM_NUMBER_HERE' target='_…
  • Warning Line 1585, Column 213: reference not terminated by REFC delimiter
    …id=7063&cb=INSERT_RANDOM_NUMBER_HERE&n=aa2e121b' border='0' alt='' /></a></nos…

    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 1585, Column 213: reference to external entity in attribute value
    …id=7063&cb=INSERT_RANDOM_NUMBER_HERE&n=aa2e121b' border='0' alt='' /></a></nos…

    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 1585, Column 213: reference to entity "n" for which no system identifier could be generated
    …id=7063&cb=INSERT_RANDOM_NUMBER_HERE&n=aa2e121b' border='0' alt='' /></a></nos…

    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 223, Column 211: entity was defined here
    …neid=7064&cb=INSERT_RANDOM_NUMBER_HERE&n=ac43b79d' border='0' alt='' /></a></n…
  • Error Line 1587, Column 87: there is no attribute "charset"
    …iv class="textwidget"><SCRIPT charset="utf-8" type="text/javascript" src="http…

    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 1587, Column 100: there is no attribute "type"
    …twidget"><SCRIPT charset="utf-8" type="text/javascript" src="http://ws.amazon.…

    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 1587, Column 122: there is no attribute "src"
    …et="utf-8" type="text/javascript" src="http://ws.amazon.com/widgets/q?rt=tf_sw…

    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 1587, Column 163: cannot generate system identifier for general entity "ServiceVersion"
    …tp://ws.amazon.com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&I…

    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 1587, Column 163: general entity "ServiceVersion" not defined and no default entity
    …tp://ws.amazon.com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&I…

    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 1587, Column 177: reference not terminated by REFC delimiter
    ….com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US…

    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 1587, Column 177: reference to external entity in attribute value
    ….com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US…

    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 1587, Column 177: reference to entity "ServiceVersion" for which no system identifier could be generated
    ….com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US…

    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 1587, Column 162: entity was defined here
    …ttp://ws.amazon.com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&…
  • Warning Line 1587, Column 187: cannot generate system identifier for general entity "MarketPlace"
    …ts/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistof…

    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 1587, Column 187: general entity "MarketPlace" not defined and no default entity
    …ts/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistof…

    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 1587, Column 198: reference not terminated by REFC delimiter
    …sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistofthes-20/800…

    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 1587, Column 198: reference to external entity in attribute value
    …sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistofthes-20/800…

    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 1587, Column 198: reference to entity "MarketPlace" for which no system identifier could be generated
    …sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistofthes-20/800…

    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 1587, Column 186: entity was defined here
    …ets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesisto…
  • Warning Line 1587, Column 202: cannot generate system identifier for general entity "ID"
    …erviceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistofthes-20/8002/0b…

    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 1587, Column 202: general entity "ID" not defined and no default entity
    …erviceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistofthes-20/8002/0b…

    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 1587, Column 204: reference not terminated by REFC delimiter
    …viceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistofthes-20/8002/0bd6…

    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 1587, Column 204: reference to external entity in attribute value
    …viceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistofthes-20/8002/0bd6…

    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 1587, Column 204: reference to entity "ID" for which no system identifier could be generated
    …viceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistofthes-20/8002/0bd6…

    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 1587, Column 201: entity was defined here
    …ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistofthes-20/8002/0…
  • Error Line 1587, Column 277: element "SCRIPT" undefined
    …/0bd675fd-5fff-4f94-b9b5-ac9f37ac9c67"> </SCRIPT> <NOSCRIPT><A HREF="http://ws…

    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 1587, Column 298: element "NOSCRIPT" undefined
    …9b5-ac9f37ac9c67"> </SCRIPT> <NOSCRIPT><A HREF="http://ws.amazon.com/widgets/q…

    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 1587, Column 307: there is no attribute "HREF"
    …7ac9c67"> </SCRIPT> <NOSCRIPT><A HREF="http://ws.amazon.com/widgets/q?rt=tf_sw…

    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 1587, Column 362: reference not terminated by REFC delimiter
    ….com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…

    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 1587, Column 362: reference to external entity in attribute value
    ….com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…

    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 1587, Column 362: reference to entity "ServiceVersion" for which no system identifier could be generated
    ….com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2F…

    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 1587, Column 162: entity was defined here
    …ttp://ws.amazon.com/widgets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&…
  • Warning Line 1587, Column 383: reference not terminated by REFC delimiter
    …sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Fthesistofthes-20…

    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 1587, Column 383: reference to external entity in attribute value
    …sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Fthesistofthes-20…

    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 1587, Column 383: reference to entity "MarketPlace" for which no system identifier could be generated
    …sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Fthesistofthes-20…

    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 1587, Column 186: entity was defined here
    …ets/q?rt=tf_sw&ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesisto…
  • Warning Line 1587, Column 389: reference not terminated by REFC delimiter
    …viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Fthesistofthes-20%2F800…

    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 1587, Column 389: reference to external entity in attribute value
    …viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Fthesistofthes-20%2F800…

    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 1587, Column 389: reference to entity "ID" for which no system identifier could be generated
    …viceVersion=20070822&MarketPlace=US&ID=V20070822%2FUS%2Fthesistofthes-20%2F800…

    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 1587, Column 201: entity was defined here
    …ServiceVersion=20070822&MarketPlace=US&ID=V20070822/US/thesistofthes-20/8002/0…
  • Warning Line 1587, Column 470: cannot generate system identifier for general entity "Operation"
    …F0bd675fd-5fff-4f94-b9b5-ac9f37ac9c67&Operation=NoScript">Amazon.com Widgets</…

    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 1587, Column 470: general entity "Operation" not defined and no default entity
    …F0bd675fd-5fff-4f94-b9b5-ac9f37ac9c67&Operation=NoScript">Amazon.com Widgets</…

    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 1587, Column 479: reference not terminated by REFC delimiter
    …-5fff-4f94-b9b5-ac9f37ac9c67&Operation=NoScript">Amazon.com Widgets</A></NOSCR…

    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 1587, Column 479: reference to external entity in attribute value
    …-5fff-4f94-b9b5-ac9f37ac9c67&Operation=NoScript">Amazon.com Widgets</A></NOSCR…

    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 1587, Column 479: reference to entity "Operation" for which no system identifier could be generated
    …-5fff-4f94-b9b5-ac9f37ac9c67&Operation=NoScript">Amazon.com Widgets</A></NOSCR…

    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 1587, Column 469: entity was defined here
    …2F0bd675fd-5fff-4f94-b9b5-ac9f37ac9c67&Operation=NoScript">Amazon.com Widgets<…
  • Error Line 1587, Column 489: element "A" undefined
    …ff-4f94-b9b5-ac9f37ac9c67&Operation=NoScript">Amazon.com Widgets</A></NOSCRIPT>

    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 1588, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1588, Column 1: start tag was here
    <br><br>
  • Error Line 1588, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <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 1588, Column 5: start tag was here
    <br><br>
  • Error Line 1589, Column 36: there is no attribute "data-href"
    <div class="fb-like-box" data-href="http://www.facebook.com/shrinkingjeans" dat…

    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 1589, Column 88: there is no attribute "data-width"
    …cebook.com/shrinkingjeans" data-width="120" data-show-faces="true" data-stream…

    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 1589, Column 110: there is no attribute "data-show-faces"
    …ans" data-width="120" data-show-faces="true" data-stream="false" data-header="…

    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 1589, Column 129: there is no attribute "data-stream"
    …dth="120" data-show-faces="true" data-stream="false" data-header="false"></div>

    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 1589, Column 149: there is no attribute "data-header"
    …dth="120" data-show-faces="true" data-stream="false" data-header="false"></div>

    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 1592, Column 260: end tag for "img" omitted, but OMITTAG NO was specified
    …ds/MenuPlanSK-01.png" border="1" alt="Weekly Menu Plans With Grocery List"></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 1592, Column 91: start tag was here
    …butt-off-more-menus/" target="_blank"><img src="http://i1074.photobucket.com/a…
  • Error Line 1660, Column 176: end tag for "img" omitted, but OMITTAG NO was specified
    …ww255/shrinkingjeans/christy-sidebar.jpg" border="0" alt="christy-sidebar"></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 1660, Column 53: start tag was here
    …//shrinkingjeans.net/christy-editor/"><img src="http://i725.photobucket.com/al…
  • Error Line 1662, 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 1662, Column 1: start tag was here
    <br>
  • Error Line 1663, Column 195: end tag for "img" omitted, but OMITTAG NO was specified
    …s/lissa-profile-nov.jpg" border="1" height="100" width="100" alt="Melissa"></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 1663, Column 53: start tag was here
    …//shrinkingjeans.net/melissa-editor/"><img src="http://i725.photobucket.com/al…
  • Error Line 1667, Column 178: end tag for "img" omitted, but OMITTAG NO was specified
    …/albums/ww255/shrinkingjeans/Thea-Profile-100px.jpg" border="1" alt="Thea"></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 1667, Column 63: start tag was here
    …gjeans.net/thea-contributing-writer/"><img src="http://i725.photobucket.com/al…
  • Error Line 1669, 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 1669, Column 1: start tag was here
    <br>
  • Error Line 1670, Column 178: end tag for "img" omitted, but OMITTAG NO was specified
    …com/albums/ww255/shrinkingjeans/heather100px.jpg" border="1" alt="Heather"></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 1670, Column 66: start tag was here
    …ans.net/heather-contributing-writer/"><img src="http://i725.photobucket.com/al…
  • Error Line 1672, 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 1672, Column 1: start tag was here
    <br>
  • Error Line 1673, Column 168: end tag for "img" omitted, but OMITTAG NO was specified
    …bucket.com/albums/ww255/shrinkingjeans/lisa-100.jpg" border="1" alt="Lisa"></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 1673, Column 63: start tag was here
    …gjeans.net/lisa-contributing-writer/"><img src="http://i725.photobucket.com/al…
  • Error Line 1675, 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 1675, Column 1: start tag was here
    <br>
  • Error Line 1676, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    …ket.com/albums/ww255/shrinkingjeans/nancy100px.jpg" border="1" alt="Nancy"></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 1676, Column 64: start tag was here
    …jeans.net/nancy-contributing-writer/"><img src="http://i725.photobucket.com/al…
  • Error Line 1678, 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 1678, Column 1: start tag was here
    <br>
  • Error Line 1679, Column 173: end tag for "img" omitted, but OMITTAG NO was specified
    …ket.com/albums/ww255/shrinkingjeans/karena100.jpg" border="1" alt="Karena"></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 1679, Column 65: start tag was here
    …eans.net/karena-contributing-writer/"><img src="http://i725.photobucket.com/al…
  • Error Line 1681, 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 1681, Column 1: start tag was here
    <br>
  • Error Line 1682, Column 167: end tag for "img" omitted, but OMITTAG NO was specified
    …obucket.com/albums/ww255/shrinkingjeans/Mary100.jpg" border="1" alt="Mary"></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 1682, Column 63: start tag was here
    …gjeans.net/mary-contributing-writer/"><img src="http://i725.photobucket.com/al…
  • Error Line 1684, 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 1684, Column 1: start tag was here
    <br>
  • Error Line 1685, Column 164: end tag for "img" omitted, but OMITTAG NO was specified
    …otobucket.com/albums/ww255/shrinkingjeans/mel100.jpg" border="1" alt="Mel"></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 1685, Column 62: start tag was here
    …ngjeans.net/mel-contributing-writer/"><img src="http://i725.photobucket.com/al…
  • Error Line 1687, 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 1687, Column 1: start tag was here
    <br>
  • Error Line 1688, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …3/01/melissa-150.jpg" border="1" height="100" width="100" alt="Melissa S."></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 1688, Column 74: start tag was here
    …about/melissa-s-contributing-writer/"><img src="http://shrinkingjeans.net/file…
  • Warning Line 1773, Column 89: cannot generate system identifier for general entity "tag"
    …=aHR0cDovL3Nocmlua2luZ2plYW5zLm5ldA==&tag=1" alt="Check Google Page Rank" styl…

    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 1773, Column 89: general entity "tag" not defined and no default entity
    …=aHR0cDovL3Nocmlua2luZ2plYW5zLm5ldA==&tag=1" alt="Check Google Page Rank" styl…

    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 1773, Column 92: reference not terminated by REFC delimiter
    …R0cDovL3Nocmlua2luZ2plYW5zLm5ldA==&tag=1" alt="Check Google Page Rank" style="…

    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 1773, Column 92: reference to external entity in attribute value
    …R0cDovL3Nocmlua2luZ2plYW5zLm5ldA==&tag=1" alt="Check Google Page Rank" style="…

    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 1773, Column 92: reference to entity "tag" for which no system identifier could be generated
    …R0cDovL3Nocmlua2luZ2plYW5zLm5ldA==&tag=1" alt="Check Google Page Rank" style="…

    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 1773, Column 88: entity was defined here
    …x=aHR0cDovL3Nocmlua2luZ2plYW5zLm5ldA==&tag=1" alt="Check Google Page Rank" sty…
  • Error Line 1774, 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 1774, Column 1: start tag was here
    <br>
  • Warning Line 1783, Column 242: reference not terminated by REFC delimiter
    …network.com/_clevergirls/badges/?a=c&c=gold&s=square&u=1011' title='Clever Gir…

    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 1783, Column 242: reference to external entity in attribute value
    …network.com/_clevergirls/badges/?a=c&c=gold&s=square&u=1011' title='Clever Gir…

    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 1783, Column 242: reference to entity "c" for which no system identifier could be generated
    …network.com/_clevergirls/badges/?a=c&c=gold&s=square&u=1011' title='Clever Gir…

    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 1387, Column 170: entity was defined here
    …ernetwork.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Col…
  • Warning Line 1783, Column 249: reference not terminated by REFC delimiter
    ….com/_clevergirls/badges/?a=c&c=gold&s=square&u=1011' title='Clever Girls Coll…

    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 1783, Column 249: reference to external entity in attribute value
    ….com/_clevergirls/badges/?a=c&c=gold&s=square&u=1011' title='Clever Girls Coll…

    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 1783, Column 249: reference to entity "s" for which no system identifier could be generated
    ….com/_clevergirls/badges/?a=c&c=gold&s=square&u=1011' title='Clever Girls Coll…

    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 1387, Column 174: entity was defined here
    …twork.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collect…
  • Warning Line 1783, Column 258: reference not terminated by REFC delimiter
    …vergirls/badges/?a=c&c=gold&s=square&u=1011' title='Clever Girls Collective Me…

    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 1783, Column 258: reference to external entity in attribute value
    …vergirls/badges/?a=c&c=gold&s=square&u=1011' title='Clever Girls Collective Me…

    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 1783, Column 258: reference to entity "u" for which no system identifier could be generated
    …vergirls/badges/?a=c&c=gold&s=square&u=1011' title='Clever Girls Collective Me…

    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 1387, Column 178: entity was defined here
    …k.com/_clevergirls/badges/?a=c&c=n&s=n&u=1011' title='Clever Girls Collective …
  • Error Line 1783, Column 311: required attribute "alt" not specified
    …title='Clever Girls Collective Member Badge' /></a><!-- END CGC Badge --></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 1785, Column 387: there is no attribute "property"
    …="http://shrinkingjeans.net" property="cc:attributionName" rel="cc:attribution…

    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 1816, Column 5: end tag for "ul" which is not finished
    </ul></div>    <script type="text/javascript">

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

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

Visitor Analysis

Daily Visitor
  • 665 visits