Günstige Sommerreifen, Winterreifen oder Kompletträder. Bequem Ersatz- und Verschleißteile online bei A.T.U bestellen. Wir haben alles was Ihr Auto braucht. ...

atu.de
  • Domain Name
    atu.de
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #20975
  • Page Size
    128.2 KB
  • Ip Address
    62.48.72.72
  • Heading
    H1: 1, H2: 5, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 40 JPG, 6 PNG

Website Meta Analysis

  • Title
    Reifen, Felgen und Autoteile im A.T.U Online Shop
  • Meta Keyword
    Reifen, Felgen, Autoteile, Auto, Ersatzteile, Verschleißteile, ATU
  • Meta Description
    Günstige Sommerreifen, Winterreifen oder Kompletträder. Bequem Ersatz- und Verschleißteile online bei A.T.U bestellen. Wir haben alles was Ihr Auto braucht.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    62.48.72.72
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from atu.de.

HTML Analysis

  • cache-control: no-cache, must-revalidate
  • pragma: no-cache
  • content-type: text/html;charset=UTF-8
  • content-encoding: gzip
  • expires: Thu, 26 Dec 2000 00:00:00 GMT
  • last-modified: Tue, 10 Sep 2013 03:07:40 GMT
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • p3p: CP="NOI DSP COR NID CURa ADMa DEVa PSAa PSDa OUR COM BUS INT OTC STA PUR"
  • date: Tue, 10 Sep 2013 03:07:40 GMT
  • content-length: 31570
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% Copyright (c) 2010 by DENIC
% Version: 2.0
%
% Restricted rights.
%
% Terms and Conditions of Use
%
% The data in this record is provided by DENIC for informational purposes only.
% DENIC does not guarantee its accuracy and cannot, under any circumstances,
% be held liable in case the stored information would prove to be wrong,
% incomplete or not accurate in any sense.
%
% All the domain data that is visible in the whois service is protected by law.
% It is not permitted to use it for any purpose other than technical or
% administrative requirements associated with the operation of the Internet.
% It is explicitly forbidden to extract, copy and/or use or re-utilise in any
% form and by any means (electronically or not) the whole or a quantitatively
% or qualitatively substantial part of the contents of the whois database
% without prior and explicit written permission by DENIC.
% It is prohibited, in particular, to use it for transmission of unsolicited
% and/or commercial and/or advertising by phone, fax, e-mail or for any similar
% purposes.
%
% By maintaining the connection you assure that you have a legitimate interest
% in the data and that you will only use it for the stated purposes. You are
% aware that DENIC maintains the right to initiate legal proceedings against
% you in the event of any breach of this assurance and to bar you from using
% its whois service.
%
% The DENIC whois service on port 43 never discloses any information concerning
% the domain holder/administrative contact. Information concerning the domain
% holder/administrative contact can be obtained through use of our web-based
% whois service available at the DENIC website:
% http://www.denic.de/en/background/whois-service/webwhois.html
%

Domain: atu.de
Nserver: dns1.dpn.de
Nserver: dns2.dpn.de
Status: connect
Changed: 2011-03-15T10:16:10+01:00

[Tech-C]
Type: PERSON
Name: Schiemann Volker
Address: Interoute Deutschland GmbH
Address: Prinzenallee 9
PostalCode: 40549
City: Duesseldorf
CountryCode: DE
Phone: +49.1805005492
Fax: +49.21150736200
Email: email
Changed: 2008-08-22T16:23:07+02:00

[Zone-C]
Type: PERSON
Name: Schiemann Volker
Address: Interoute Deutschland GmbH
Address: Prinzenallee 9
PostalCode: 40549
City: Duesseldorf
CountryCode: DE
Phone: +49.1805005492
Fax: +49.21150736200
Email: email
Changed: 2008-08-22T16:23:07+02:00

DNS Analysis


DNS servers
dns2.dpn.de [194.77.111.16]
dns1.dpn.de [194.231.40.24]


DNS Records

Answer records
atu.de SOA
server: dns2.dpn.de
email: hostmaster@dpn.de
serial: 2012102203
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
86400s
atu.de NS  dns2.dpn.de 86400s
atu.de NS  dns1.dpn.de 86400s
atu.de A 62.48.72.72 86400s
atu.de MX
preference: 5
exchange: mail2.atu.eu
86400s
atu.de MX
preference: 5
exchange: mail1.atu.eu
86400s

Authority records

Additional records
dns1.dpn.de A 194.231.40.24 86400s
dns2.dpn.de A 194.77.111.16 86400s
mail1.atu.eu A 193.37.131.22 86400s
mail2.atu.eu A 193.37.131.42 86400s

IP 62.48.72.72 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 182 Errors
  • 207 Warnings
Ratio Text/Html
  • 0.5920025586938478
Message Error
  • Error Line 47, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html lang="de" >

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 51, Column 46: there is no attribute "class"
    <!--[if gt IE 8]><!--> <html lang="de" class="no-js"> <!--<![endif]-->

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

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

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

  • Error Line 51, Column 53: document type does not allow element "html" here
    <!--[if gt IE 8]><!--> <html lang="de" class="no-js"> <!--<![endif]-->

    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 51, Column 24: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <!--[if gt IE 8]><!--> <html lang="de" class="no-js"> <!--<![endif]-->

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 80, Column 17: document type does not allow element "a" here; assuming missing "object" start-tag
    <a name="fh_top"></a>
  • Error Line 81, Column 59: document type does not allow element "link" here
    <link rel="icon" href="/favicon.ico" type="image/x-icon" />

    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 82, Column 68: document type does not allow element "link" here
    <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" />

    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 84, Column 83: document type does not allow element "link" here
    …k href="/de/resources/css/layout.css?rnd=1" rel="stylesheet" type="text/css" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 85, Column 77: document type does not allow element "link" here
    <link href="/de/resources/css/styles.css" rel="stylesheet" type="text/css" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 87, Column 115: document type does not allow element "link" here
    …n/opensearchdescription+xml" rel="search"  href="/de/content/xml/atu-os.xml" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 88, Column 109: document type does not allow element "link" here
    …plication/rss+xml" title="A.T.U RSS Feed" href="/de/content/xml/getnews.jsp" />

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

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

  • Info Line 80, Column 1: start tag was here
    <a name="fh_top"></a>
  • Error Line 126, Column 31: document type does not allow element "script" here; assuming missing "body" start-tag
    <script type="text/javascript">
  • Error Line 130, Column 6: document type does not allow element "body" here
    <body>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 179, Column 80: document type does not allow element "link" here
    <link rel="stylesheet" href="/de/resources/css/json_menu.css" type="text/css" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 180, Column 91: cannot generate system identifier for general entity "active"
    …">var json_menu_url = "/de/content/navi/json_menu.jsp?type=1&active=";</script>

    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 180, Column 91: general entity "active" not defined and no default entity
    …">var json_menu_url = "/de/content/navi/json_menu.jsp?type=1&active=";</script>

    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 180, Column 97: reference not terminated by REFC delimiter
    …">var json_menu_url = "/de/content/navi/json_menu.jsp?type=1&active=";</script>

    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 180, Column 97: reference to entity "active" for which no system identifier could be generated
    …">var json_menu_url = "/de/content/navi/json_menu.jsp?type=1&active=";</script>

    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 180, Column 90: entity was defined here
    …">var json_menu_url = "/de/content/navi/json_menu.jsp?type=1&active=";</script>
  • Error Line 207, Column 10: element "header" undefined
    		<header>

    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).
  • Warning Line 211, Column 69: character "&" is the first character of a delimiter but occurred as data
    …"http://www.atu.de/" class="logo">A.T.U. - Autoteile & Zubeh&ouml;r</a></h1>			

    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 220, Column 34: character "<" is the first character of a delimiter but occurred as data
                			for (var i = 0; i < splitSearchterm.length; i++)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 225, Column 61: character "&" is the first character of a delimiter but occurred as data
                			splitSearchterm = searchtermBereinigt.split("&");

    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 227, Column 34: character "<" is the first character of a delimiter but occurred as data
                			for (var i = 0; i < splitSearchterm.length; i++)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 234, Column 34: character "<" is the first character of a delimiter but occurred as data
                			for (var i = 0; i < splitSearchterm.length; i++)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 241, Column 34: character "<" is the first character of a delimiter but occurred as data
                			for (var i = 0; i < splitSearchterm.length; i++)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 255, Column 75: there is no attribute "placeholder"
    …alue="" name="searchterm" placeholder="Suchbegriff, Webcode, Artikelnummer ode…

    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 255, Column 150: end tag for "input" omitted, but OMITTAG NO was specified
    …der="Suchbegriff, Webcode, Artikelnummer oder OE-Nummer eingeben" class="text">

    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 255, Column 17: start tag was here
                    <input type="text" value="" name="searchterm" placeholder="Such…
  • Error Line 256, Column 50: syntax of attribute value does not conform to declared value
                    <input type="submit" name="" id="" value="" class="submit" />

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 260, Column 15: there is no attribute "class"
    			<nav class="main" style="z-index:2;">

    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 260, Column 28: there is no attribute "style"
    			<nav class="main" style="z-index:2;">

    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 260, Column 40: element "nav" undefined
    			<nav class="main" style="z-index:2;">

    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 279, Column 21: element "nav" undefined
    			<nav class="meta">

    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 301, Column 46: element "nav" undefined
                		        	<nav class="secondary">

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

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 420, Column 109: character "&" is the first character of a delimiter but occurred as data
    …line-shop/kategorie/Felgen-Raeder-und-Reifen_w5369/">Felgen, Räder & Reifen</a>

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

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 470, Column 113: character "&" is the first character of a delimiter but occurred as data
    …gen-Raeder-und-Reifen-w5369/Alufelgen-und-Raeder_w10041/">Alufelgen & Räder</a>

    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 482, Column 119: character "&" is the first character of a delimiter but occurred as data
    …fen-w5369/Felgen-und-Raederkonfigurator_w11634/">Felgen & Räderkonfigurator</a>

    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 490, Column 117: character "&" is the first character of a delimiter but occurred as data
    …Raeder-und-Reifen-w5369/Stahlfelgen-und-Raeder_w10040/">Stahlfelgen & Räder</a>

    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 510, Column 118: character "&" is the first character of a delimiter but occurred as data
    …eder-und-Reifen-w5369/Ratgeber-Rad-und-Reifen_w6638/">Ratgeber Rad & Reifen</a>

    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 532, Column 116: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5369}…

    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 532, Column 138: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5369}/brand={continental}">…

    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 536, Column 116: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5369}…

    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 536, Column 138: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5369}/brand={michelin}">Mic…

    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 540, Column 116: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5369}…

    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 540, Column 138: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5369}/brand={nokian}">Nokia…

    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 544, Column 116: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5369}…

    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 544, Column 138: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5369}/brand={goodyear}">Goo…

    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 548, Column 116: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5369}…

    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 548, Column 138: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5369}/brand={uniroyal}">Uni…

    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 552, Column 116: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5369}…

    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 552, Column 138: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5369}/brand={barum}">Barum<…

    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 556, Column 116: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5369}…

    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 556, Column 138: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5369}/brand={pirelli}">Pire…

    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 560, Column 116: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5369}…

    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 560, Column 138: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5369}/brand={bridgestone}">…

    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 564, Column 116: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5369}…

    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 564, Column 138: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5369}/brand={firestone}">Fi…

    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 568, Column 116: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5369}…

    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 568, Column 138: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5369}/brand={rigdon}">Rigdo…

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

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 664, Column 97: character "&" is the first character of a delimiter but occurred as data
    …gorie/OEle-w5532/Getriebe-und-Hydraulikoele_w5566/">Getriebe & Hydrauliköle</a>

    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 690, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 690, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/brand={castrol}">Cast…

    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 694, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 694, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/brand={shell}">Shell<…

    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 698, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 698, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/brand={liqui20moly}">…

    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 702, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 702, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/brand={mobil}">Mobil<…

    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 706, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 706, Column 118: character "<" is the first character of a delimiter but occurred as data
    …t/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/brand={atu}">ATU</a>

    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 716, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 716, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/viskositaet={0w2d30}"…

    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 720, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 720, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/viskositaet={0w2d40}"…

    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 724, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 724, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/viskositaet={5w2d30}"…

    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 728, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 728, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/viskositaet={5w2d40}"…

    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 732, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 732, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/viskositaet={10w2d60}…

    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 736, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 736, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/viskositaet={10w2d40}…

    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 740, Column 96: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5532}…

    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 740, Column 118: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5532}/viskositaet={15w2d40}…

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

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 846, Column 101: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5722}…

    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 846, Column 123: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5722}/brand={arktis}">Arkti…

    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 850, Column 101: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5722}…

    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 850, Column 123: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5722}/brand={varta}">Varta<…

    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 854, Column 101: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5722}…

    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 854, Column 123: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5722}/brand={banner}">Banne…

    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 858, Column 101: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5722}…

    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 858, Column 123: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5722}/brand={ctek}">CTEK</a…

    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 896, Column 97: character "&" is the first character of a delimiter but occurred as data
    …href="/online-shop/kategorie/Reise-und-Transport_w11621/">Reise & Transport</a>

    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 944, Column 109: character "&" is the first character of a delimiter but occurred as data
    …eise-und-Transport-w11621/Anhaenger-und-Zubehoer_w5796/">Anhänger & Zubehör</a>

    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 970, Column 112: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11621…

    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 970, Column 134: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_11621}/brand={thule}">Thule…

    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 974, Column 112: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11621…

    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 974, Column 134: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_11621}/brand={atera}">Atera…

    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 978, Column 112: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11621…

    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 978, Column 134: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_11621}/brand={stedele}">Ste…

    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 982, Column 112: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11621…

    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 982, Column 134: character "<" is the first character of a delimiter but occurred as data
    …/de_DE/categories<{root_atu}/categories<{root_atu_w_11621}/brand={eal}">EAL</a>

    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 986, Column 112: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11621…

    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 986, Column 134: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_11621}/brand={alkar}">Alkar…

    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 990, Column 112: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11621…

    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 990, Column 134: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_11621}/brand={al2dko}">AL-K…

    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 1068, Column 102: cannot generate system identifier for general entity "Buggys"
    …ategorie/Kinderwelt-w11622/KinderwagenundBuggys_w11011/">Kinderwagen&Buggys</a>

    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 1068, Column 102: general entity "Buggys" not defined and no default entity
    …ategorie/Kinderwelt-w11622/KinderwagenundBuggys_w11011/">Kinderwagen&Buggys</a>

    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 1068, Column 108: reference not terminated by REFC delimiter
    …ategorie/Kinderwelt-w11622/KinderwagenundBuggys_w11011/">Kinderwagen&Buggys</a>

    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 1068, Column 108: reference to entity "Buggys" for which no system identifier could be generated
    …ategorie/Kinderwelt-w11622/KinderwagenundBuggys_w11011/">Kinderwagen&Buggys</a>

    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 1068, Column 101: entity was defined here
    …ategorie/Kinderwelt-w11622/KinderwagenundBuggys_w11011/">Kinderwagen&Buggys</a>
  • Warning Line 1122, Column 103: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11622…

    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 1122, Column 125: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_11622}/brand={cybex}">Cybex…

    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 1126, Column 103: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11622…

    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 1126, Column 125: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_11622}/brand={maxi2dcosi}">…

    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 1130, Column 103: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11622…

    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 1130, Column 125: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_11622}/brand={concord}">Con…

    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 1134, Column 103: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11622…

    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 1134, Column 125: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_11622}/brand={kaufmann}">Ka…

    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 1138, Column 103: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11622…

    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 1138, Column 125: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_11622}/brand={osann}">Osann…

    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 1142, Column 103: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11622…

    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 1142, Column 125: character "<" is the first character of a delimiter but occurred as data
    …/de_DE/categories<{root_atu}/categories<{root_atu_w_11622}/brand={iwh}">IWH</a>

    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 1216, Column 119: character "&" is the first character of a delimiter but occurred as data
    …20/Autopflege-Wartung-und-Reparatur_w5751/">Autopflege, Wartung & Reparatur</a>

    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 1244, Column 107: character "&" is the first character of a delimiter but occurred as data
    …ehoer-w10020/Pannenhilfe-und-Erste-Hilfe_w10776/">Pannenhilfe & Erste Hilfe</a>

    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 1248, Column 86: character "&" is the first character of a delimiter but occurred as data
    …online-shop/kategorie/Zubehoer-w10020/EM-und-Fussball_w11509/">EM & Fußball</a>

    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 1274, Column 101: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_10020…

    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 1274, Column 123: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_10020}/brand={schoenek}">Sc…

    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 1278, Column 101: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_10020…

    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 1278, Column 123: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_10020}/brand={raida}">Raida…

    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 1282, Column 101: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_10020…

    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 1282, Column 123: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_10020}/brand={diana}">Diana…

    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 1286, Column 101: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_10020…

    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 1286, Column 123: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_10020}/brand={ctek}">CTEK</…

    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 1290, Column 101: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_10020…

    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 1290, Column 123: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_10020}/brand={sonax}">Sonax…

    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 1364, Column 91: character "&" is the first character of a delimiter but occurred as data
    …line-shop/kategorie/Zweiraeder-w5601/Roller-und-mehr_w10060/">Roller & mehr</a>

    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 1368, Column 95: character "&" is the first character of a delimiter but occurred as data
    …kategorie/Zweiraeder-w5601/Helme-und-Bekleidung_w11191/">Helme & Bekleidung</a>

    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 1372, Column 101: character "&" is the first character of a delimiter but occurred as data
    …egorie/Zweiraeder-w5601/Fahrraeder-und-Zubehoer_w5776/">Fahrräder & Zubehör</a>

    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 1390, Column 102: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5601}…

    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 1390, Column 124: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5601}/brand={castrol}">Cast…

    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 1394, Column 102: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5601}…

    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 1394, Column 124: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5601}/brand={explorer}">Exp…

    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 1398, Column 102: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5601}…

    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 1398, Column 124: character "<" is the first character of a delimiter but occurred as data
    …t/de_DE/categories<{root_atu}/categories<{root_atu_w_5601}/brand={ksr}">KSR</a>

    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 1402, Column 102: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5601}…

    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 1402, Column 124: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5601}/brand={uvex}">Uvex</a…

    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 1406, Column 102: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5601}…

    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 1406, Column 124: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5601}/brand={prophete}">Pro…

    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 1420, Column 155: character "&" is the first character of a delimiter but occurred as data
    …efault">Nur online ++ 20% auf Roller- & Motorradhelme ++ Nur bis 31.01.2013</a…

    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 1424, Column 153: character "&" is the first character of a delimiter but occurred as data
    …efault">Nur online ++ 20% auf Roller- & Motorradbatterien ++ Nur bis 31.01.201…

    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 1456, Column 95: character "&" is the first character of a delimiter but occurred as data
    … href="/online-shop/kategorie/Hifi-und-Navigation_w5046/">Hifi & Navigation</a>

    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 1504, Column 99: character "&" is the first character of a delimiter but occurred as data
    …gorie/Hifi-und-Navigation-w5046/DVD-und-Multimedia_w6577/">DVD & Multimedia</a>

    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 1508, Column 119: character "&" is the first character of a delimiter but occurred as data
    …ation-w5046/Lautsprecher-und-Verstaerker_w10773/">Lautsprecher & Verstärker</a>

    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 1530, Column 111: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5046}…

    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 1530, Column 133: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5046}/brand={tomtom}">TomTo…

    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 1534, Column 111: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5046}…

    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 1534, Column 133: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5046}/brand={garmin}">Garmi…

    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 1538, Column 111: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5046}…

    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 1538, Column 133: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5046}/brand={parrot}">Parro…

    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 1542, Column 111: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5046}…

    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 1542, Column 133: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5046}/brand={pioneer}">Pion…

    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 1546, Column 111: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5046}…

    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 1546, Column 133: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5046}/brand={magnat}">Magna…

    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 1620, Column 102: character "&" is the first character of a delimiter but occurred as data
    …ie/Tuning-w5359/Car-Styling-und-Peformance_w5386/">Car Styling & Peformance</a>

    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 1640, Column 91: character "&" is the first character of a delimiter but occurred as data
    …shop/kategorie/Tuning-w5359/Folien-und-Aufkleber_w5614/">Folien & Aufkleber</a>

    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 1652, Column 106: character "&" is the first character of a delimiter but occurred as data
    …-w5359/Alufelgen--und-Komplettradshop_w10684/">Alufelgen- & Komplettradshop</a>

    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 1666, Column 98: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5359}…

    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 1666, Column 120: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5359}/brand={foliatec}">Fol…

    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 1670, Column 98: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5359}…

    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 1670, Column 120: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5359}/brand={raid}">raid</a…

    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 1674, Column 98: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5359}…

    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 1674, Column 120: character "<" is the first character of a delimiter but occurred as data
    …t/de_DE/categories<{root_atu}/categories<{root_atu_w_5359}/brand={jom}">Jom</a>

    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 1678, Column 98: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5359}…

    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 1678, Column 120: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5359}/brand={in2epro2e}">in…

    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 1682, Column 98: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5359}…

    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 1682, Column 120: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5359}/brand={remus}">Remus<…

    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 1686, Column 98: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_5359}…

    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 1686, Column 120: character "<" is the first character of a delimiter but occurred as data
    …de_DE/categories<{root_atu}/categories<{root_atu_w_5359}/brand={vogtland}">Vog…

    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 1798, Column 101: character "<" is the first character of a delimiter but occurred as data
    …ms=fh_location=//root/de_DE/categories<{root_atu}/categories<{root_atu_w_11626…

    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 1798, Column 123: character "<" is the first character of a delimiter but occurred as data
    …/de_DE/categories<{root_atu}/categories<{root_atu_w_11626}/brand={atu}">ATU</a>

    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 1839, Column 25: end tag for element "tr" which is not open
                        </tr>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1840, Column 24: end tag for element "table" which is not open
                    </table>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1868, Column 84: document type does not allow element "link" here
    …ink href="/de/resources/css/fredhopper.css" rel="stylesheet" type="text/css" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 1962, Column 65: required attribute "alt" not specified
    				<img src="/de/content/static/fh_gfx/kampagnen/spacer.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 1980, Column 81: document type does not allow element "link" here
    …link rel="stylesheet" href="/de/resources/css/layerslider.css" type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 1980, Column 82: end tag for "link" omitted, but OMITTAG NO was specified
    …link rel="stylesheet" href="/de/resources/css/layerslider.css" type="text/css">

    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 1980, Column 2: start tag was here
    	<link rel="stylesheet" href="/de/resources/css/layerslider.css" type="text/css…
  • Error Line 1990, Column 207: end tag for "img" omitted, but OMITTAG NO was specified
    ….de/de/gfx/fh_gfx/banner/2013/februar1/FH_30_Winterreifen.jpg" alt="layer"></a>

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

  • Info Line 1990, Column 104: start tag was here
    …-und-Reifen-w5369/WSV-Reifen_w11672/"><img src="http://webt.atu.de/de/gfx/fh_g…
  • Error Line 1996, Column 223: end tag for "img" omitted, but OMITTAG NO was specified
    …atu.de/de/gfx/fh_gfx/banner/2013/februar1/FH_50_Alufelgen.jpg" alt="layer"></a>

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

  • Info Line 1996, Column 123: start tag was here
    …elgen-und-Raederkonfigurator_w11634/"><img src="http://webt.atu.de/de/gfx/fh_g…
  • Error Line 2002, Column 226: end tag for "img" omitted, but OMITTAG NO was specified
    ….de/de/gfx/fh_gfx/banner/2013/februar1/FH_20_Schneeketten.jpg" alt="layer"></a>

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

  • Info Line 2002, Column 123: start tag was here
    …adzubehoer-w5590/Schneeketten_w5600/"><img src="http://webt.atu.de/de/gfx/fh_g…
  • Error Line 2008, Column 218: end tag for "img" omitted, but OMITTAG NO was specified
    …de/de/gfx/fh_gfx/banner/2013/februar1/FH_50_Stossdaempfer.jpg" alt="layer"></a>

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

  • Info Line 2008, Column 114: start tag was here
    …teile-w5451/Autoteile-Katalog_w5962/"><img src="http://webt.atu.de/de/gfx/fh_g…
  • Error Line 2014, Column 159: end tag for "img" omitted, but OMITTAG NO was specified
    …t.atu.de/de/gfx/fh_gfx/banner/2012/Oktober2/FH_newsletter.jpg" alt="layer"></a>

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

  • Info Line 2014, Column 61: start tag was here
    … href="/pages/common/newsletter.html"><img src="http://webt.atu.de/de/gfx/fh_g…
  • Error Line 2044, Column 29: document type does not allow element "div" here; assuming missing "li" start-tag
    				<div style="clear:both;"></div>
  • Error Line 2045, Column 8: end tag for "li" omitted, but OMITTAG NO was specified
    			</ul>

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

  • Info Line 2044, Column 5: start tag was here
    				<div style="clear:both;"></div>
  • Error Line 2150, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2151, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/HN0_/HN0018_100.jpg" style="cursor:pointer;"/>

    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 2175, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2176, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/FS4_/FS4156_100.jpg" style="cursor:pointer;"/>

    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 2200, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2201, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/PM8_/PM8991_100.jpg" style="cursor:pointer;"/>

    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 2225, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2226, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/FA0_/FA0530_100.jpg" style="cursor:pointer;"/>

    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 2250, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2251, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/TY0_/TY055E_100.jpg" style="cursor:pointer;"/>

    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 2275, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2276, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/FS4_/FS4206_100.jpg" style="cursor:pointer;"/>

    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 2300, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2301, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/FS2_/FS2011_100.jpg" style="cursor:pointer;"/>

    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 2325, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2326, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/WE0_/WE0010_100.jpg" style="cursor:pointer;"/>

    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 2350, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2351, Column 54: cannot generate system identifier for general entity "size"
    …		<img src="/atu/control/img?vknid=11929166&size=100" style="cursor:pointer;"/>

    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 2351, Column 54: general entity "size" not defined and no default entity
    …		<img src="/atu/control/img?vknid=11929166&size=100" style="cursor:pointer;"/>

    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 2351, Column 58: reference not terminated by REFC delimiter
    …		<img src="/atu/control/img?vknid=11929166&size=100" style="cursor:pointer;"/>

    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 2351, Column 58: reference to external entity in attribute value
    …		<img src="/atu/control/img?vknid=11929166&size=100" style="cursor:pointer;"/>

    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 2351, Column 58: reference to entity "size" for which no system identifier could be generated
    …		<img src="/atu/control/img?vknid=11929166&size=100" style="cursor:pointer;"/>

    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 2351, Column 53: entity was defined here
    …		<img src="/atu/control/img?vknid=11929166&size=100" style="cursor:pointer;"/>
  • Error Line 2351, Column 88: required attribute "alt" not specified
    …		<img src="/atu/control/img?vknid=11929166&size=100" style="cursor:pointer;"/>

    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 2375, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2376, Column 57: reference not terminated by REFC delimiter
    …			<img src="/atu/control/img?vknid=1006023&size=100" style="cursor:pointer;"/>

    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 2376, Column 57: reference to external entity in attribute value
    …			<img src="/atu/control/img?vknid=1006023&size=100" style="cursor:pointer;"/>

    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 2376, Column 57: reference to entity "size" for which no system identifier could be generated
    …			<img src="/atu/control/img?vknid=1006023&size=100" style="cursor:pointer;"/>

    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 2351, Column 53: entity was defined here
    …		<img src="/atu/control/img?vknid=11929166&size=100" style="cursor:pointer;"/>
  • Error Line 2376, Column 87: required attribute "alt" not specified
    …			<img src="/atu/control/img?vknid=1006023&size=100" style="cursor:pointer;"/>

    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 2400, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2401, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/IC0_/IC0988_100.jpg" style="cursor:pointer;"/>

    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 2425, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2426, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/BON_/BON262_100.jpg" style="cursor:pointer;"/>

    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 2450, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2451, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/FS1_/FS1183_100.jpg" style="cursor:pointer;"/>

    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 2475, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2476, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/PM9_/PM9035_100.jpg" style="cursor:pointer;"/>

    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 2500, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2501, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/PRO_/PRO107_100.jpg" style="cursor:pointer;"/>

    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 2525, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2526, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/IC0_/IC0427_100.jpg" style="cursor:pointer;"/>

    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 2550, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2551, Column 82: required attribute "alt" not specified
    …								<img src="/gfx/Nokian_WR_D3_2455_561_100.jpg" style="cursor:pointer;"/>

    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 2575, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2576, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/PM8_/PM8679_100.jpg" style="cursor:pointer;"/>

    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 2600, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2601, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/IC3_/IC3709_100.jpg" style="cursor:pointer;"/>

    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 2625, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2626, Column 87: required attribute "alt" not specified
    …			<img src="/gfx/Uniroyal_MS_plus_6_865_108_100.jpg" style="cursor:pointer;"/>

    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 2650, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2651, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/SKT_/SKT300_100.jpg" style="cursor:pointer;"/>

    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 2675, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2676, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/ROF_/ROF424_100.jpg" style="cursor:pointer;"/>

    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 2700, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2701, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/OM0_/OM0106_100.jpg" style="cursor:pointer;"/>

    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 2725, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="img-wrapper">

    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 2726, Column 87: required attribute "alt" not specified
    …			<img src="/extern/gfx/artikel/SKT_/SKT315_100.jpg" style="cursor:pointer;"/>

    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 3284, Column 69: there is no attribute "onChange"
    …cbxFahrzeugart" id="cbxFahrzeugart10" onChange="FAChanged10(this.form, true);">

    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 3285, Column 36: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    							<option value="pkw" selected>PKW</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 3295, Column 37: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    								<option value="2"  selected >Winterreifen</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 3303, Column 129: duplicate specification of attribute "style"
    …cbxReifenbreite10" onchange="RBChanged10(this.form, true)" style="width:58px;">

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

  • Error Line 3304, Column 16: end tag for "select" which is not finished
    							</select>

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

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

  • Error Line 3305, Column 127: duplicate specification of attribute "style"
    …"cbxQuerschnitt10" onchange="QSChanged10(this.form, true)" style="width:52px;">

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

  • Error Line 3306, Column 16: end tag for "select" which is not finished
    							</select>

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

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

  • Error Line 3310, Column 139: duplicate specification of attribute "style"
    …lgendurchmesser10" onchange="FDChanged10(this.form, true)" style="width:52px;">

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

  • Error Line 3311, Column 16: end tag for "select" which is not finished
    							</select>

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

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

  • Error Line 3312, Column 123: duplicate specification of attribute "style"
    …d="cbxLastindex10" onchange="LIChanged10(this.form, true)" style="width:52px;">

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

  • Error Line 3313, Column 16: end tag for "select" which is not finished
    							</select>

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

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

  • Error Line 3314, Column 101: duplicate specification of attribute "style"
    …="cbxSpeedindex"  id="cbxSpeedindex10" style="width:129px;margin-right: 10px;">

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

  • Error Line 3315, Column 16: end tag for "select" which is not finished
    							</select>

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

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

  • Error Line 3322, Column 33: required attribute "id" not specified
    						<map name="Map_Reifenbild">

    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 3323, Column 156: required attribute "alt" not specified
    …avascript:void(0)" onmouseover="Tip('Reifenbreite (mm)')" onmouseout="UnTip()">

    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 3323, Column 157: end tag for "area" omitted, but OMITTAG NO was specified
    …avascript:void(0)" onmouseover="Tip('Reifenbreite (mm)')" onmouseout="UnTip()">

    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 3323, Column 8: start tag was here
    							<area shape="poly" coords="26,80,31,91,64,91,88,80,85,55"      href="jav…
  • Error Line 3324, Column 168: required attribute "alt" not specified
    … onmouseover="Tip('Querschnittsverh&auml;ltnis H/B (%)')" onmouseout="UnTip()">

    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 3324, Column 169: end tag for "area" omitted, but OMITTAG NO was specified
    … onmouseover="Tip('Querschnittsverh&auml;ltnis H/B (%)')" onmouseout="UnTip()">

    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 3324, Column 8: start tag was here
    							<area shape="poly" coords="88,55,93,81,126,76,125,50"    href="javascrip…
  • Error Line 3325, Column 155: required attribute "alt" not specified
    …ript:void(0)" onmouseover="Tip('Bauart-Code (R=Radial)')" onmouseout="UnTip()">

    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 3325, Column 156: end tag for "area" omitted, but OMITTAG NO was specified
    …ript:void(0)" onmouseover="Tip('Bauart-Code (R=Radial)')" onmouseout="UnTip()">

    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 3325, Column 8: start tag was here
    							<area shape="poly" coords="125,52,125,76,147,76,148,52"  href="javascrip…
  • Error Line 3326, Column 174: required attribute "alt" not specified
    …seover="Tip('Felgendurchmesser (Zoll-Gr&ouml;&szlig;e)')" onmouseout="UnTip()">

    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 3326, Column 175: end tag for "area" omitted, but OMITTAG NO was specified
    …seover="Tip('Felgendurchmesser (Zoll-Gr&ouml;&szlig;e)')" onmouseout="UnTip()">

    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 3326, Column 8: start tag was here
    							<area shape="poly" coords="152,52,152,77,179,80,186,55"  href="javascrip…
  • Error Line 3327, Column 173: required attribute "alt" not specified
    …useover="Tip('Tragf&auml;higkeitskennzahl (Load-Index)')" onmouseout="UnTip()">

    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 3327, Column 174: end tag for "area" omitted, but OMITTAG NO was specified
    …useover="Tip('Tragf&auml;higkeitskennzahl (Load-Index)')" onmouseout="UnTip()">

    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 3327, Column 8: start tag was here
    							<area shape="poly" coords="188,57,183,80,209,87,218,65"  href="javascrip…
  • Error Line 3328, Column 169: required attribute "alt" not specified
    …nmouseover="Tip('Geschwindigkeits-Symbol (Speed-Index)')" onmouseout="UnTip()">

    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 3328, Column 170: end tag for "area" omitted, but OMITTAG NO was specified
    …nmouseover="Tip('Geschwindigkeits-Symbol (Speed-Index)')" onmouseout="UnTip()">

    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 3328, Column 8: start tag was here
    							<area shape="poly" coords="220,67,211,91,233,91,238,73" href="javascript…
  • Error Line 3331, Column 89: required attribute "alt" not specified
    …g src="/de/resources/gfx/layout/legend-reifen2.png" usemap="#Map_Reifenbild" />

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

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

  • Warning Line 3348, Column 64: cannot generate system identifier for general entity "sortingby"
    …hop/kategorie/?searchterm=sommerreifen&sortingby=-$rc_default">Sommerreifen</a>

    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 3348, Column 64: general entity "sortingby" not defined and no default entity
    …hop/kategorie/?searchterm=sommerreifen&sortingby=-$rc_default">Sommerreifen</a>

    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 3348, Column 73: reference not terminated by REFC delimiter
    …hop/kategorie/?searchterm=sommerreifen&sortingby=-$rc_default">Sommerreifen</a>

    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 3348, Column 73: reference to external entity in attribute value
    …hop/kategorie/?searchterm=sommerreifen&sortingby=-$rc_default">Sommerreifen</a>

    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 3348, Column 73: reference to entity "sortingby" for which no system identifier could be generated
    …hop/kategorie/?searchterm=sommerreifen&sortingby=-$rc_default">Sommerreifen</a>

    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 3348, Column 63: entity was defined here
    …hop/kategorie/?searchterm=sommerreifen&sortingby=-$rc_default">Sommerreifen</a…
  • Error Line 3351, Column 20: there is no attribute "itemtype"
    					<div itemtype="http://schema.org/Product" itemscope="" class="productbox">

    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 3351, Column 58: there is no attribute "itemscope"
    					<div itemtype="http://schema.org/Product" itemscope="" class="productbox">

    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 3355, Column 24: there is no attribute "itemprop"
    									<img itemprop="image" title="" alt="" src="/gfx/Uniroyal_Rain_Expert_8…

    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 3355, Column 139: end tag for "img" omitted, but OMITTAG NO was specified
    …iroyal_Rain_Expert_865_96_100.jpg" style="max-width: 100px; max-height: 100px">

    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 3355, Column 10: start tag was here
    									<img itemprop="image" title="" alt="" src="/gfx/Uniroyal_Rain_Expert_8…
  • Error Line 3358, Column 95: there is no attribute "itemprop"
    …al-Rain-Expert-19565-R15-91V-Sommerreifen-UN1101" itemprop="name" class="name">

    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 3365, Column 35: there is no attribute "itemprop"
    						<div class="price" itemprop="offers" itemscope itemtype="http://schema.or…

    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 3365, Column 54: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 3373, Column 41: there is no attribute "itemprop"
    …							<p class="pricevalue" itemprop="price">58,81<span class="euro">&euro;</…

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

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

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

  • Warning Line 3412, Column 73: reference not terminated by REFC delimiter
    …hop/kategorie/?searchterm=sommerreifen&sortingby=-$rc_default">Sommerreifen</a>

    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 3412, Column 73: reference to external entity in attribute value
    …hop/kategorie/?searchterm=sommerreifen&sortingby=-$rc_default">Sommerreifen</a>

    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 3412, Column 73: reference to entity "sortingby" for which no system identifier could be generated
    …hop/kategorie/?searchterm=sommerreifen&sortingby=-$rc_default">Sommerreifen</a>

    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 3348, Column 63: entity was defined here
    …hop/kategorie/?searchterm=sommerreifen&sortingby=-$rc_default">Sommerreifen</a…
  • Error Line 3419, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …"" src="/extern/gfx/fbs/k-115.JPG" style="max-width: 100px; max-height: 100px">

    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 3419, Column 10: start tag was here
    									<img itemprop="image" title="" alt="" src="/extern/gfx/fbs/k-115.JPG" …
  • Error Line 3429, Column 54: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 3547, Column 63: end tag for "input" omitted, but OMITTAG NO was specified
    									<input type="text" name="zu2" maxlength="4" value=""> 

    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 3547, Column 10: start tag was here
    									<input type="text" name="zu2" maxlength="4" value=""> 
  • Error Line 3549, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    									<input type="text"  name="zu3" maxlength="3" value=""> 

    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 3549, Column 10: start tag was here
    									<input type="text"  name="zu3" maxlength="3" value=""> 
  • Error Line 3715, Column 138: end tag for "img" omitted, but OMITTAG NO was specified
    …n/gfx/artikel/1ON_/1ONL02_100.jpg" style="max-width: 100px; max-height: 100px">

    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 3715, Column 10: start tag was here
    									<img itemprop="image" title="" alt="" src="/extern/gfx/artikel/1ON_/1O…
  • Error Line 3725, Column 54: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 3771, Column 138: end tag for "img" omitted, but OMITTAG NO was specified
    …n/gfx/artikel/1ON_/1ONL07_100.jpg" style="max-width: 100px; max-height: 100px">

    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 3771, Column 10: start tag was here
    									<img itemprop="image" title="" alt="" src="/extern/gfx/artikel/1ON_/1O…
  • Error Line 3781, Column 54: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Warning Line 3836, Column 18: character "&" is the first character of a delimiter but occurred as data
    		if (sZu2 == "" && sZu3 == "")

    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 3836, Column 19: character "&" is the first character of a delimiter but occurred as data
    		if (sZu2 == "" && sZu3 == "")

    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 3844, Column 20: character "<" is the first character of a delimiter but occurred as data
    			if (sZu2.length < 4)

    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 3849, Column 20: character "<" is the first character of a delimiter but occurred as data
    			if (sZu3.length < 3)

    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 3855, Column 73: character "&" is the first character of a delimiter but occurred as data
    			document.frmEkatGetData11.action="/pages/shop/ekat/ekat.html?todo=set&"

    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 3857, Column 9: cannot generate system identifier for general entity "selModell"
    				+ "&selModell=" + sModell

    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 3857, Column 9: general entity "selModell" not defined and no default entity
    				+ "&selModell=" + sModell

    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 3857, Column 18: reference not terminated by REFC delimiter
    				+ "&selModell=" + sModell

    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 3857, Column 18: reference to entity "selModell" for which no system identifier could be generated
    				+ "&selModell=" + sModell

    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 3857, Column 8: entity was defined here
    				+ "&selModell=" + sModell
  • Warning Line 3858, Column 9: cannot generate system identifier for general entity "zu2"
    				+ "&zu2=" + sZu2

    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 3858, Column 9: general entity "zu2" not defined and no default entity
    				+ "&zu2=" + sZu2

    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 3858, Column 12: reference not terminated by REFC delimiter
    				+ "&zu2=" + sZu2

    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 3858, Column 12: reference to entity "zu2" for which no system identifier could be generated
    				+ "&zu2=" + sZu2

    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 3858, Column 8: entity was defined here
    				+ "&zu2=" + sZu2
  • Warning Line 3859, Column 9: cannot generate system identifier for general entity "zu3"
    				+ "&zu3=" + sZu3

    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 3859, Column 9: general entity "zu3" not defined and no default entity
    				+ "&zu3=" + sZu3

    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 3859, Column 12: reference not terminated by REFC delimiter
    				+ "&zu3=" + sZu3

    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 3859, Column 12: reference to entity "zu3" for which no system identifier could be generated
    				+ "&zu3=" + sZu3

    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 3859, Column 8: entity was defined here
    				+ "&zu3=" + sZu3
  • Warning Line 3884, Column 73: character "&" is the first character of a delimiter but occurred as data
    			document.frmEkatGetData11.action="/pages/shop/ekat/ekat.html?todo=set&"

    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 3886, Column 18: reference not terminated by REFC delimiter
    				+ "&selModell=" + sModell

    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 3886, Column 18: reference to entity "selModell" for which no system identifier could be generated
    				+ "&selModell=" + sModell

    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 3857, Column 8: entity was defined here
    				+ "&selModell=" + sModell
  • Warning Line 3887, Column 12: reference not terminated by REFC delimiter
    				+ "&zu2=" + sZu2

    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 3887, Column 12: reference to entity "zu2" for which no system identifier could be generated
    				+ "&zu2=" + sZu2

    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 3858, Column 8: entity was defined here
    				+ "&zu2=" + sZu2
  • Warning Line 3888, Column 12: reference not terminated by REFC delimiter
    				+ "&zu3=" + sZu3

    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 3888, Column 12: reference to entity "zu3" for which no system identifier could be generated
    				+ "&zu3=" + sZu3

    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 3859, Column 8: entity was defined here
    				+ "&zu3=" + sZu3
  • Warning Line 3908, Column 15: character "<" is the first character of a delimiter but occurred as data
    			for(i=0; i < response.daten.kfzmodelldaten.length; i++)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 3956, Column 41: "itemscope" is not a member of a group specified for any attribute
    						<div class="productbox" itemscope itemtype="http://schema.org/Product">
  • Error Line 3960, Column 124: required attribute "alt" not specified
    …JB320A_100.jpg" style="max-width: 100px; max-height: 100px" itemprop="image" />

    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 3969, Column 55: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 3991, Column 41: "itemscope" is not a member of a group specified for any attribute
    						<div class="productbox" itemscope itemtype="http://schema.org/Product">
  • Error Line 3995, Column 124: required attribute "alt" not specified
    …AB0009_100.jpg" style="max-width: 100px; max-height: 100px" itemprop="image" />

    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 4004, Column 55: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 4026, Column 41: "itemscope" is not a member of a group specified for any attribute
    						<div class="productbox" itemscope itemtype="http://schema.org/Product">
  • Error Line 4030, Column 126: required attribute "alt" not specified
    …T00066_100.jpg" style="max-width: 100px; max-height: 100px" itemprop="image" />

    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 4039, Column 55: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 4061, Column 41: "itemscope" is not a member of a group specified for any attribute
    						<div class="productbox" itemscope itemtype="http://schema.org/Product">
  • Error Line 4065, Column 124: required attribute "alt" not specified
    …FZ9507_100.jpg" style="max-width: 100px; max-height: 100px" itemprop="image" />

    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 4074, Column 55: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 4124, Column 42: "itemscope" is not a member of a group specified for any attribute
    							<div class="productbox" itemscope itemtype="http://schema.org/Product">
  • Error Line 4128, Column 125: required attribute "alt" not specified
    …TAY804_100.jpg" style="max-width: 100px; max-height: 100px" itemprop="image" />

    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 4137, Column 56: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 4176, Column 42: "itemscope" is not a member of a group specified for any attribute
    							<div class="productbox" itemscope itemtype="http://schema.org/Product">
  • Error Line 4180, Column 125: required attribute "alt" not specified
    …TAM007_100.jpg" style="max-width: 100px; max-height: 100px" itemprop="image" />

    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 4189, Column 56: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 4228, Column 42: "itemscope" is not a member of a group specified for any attribute
    							<div class="productbox" itemscope itemtype="http://schema.org/Product">
  • Error Line 4232, Column 125: required attribute "alt" not specified
    …TAY860_100.jpg" style="max-width: 100px; max-height: 100px" itemprop="image" />

    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 4241, Column 56: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 4280, Column 42: "itemscope" is not a member of a group specified for any attribute
    							<div class="productbox" itemscope itemtype="http://schema.org/Product">
  • Error Line 4284, Column 125: required attribute "alt" not specified
    …TAY900_100.jpg" style="max-width: 100px; max-height: 100px" itemprop="image" />

    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 4293, Column 56: "itemscope" is not a member of a group specified for any attribute
    …v class="price" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Warning Line 4350, Column 931: character "&" is the first character of a delimiter but occurred as data
    …><br />In der Kategorie Felgen, Räder & Reifen erhalten Sie ein großes Produkt…

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

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

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

  • Error Line 4388, Column 18: there is no attribute "class"
    				<aside class="rightcol start">

    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 4388, Column 34: element "aside" undefined
    				<aside class="rightcol start">

    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 4443, Column 22: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					<p class="small"><span class="bold">keine Versandkosten</span><br />innerh…

    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 4562, Column 91: cannot generate system identifier for general entity "catalogID"
    …rt/k0jRgqeCPE3L/scv.html?mode=catalog&catalogID=4635&campaignID=4641&width=945…

    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 4562, Column 91: general entity "catalogID" not defined and no default entity
    …rt/k0jRgqeCPE3L/scv.html?mode=catalog&catalogID=4635&campaignID=4641&width=945…

    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 4562, Column 100: reference not terminated by REFC delimiter
    …eCPE3L/scv.html?mode=catalog&catalogID=4635&campaignID=4641&width=945&height=6…

    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 4562, Column 100: reference to external entity in attribute value
    …eCPE3L/scv.html?mode=catalog&catalogID=4635&campaignID=4641&width=945&height=6…

    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 4562, Column 100: reference to entity "catalogID" for which no system identifier could be generated
    …eCPE3L/scv.html?mode=catalog&catalogID=4635&campaignID=4641&width=945&height=6…

    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 4562, Column 90: entity was defined here
    …ort/k0jRgqeCPE3L/scv.html?mode=catalog&catalogID=4635&campaignID=4641&width=94…
  • Warning Line 4562, Column 106: cannot generate system identifier for general entity "campaignID"
    …/scv.html?mode=catalog&catalogID=4635&campaignID=4641&width=945&height=670&bgc…

    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 4562, Column 106: general entity "campaignID" not defined and no default entity
    …/scv.html?mode=catalog&catalogID=4635&campaignID=4641&width=945&height=670&bgc…

    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 4562, Column 116: reference not terminated by REFC delimiter
    …mode=catalog&catalogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFF…

    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 4562, Column 116: reference to external entity in attribute value
    …mode=catalog&catalogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFF…

    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 4562, Column 116: reference to entity "campaignID" for which no system identifier could be generated
    …mode=catalog&catalogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFF…

    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 4562, Column 105: entity was defined here
    …L/scv.html?mode=catalog&catalogID=4635&campaignID=4641&width=945&height=670&bg…
  • Warning Line 4562, Column 122: cannot generate system identifier for general entity "width"
    …atalog&catalogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt…

    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 4562, Column 122: general entity "width" not defined and no default entity
    …atalog&catalogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt…

    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 4562, Column 127: reference not terminated by REFC delimiter
    …g&catalogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top…

    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 4562, Column 127: reference to external entity in attribute value
    …g&catalogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top…

    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 4562, Column 127: reference to entity "width" for which no system identifier could be generated
    …g&catalogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top…

    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 4562, Column 121: entity was defined here
    …catalog&catalogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" al…
  • Warning Line 4562, Column 132: cannot generate system identifier for general entity "height"
    …alogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Ange…

    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 4562, Column 132: general entity "height" not defined and no default entity
    …alogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Ange…

    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 4562, Column 138: reference not terminated by REFC delimiter
    …=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Angebote" …

    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 4562, Column 138: reference to external entity in attribute value
    …=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Angebote" …

    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 4562, Column 138: reference to entity "height" for which no system identifier could be generated
    …=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Angebote" …

    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 4562, Column 131: entity was defined here
    …talogID=4635&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Ang…
  • Warning Line 4562, Column 143: cannot generate system identifier for general entity "bgcolor"
    …&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Angebote" targe…

    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 4562, Column 143: general entity "bgcolor" not defined and no default entity
    …&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Angebote" targe…

    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 4562, Column 150: reference not terminated by REFC delimiter
    …gnID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Angebote" target="_bla…

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

  • Warning Line 4562, Column 150: reference to external entity in attribute value
    …gnID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Angebote" target="_bla…

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

  • Error Line 4562, Column 150: reference to entity "bgcolor" for which no system identifier could be generated
    …gnID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Angebote" target="_bla…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 4562, Column 142: entity was defined here
    …5&campaignID=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Angebote" targ…
  • Error Line 4562, Column 163: there is no attribute "alt"
    …=4641&width=945&height=670&bgcolor=FFFFFF" alt="Top Angebote" target="_blank" >

    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 4564, Column 65: required attribute "alt" not specified
    					<img src="/de/gfx/fh_gfx/teaser/teaser_topangebote_2.jpg" />

    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 4574, Column 65: required attribute "alt" not specified
    					<img src="/de/gfx/fh_gfx/teaser/teaser_versandkosten.jpg" />

    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 4584, Column 70: required attribute "alt" not specified
    					<img src="/de/gfx/fh_gfx/teaser/teaser_terminvereinbarung.jpg" />

    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 4594, Column 90: required attribute "alt" not specified
    …rc="http://webt.atu.de/de/gfx/fh_gfx/banner/2013/januar1/T_Schneeketten.jpg" />

    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 4604, Column 66: required attribute "alt" not specified
    					<img src="/de/gfx/fh_gfx/teaser/teaser_atu-newsletter.jpg" />

    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 4614, Column 60: required attribute "alt" not specified
    					<img src="/de/gfx/fh_gfx/teaser/teaser_atu-card.jpg" />

    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 4624, Column 73: required attribute "alt" not specified
    					<img src="/de/gfx/fh_gfx/teaser/teaser_alufelgen-komplettrad.jpg" />

    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 4634, Column 55: required attribute "alt" not specified
    					<img src="/de/gfx/fh_gfx/teaser/teaser_app.jpg" />

    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 4644, Column 58: required attribute "alt" not specified
    					<img src="/de/gfx/fh_gfx/teaser/teaser_atu-tv.jpg" />

    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 4654, Column 64: required attribute "alt" not specified
    					<img src="/de/gfx/fh_gfx/teaser/teaser_finanzierung.jpg" />

    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 4736, Column 9: element "footer" undefined
    	<footer>

    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 4830, Column 9: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    					<li>

    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 4833, Column 9: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    					<li>

    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 4836, Column 9: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    					<li>

    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 4839, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    					<li class="heading2">

    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 4842, Column 9: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    					<li>

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

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

  • Info Line 4828, Column 6: start tag was here
    					<li>
  • Error Line 4876, Column 11: end tag for "br" omitted, but OMITTAG NO was specified
    						<br><br>

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

  • Info Line 4876, Column 7: start tag was here
    						<br><br>
  • Error Line 4876, Column 15: end tag for "br" omitted, but OMITTAG NO was specified
    						<br><br>

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

  • Info Line 4876, Column 11: start tag was here
    						<br><br>
  • Error Line 4884, Column 31: element "nav" undefined
    			<nav class="footer-metanav">

    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).
  • Warning Line 4896, Column 33: character "&" is the first character of a delimiter but occurred as data
    						&copy; A.T.U Handels GmbH & Co KG

    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 4928, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
    	</footer>

    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 4739, Column 3: start tag was here
    		<div class="footer-bottom">
  • Error Line 4930, Column 6: end tag for element "div" which is not open
    </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 4996, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
    </html>

    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 126, Column 1: start tag was here
    <script type="text/javascript">
  • Error Line 4996, Column 8: "html" not finished but document ended
    </html>
  • Error Line 4996, Column 8: end tag for "html" omitted, but OMITTAG NO was specified
    </html>

    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 47, Column 1: start tag was here
    <html lang="de" >

Visitor Analysis

Daily Visitor
  • 7.350 visits