Testsieger im Flug-Preisvergleich bei ComputerBild, empfohlen von Stiftung Warentest. Über 100 Flug-Seiten wie airberlin, Expedia im Vergleich. Billigflüge finden und buchen. Billigflieger im Überblick. ...

swoodoo.com
  • Domain Name
    swoodoo.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #9929
  • Page Size
    77 KB
  • Ip Address
    185.6.168.66
  • Heading
    H1: 1, H2: 7, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 0 JPG, 4 PNG

Website Meta Analysis

  • Title
    swoodoo | Billige Flüge buchen - Billigflüge - Günstige Flug-Tickets für Billigflieger
  • Meta Keyword
  • Meta Description
    Testsieger im Flug-Preisvergleich bei ComputerBild, empfohlen von Stiftung Warentest. Über 100 Flug-Seiten wie airberlin, Expedia im Vergleich. Billigflüge finden und buchen. Billigflieger im Überblick.

Technical Analysis

  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    185.6.168.66
  • Domain Age
    7 Years, 8 Months, 9 days.
  • Javascript Library
    yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache-Coyote/1.1
  • pragma: no-cache
  • expires: Thu, 01 Jan 1970 00:00:00 GMT
  • cache-control: private, no-cache, no-store, must-revalidate, max-age=0
  • content-type: text/html;charset=UTF-8
  • content-language: en-US
  • content-encoding: gzip
  • vary: Accept-Encoding
  • p3p: CP="ALL DSP LAW CUR ADM DEVi TAI PSA PSD IVA IVD CONi OUR SAM LEG UNI PUR"
  • date: Tue, 10 Sep 2013 14:15:40 GMT
  • content-length: 15343
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
101domain, Inc. is the leader in International Domain
Name Registration.

Visit us at http://101domain.com for the largest select
of domains available anywhere and everywhere.

gTLDs at incredible prices.
ccTLDs at even more incredible prices.
Local presence & Trustee Services.
Web Hosting.
SSL Certificates.

Are you a brand or trademark holder?

Let us show you what we can do for your brand!

Corporate Domain Name Management
Comprehensive Brand Monitoring
Global Presence and Protection

Visit us at http://www.101domain.com/ today!

------------------------------------------------------------
TERMS OF USE: The data in this whois database is provided
only for lawful purposes. It is expressly forbidden to use
the data to: (a) allow, enable, or otherwise support the
transmission by e-mail, telephone, or facsimile of mass,
unsolicited, commercial advertising or solicitations to
entities other than the data recipient's own existing
customers; or (b) enable high volume, automated, electronic
processes that send queries or data to the systems of any
registry operator or ICANN-accredited registrar, except as
reasonably necessary to register domain names or modify
existing registrations. In addition to (a) and (b), high-
volume, automated, electronic processes directed at this
whois database is also expressly forbidden. Accuracy in
the provided data is not guaranteed. Failure to abide by
these terms of use may result in restricted or terminated
access. These terms of use may be modified at any time.
------------------------------------------------------------

Register your domain name at http://www.101domain.com/

Domain name: SWOODOO.COM

Registrant Contact:
KAYAK Europe GmbH
Network Operations ( email )
+1.9783698170 ext
Fax: +1. ext
Limmatquai 2
Zurich,
CH

Administrative Contact:
KAYAK Europe GmbH
Network Operations ( email )
+1.9783698170 ext
Fax: +1. ext
Limmatquai 2
Zurich,
CH

Technical Contact:
KAYAK Europe GmbH
Network Operations ( email )
+1.9783698170 ext
Fax: +1. ext
Limmatquai 2
Zurich,
CH

Billing Contact:
101Domain, Inc.
Billing Department ( email )
+1.7604448673 ext
Fax: +1.7605794996 ext
5858 Edison Pl.
Carlsbad, CA
US

Status:
ok

Name Servers:
A.DNSVR.COM
E.DNSVR.COM

Creation date: 11 Jan 2006 13:01:06
Expiration date: 11 Jan 2014 13:01:06
Updated date: 20 Jun 2012 17:06:26

DNS Analysis


DNS servers
ns1.p11.dynect.net [208.78.70.11]
ns3.p11.dynect.net [208.78.71.11]
ns2.p11.dynect.net [204.13.250.11]
ns4.p11.dynect.net [204.13.251.11]


DNS Records

Answer records
swoodoo.com SOA
server: ns1.p11.dynect.net
email: hostmaster@kayak.com
serial: 1357229556
refresh: 3600
retry: 600
expire: 604800
minimum ttl: 60
3600s
swoodoo.com NS  ns4.p11.dynect.net 86400s
swoodoo.com NS  ns2.p11.dynect.net 86400s
swoodoo.com NS  ns1.p11.dynect.net 86400s
swoodoo.com NS  ns3.p11.dynect.net 86400s
swoodoo.com A 208.94.138.66 3600s
swoodoo.com A 208.94.136.66 3600s
swoodoo.com MX
preference: 5
exchange: ALT2.ASPMX.L.GOOGLE.com
3600s
swoodoo.com MX
preference: 10
exchange: ASPMX2.GOOGLEMAIL.com
3600s
swoodoo.com MX
preference: 10
exchange: ASPMX3.GOOGLEMAIL.com
3600s
swoodoo.com MX
preference: 10
exchange: ASPMX4.GOOGLEMAIL.com
3600s
swoodoo.com MX
preference: 10
exchange: ASPMX5.GOOGLEMAIL.com
3600s
swoodoo.com MX
preference: 0
exchange: ASPMX.L.GOOGLE.com
3600s
swoodoo.com MX
preference: 5
exchange: ALT1.ASPMX.L.GOOGLE.com
3600s
swoodoo.com TXT v=spf1 a mx a:80.72.136.200 a:193.219.74.141 include:spf.kayak.com include:_spf.google.com ~all 3600s

Authority records

Additional records

IP 185.6.168.66 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 89 Errors
  • 53 Warnings
Ratio Text/Html
  • 0.6864350912778905
Message Error
  • Error Line 10, Column 16: there is no attribute "property"
    <meta property="og:image" content="http://www.swoodoo.com/v546253/aff/swoodoo_w…

    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 44, Column 74: end tag for "meta" omitted, but OMITTAG NO was specified
                    <meta name="apple-itunes-app" content="app-id=362070846">    

    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 44, Column 17: start tag was here
                    <meta name="apple-itunes-app" content="app-id=362070846">    
  • Error Line 66, Column 67: document type does not allow element "div" here
    …ss="nojs" style="border-width:0 0 1px"><span>F\u00FCr diese Website m\u00FCsse…

    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 66, Column 132: character "<" is the first character of a delimiter but occurred as data
    …te m\u00FCssen Cookies aktiviert sein.<\/span> Wir m\u00F6chten uns bei Ihrem …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 66, Column 218: an attribute value must be a literal unless it contains only name characters
    …hsten Besuch an Sie erinnern: <a href=\"http:\/\/lifehacker.com\/5461114\/fact…

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

  • Warning Line 66, Column 343: character "<" is the first character of a delimiter but occurred as data
    …Informieren Sie sich \u00FCber Cookies<\/a> und <a href=\"http:\/\/www.ehow.co…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 66, Column 361: an attribute value must be a literal unless it contains only name characters
    …ch \u00FCber Cookies<\/a> und <a href=\"http:\/\/www.ehow.com\/video_4751810_e…

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

  • Error Line 66, Column 421: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …m\/video_4751810_enable-cookies.html\">dar\u00FCber, wie man sie aktiviert.<\/…

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

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

  • Warning Line 66, Column 458: character "<" is the first character of a delimiter but occurred as data
    …51810_enable-cookies.html\">dar\u00FCber, wie man sie aktiviert.<\/a><\/div>');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 66, Column 463: character "<" is the first character of a delimiter but occurred as data
    …51810_enable-cookies.html\">dar\u00FCber, wie man sie aktiviert.<\/a><\/div>');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 68, Column 21: end tag for "a" omitted, but OMITTAG NO was specified
                </script>

    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 66, Column 353: start tag was here
    …n Sie sich \u00FCber Cookies<\/a> und <a href=\"http:\/\/www.ehow.com\/video_4…
  • Error Line 68, Column 21: end tag for "a" omitted, but OMITTAG NO was specified
                </script>

    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 66, Column 210: start tag was here
    …n\u00E4chsten Besuch an Sie erinnern: <a href=\"http:\/\/lifehacker.com\/54611…
  • Error Line 68, Column 21: end tag for "span" omitted, but OMITTAG NO was specified
                </script>

    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 66, Column 68: start tag was here
    …s="nojs" style="border-width:0 0 1px"><span>F\u00FCr diese Website m\u00FCssen…
  • Error Line 68, Column 21: end tag for "div" omitted, but OMITTAG NO was specified
                </script>

    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 66, Column 21: start tag was here
        document.write('<div class="nojs" style="border-width:0 0 1px"><span>F\u00F…
  • Error Line 92, Column 30: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            <div id="countryList"></div>

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

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

  • Error Line 109, Column 35: there is no attribute "role"
                    <div id="bd" role="main">

    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 116, Column 16: value of attribute "frameborder" cannot be "no"; must be one of "1", "0"
    frameborder="no" border="0" marginwidth="0" marginheight="0" SCROLLING="no" sty…

    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 116, Column 25: there is no attribute "border"
    frameborder="no" border="0" marginwidth="0" marginheight="0" SCROLLING="no" sty…

    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 116, Column 72: there is no attribute "SCROLLING"
    …nwidth="0" marginheight="0" SCROLLING="no" style="margin-top:0px;" src="/image…

    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 116, Column 83: duplicate specification of attribute "style"
    …marginheight="0" SCROLLING="no" style="margin-top:0px;" src="/images/1x1_blank…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Warning Line 117, Column 43: cannot generate system identifier for general entity "targeting"
    …desc="/s/sparkle?action=getgptcontent&targeting=adTile|1;isTest|N;origin|F..FD…

    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 117, Column 43: general entity "targeting" not defined and no default entity
    …desc="/s/sparkle?action=getgptcontent&targeting=adTile|1;isTest|N;origin|F..FD…

    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 117, Column 52: reference not terminated by REFC delimiter
    …sparkle?action=getgptcontent&targeting=adTile|1;isTest|N;origin|F..FD..R0;pos|…

    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 117, Column 52: reference to external entity in attribute value
    …sparkle?action=getgptcontent&targeting=adTile|1;isTest|N;origin|F..FD..R0;pos|…

    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 117, Column 52: reference to entity "targeting" for which no system identifier could be generated
    …sparkle?action=getgptcontent&targeting=adTile|1;isTest|N;origin|F..FD..R0;pos|…

    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 117, Column 42: entity was defined here
    …gdesc="/s/sparkle?action=getgptcontent&targeting=adTile|1;isTest|N;origin|F..F…
  • Warning Line 117, Column 136: cannot generate system identifier for general entity "id"
    …ssl|false;xp|no-op-nosearchautostart;&id=12907657|swoodoo|de|flight|frontdoor&…

    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 117, Column 136: general entity "id" not defined and no default entity
    …ssl|false;xp|no-op-nosearchautostart;&id=12907657|swoodoo|de|flight|frontdoor&…

    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 117, Column 138: reference not terminated by REFC delimiter
    …l|false;xp|no-op-nosearchautostart;&id=12907657|swoodoo|de|flight|frontdoor&si…

    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 117, Column 138: reference to external entity in attribute value
    …l|false;xp|no-op-nosearchautostart;&id=12907657|swoodoo|de|flight|frontdoor&si…

    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 117, Column 138: reference to entity "id" for which no system identifier could be generated
    …l|false;xp|no-op-nosearchautostart;&id=12907657|swoodoo|de|flight|frontdoor&si…

    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 117, Column 135: entity was defined here
    …;ssl|false;xp|no-op-nosearchautostart;&id=12907657|swoodoo|de|flight|frontdoor…
  • Warning Line 117, Column 176: cannot generate system identifier for general entity "size"
    …=12907657|swoodoo|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=136207…

    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 117, Column 176: general entity "size" not defined and no default entity
    …=12907657|swoodoo|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=136207…

    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 117, Column 180: reference not terminated by REFC delimiter
    …07657|swoodoo|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311…

    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 117, Column 180: reference to external entity in attribute value
    …07657|swoodoo|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311…

    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 117, Column 180: reference to entity "size" for which no system identifier could be generated
    …07657|swoodoo|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311…

    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 117, Column 175: entity was defined here
    …d=12907657|swoodoo|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=13620…
  • Warning Line 117, Column 189: cannot generate system identifier for general entity "origin"
    …odoo|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></if…

    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 117, Column 189: general entity "origin" not defined and no default entity
    …odoo|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></if…

    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 117, Column 195: reference not terminated by REFC delimiter
    …|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></iframe>

    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 117, Column 195: reference to external entity in attribute value
    …|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></iframe>

    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 117, Column 195: reference to entity "origin" for which no system identifier could be generated
    …|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></iframe>

    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 117, Column 188: entity was defined here
    …oodoo|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></i…
  • Warning Line 117, Column 206: cannot generate system identifier for general entity "ord"
    …|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></iframe>

    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 117, Column 206: general entity "ord" not defined and no default entity
    …|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></iframe>

    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 117, Column 209: reference not terminated by REFC delimiter
    …|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></iframe>

    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 117, Column 209: reference to external entity in attribute value
    …|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></iframe>

    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 117, Column 209: reference to entity "ord" for which no system identifier could be generated
    …|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></iframe>

    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 117, Column 205: entity was defined here
    …|de|flight|frontdoor&size=300x600&origin=F..FD..R0&ord=1362077311170"></iframe>
  • Error Line 123, Column 104: required attribute "alt" not specified
    …middle;width:22px;height:18px" src=""/><img style="vertical-align:middle;heigh…

    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 123, Column 242: required attribute "alt" not specified
    …p://www.swoodoo.com/v5461/images/time-mismatch.gif" width="1" height="1"/></td>

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

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

  • Error Line 140, Column 165: end tag for "b" omitted, but OMITTAG NO was specified
    … Uhrzeit/Datum geändert und möchte es jetzt noch einmal versuchen.</b></a></td>

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

  • Info Line 140, Column 21: start tag was here
                    <td><b><a href="javascript:document.location.reload(true)"><b>I…
  • Error Line 145, Column 4: document type does not allow element "tr" here; assuming missing "table" start-tag
    <tr>
  • Error Line 147, Column 33: an attribute value must be a literal unless it contains only name characters
    <table class="nojs" cellspacing=\"0\">

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

  • Error Line 149, Column 150: required attribute "alt" not specified
    ….com/v54661/images/a-warning-icon-maroon.gif" width="22px" height="18px"/></td>

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

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

  • Error Line 152, Column 103: end tag for "br" omitted, but OMITTAG NO was specified
    …erwendete Webbrowser funktioniert möglicherweise nicht wie erwartet.</span><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 152, Column 99: start tag was here
    …erwendete Webbrowser funktioniert möglicherweise nicht wie erwartet.</span><br>
  • Error Line 168, Column 46: document type does not allow element "div" here
    <div class="fdSearchForm fdSearchForm-flight">

    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 170, Column 42: required attribute "action" not specified
            <form name="lasttab" id="lasttab">

    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 213, Column 178: there is no attribute "role"
    …dtrip" title="Hin- und Rückflug" role="button"><span>Hin- und Rückflug</span><…

    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 242, Column 94: required attribute "alt" not specified
    …g src="http://www.swoodoo.com/v546163/images/arrows/a-reverse-directions.png"/>

    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 815, Column 10: document type does not allow element "noscript" here
    <noscript>

    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 818, Column 232: required attribute "alt" not specified
    …dass es aktiviert ist.                <img src="/s/images/no-javascript.gif" />

    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 822, Column 28: end tag for "table" omitted, but OMITTAG NO was specified
                          </div>

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

  • Info Line 145, Column 1: start tag was here
    <tr>
  • Error Line 1161, Column 106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arrow-ffffff-f3f3f3-shadow.png" width=45 height=30 style="position: absolute; …
  • Error Line 1161, Column 116: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ff-f3f3f3-shadow.png" width=45 height=30 style="position: absolute; right: 20p…
  • Error Line 1161, Column 183: required attribute "alt" not specified
    …=45 height=30 style="position: absolute; right: 20px; top: 1px; z-index: 101;">

    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 1161, Column 184: end tag for "img" omitted, but OMITTAG NO was specified
    …=45 height=30 style="position: absolute; right: 20px; top: 1px; z-index: 101;">

    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 1161, Column 13: start tag was here
                <img src="http://www.swoodoo.com/v546194/images/ttip/a-arrow-ffffff…
  • Error Line 1166, Column 15: there is no attribute "id"
        <TABLE id="innerTableTTTL" width="800" cellpadding="2" cellspacing="0" bord…

    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 1166, Column 38: there is no attribute "width"
        <TABLE id="innerTableTTTL" width="800" cellpadding="2" cellspacing="0" bord…

    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 1166, Column 56: there is no attribute "cellpadding"
    …BLE id="innerTableTTTL" width="800" cellpadding="2" cellspacing="0" border="0">

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

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

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

  • Error Line 1166, Column 72: there is no attribute "cellspacing"
    …BLE id="innerTableTTTL" width="800" cellpadding="2" cellspacing="0" border="0">

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

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

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

  • Error Line 1166, Column 83: there is no attribute "border"
    …BLE id="innerTableTTTL" width="800" cellpadding="2" cellspacing="0" border="0">

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

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

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

  • Error Line 1166, Column 86: element "TABLE" undefined
    …BLE id="innerTableTTTL" width="800" cellpadding="2" cellspacing="0" border="0">

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

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

    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 1178, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …br/>  ODER prüfen Sie, ob Toolbars oder andere Software Popups blockieren  <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 1178, Column 133: start tag was here
    …br/>  ODER prüfen Sie, ob Toolbars oder andere Software Popups blockieren  <br>
  • Error Line 1241, Column 139: document type does not allow element "div" here
    …mHTML = '<div class="smartbox-powered"><a target="_blank" href="http://www.kay…

    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 1284, Column 98: cannot generate system identifier for general entity "mt_adid"
    …l.mathtag.com\/event\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3…

    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 1284, Column 98: general entity "mt_adid" not defined and no default entity
    …l.mathtag.com\/event\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3…

    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 1284, Column 105: reference not terminated by REFC delimiter
    …ag.com\/event\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_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.

  • Error Line 1284, Column 105: reference to entity "mt_adid" for which no system identifier could be generated
    …ag.com\/event\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_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 1284, Column 97: entity was defined here
    …el.mathtag.com\/event\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io…
  • Warning Line 1284, Column 113: cannot generate system identifier for general entity "v1"
    …event\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_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 1284, Column 113: general entity "v1" not defined and no default entity
    …event\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_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 1284, Column 115: reference not terminated by REFC delimiter
    …ent\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI…

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

  • Error Line 1284, Column 115: reference to entity "v1" for which no system identifier could be generated
    …ent\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI…

    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 1284, Column 112: entity was defined here
    …/event\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_…
  • Warning Line 1284, Column 117: cannot generate system identifier for general entity "v2"
    …t\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&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 1284, Column 117: general entity "v2" not defined and no default entity
    …t\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&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.

  • Warning Line 1284, Column 119: reference not terminated by REFC delimiter
    …/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=…

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

  • Error Line 1284, Column 119: reference to entity "v2" for which no system identifier could be generated
    …/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=…

    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 1284, Column 116: entity was defined here
    …nt\/js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&…
  • Warning Line 1284, Column 121: cannot generate system identifier for general entity "v3"
    …s?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&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 1284, Column 121: general entity "v3" not defined and no default entity
    …s?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&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.

  • Warning Line 1284, Column 123: reference not terminated by REFC delimiter
    …mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=…

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

  • Error Line 1284, Column 123: reference to entity "v3" for which no system identifier could be generated
    …mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=…

    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 1284, Column 120: entity was defined here
    …js?mt_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&…
  • Warning Line 1284, Column 125: cannot generate system identifier for general entity "s1"
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=")…

    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 1284, Column 125: general entity "s1" not defined and no default entity
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=")…

    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 1284, Column 127: reference not terminated by REFC delimiter
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");

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

  • Error Line 1284, Column 127: reference to entity "s1" for which no system identifier could be generated
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");

    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 1284, Column 124: entity was defined here
    …t_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3="…
  • Warning Line 1284, Column 156: cannot generate system identifier for general entity "s2"
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");

    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 1284, Column 156: general entity "s2" not defined and no default entity
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");

    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 1284, Column 158: reference not terminated by REFC delimiter
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");

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

  • Error Line 1284, Column 158: reference to entity "s2" for which no system identifier could be generated
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");

    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 1284, Column 155: entity was defined here
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");
  • Warning Line 1284, Column 160: cannot generate system identifier for general entity "s3"
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");

    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 1284, Column 160: general entity "s3" not defined and no default entity
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");

    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 1284, Column 162: reference not terminated by REFC delimiter
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");

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

  • Error Line 1284, Column 162: reference to entity "s3" for which no system identifier could be generated
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");

    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 1284, Column 159: entity was defined here
    …_id=161875&mt_adid=100224&v1=&v2=&v3=&s1=zH28xl_Io3DaqW_20qqiYE4_MeI&s2=&s3=");
  • Error Line 1331, Column 45: document type does not allow element "div" here
    …dy').append('<div style="display:none"> <img src="http://swoodoode.widget.crit…

    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 1331, Column 126: cannot generate system identifier for general entity "wi"
    …com/psu/display.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEven…

    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 1331, Column 126: general entity "wi" not defined and no default entity
    …com/psu/display.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEven…

    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 1331, Column 128: reference not terminated by REFC delimiter
    …m/psu/display.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&…

    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 1331, Column 128: reference to external entity in attribute value
    …m/psu/display.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&…

    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 1331, Column 128: reference to entity "wi" for which no system identifier could be generated
    …m/psu/display.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&…

    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 1331, Column 125: entity was defined here
    ….com/psu/display.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEve…
  • Warning Line 1331, Column 137: cannot generate system identifier for general entity "pt1"
    …play.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=…

    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 1331, Column 137: general entity "pt1" not defined and no default entity
    …play.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=…

    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 1331, Column 140: reference not terminated by REFC delimiter
    …y.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif…

    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 1331, Column 140: reference to external entity in attribute value
    …y.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif…

    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 1331, Column 140: reference to entity "pt1" for which no system identifier could be generated
    …y.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif…

    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 1331, Column 136: entity was defined here
    …splay.js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype…
  • Warning Line 1331, Column 143: cannot generate system identifier for general entity "pt2"
    …s?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb…

    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 1331, Column 143: general entity "pt2" not defined and no default entity
    …s?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb…

    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 1331, Column 146: reference not terminated by REFC delimiter
    …1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' …

    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 1331, Column 146: reference to external entity in attribute value
    …1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' …

    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 1331, Column 146: reference to entity "pt2" for which no system identifier could be generated
    …1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' …

    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 1331, Column 142: entity was defined here
    …js?p1=' + escape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&c…
  • Warning Line 1331, Column 155: cannot generate system identifier for general entity "t1"
    …ape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.fl…

    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 1331, Column 155: general entity "t1" not defined and no default entity
    …ape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.fl…

    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 1331, Column 157: reference not terminated by REFC delimiter
    …e('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floo…

    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 1331, Column 157: reference to external entity in attribute value
    …e('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floo…

    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 1331, Column 157: reference to entity "t1" for which no system identifier could be generated
    …e('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floo…

    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 1331, Column 154: entity was defined here
    …cape('v=2&wi=7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.f…
  • Warning Line 1331, Column 168: cannot generate system identifier for general entity "resptype"
    …710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.rand…

    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 1331, Column 168: general entity "resptype" not defined and no default entity
    …710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.rand…

    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 1331, Column 176: reference not terminated by REFC delimiter
    …t1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 9…

    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 1331, Column 176: reference to external entity in attribute value
    …t1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 9…

    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 1331, Column 176: reference to entity "resptype" for which no system identifier could be generated
    …t1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 9…

    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 1331, Column 167: entity was defined here
    …7710481&pt1=0&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.ran…
  • Warning Line 1331, Column 181: cannot generate system identifier for general entity "cb"
    …pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 999999…

    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 1331, Column 181: general entity "cb" not defined and no default entity
    …pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 999999…

    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 1331, Column 183: reference not terminated by REFC delimiter
    …2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 99999999…

    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 1331, Column 183: reference to external entity in attribute value
    …2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 99999999…

    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 1331, Column 183: reference to entity "cb" for which no system identifier could be generated
    …2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 99999999…

    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 1331, Column 180: entity was defined here
    …&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 99999…
  • Error Line 1331, Column 234: required attribute "alt" not specified
    …t&resptype=gif&cb=' + Math.floor(Math.random() * 99999999999) + '" /> </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 1332, Column 45: document type does not allow element "div" here
    …dy').append('<div style="display:none"> <iframe src="http://dis.eu.criteo.com/…

    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 1332, Column 105: cannot generate system identifier for general entity "c"
    …dis.eu.criteo.com/dis/dis.aspx?p=1530&c=2&cb=' + Math.floor(Math.random() * 99…

    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 1332, Column 105: general entity "c" not defined and no default entity
    …dis.eu.criteo.com/dis/dis.aspx?p=1530&c=2&cb=' + Math.floor(Math.random() * 99…

    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 1332, Column 106: reference not terminated by REFC delimiter
    …is.eu.criteo.com/dis/dis.aspx?p=1530&c=2&cb=' + Math.floor(Math.random() * 999…

    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 1332, Column 106: reference to external entity in attribute value
    …is.eu.criteo.com/dis/dis.aspx?p=1530&c=2&cb=' + Math.floor(Math.random() * 999…

    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 1332, Column 106: reference to entity "c" for which no system identifier could be generated
    …is.eu.criteo.com/dis/dis.aspx?p=1530&c=2&cb=' + Math.floor(Math.random() * 999…

    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 1332, Column 104: entity was defined here
    …/dis.eu.criteo.com/dis/dis.aspx?p=1530&c=2&cb=' + Math.floor(Math.random() * 9…
  • Warning Line 1332, Column 111: reference not terminated by REFC delimiter
    ….criteo.com/dis/dis.aspx?p=1530&c=2&cb=' + Math.floor(Math.random() * 99999999…

    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 1332, Column 111: reference to external entity in attribute value
    ….criteo.com/dis/dis.aspx?p=1530&c=2&cb=' + Math.floor(Math.random() * 99999999…

    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 1332, Column 111: reference to entity "cb" for which no system identifier could be generated
    ….criteo.com/dis/dis.aspx?p=1530&c=2&cb=' + Math.floor(Math.random() * 99999999…

    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 1331, Column 180: entity was defined here
    …&pt2=1') + '&t1=sendEvent&resptype=gif&cb=' + Math.floor(Math.random() * 99999…

Visitor Analysis

Daily Visitor
  • 19.833 visits