fischkopf.de

Partnersuche bei Fischkopf! Jetzt anmelden und kostenlos flirten bei Fischkopf.de der größten regionalen Singlebörse für Norddeutschland. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 08-02-2013 06:40:13  (update).

Overview Info

  • Domain Name
    fischkopf.de
  • Favicon
  • Alexa Rank
    #38160
  • Google Page Rank
    PR 4
  • Ip Address
    82.199.139.127
  • Page Size
    62.8 KB
  • Images
    10 GIF, 10 JPG, 4 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 9 0 3 0 0

Website Meta Analysis



  • Title
    Partnersuche bei Fischkopf! Singlebörse für Singles in Hamburg, Bremen, Hannover, Oldenburg, Kiel, Lübeck, Rostock und Norddeutschland
  • Meta Keyword
    Partnersuche, Singlebörse, Kontaktanzeigen, Er sucht Sie, Sie sucht Ihn, Singleparty, Partnerbörse
  • Meta Description
    Partnersuche bei Fischkopf! Jetzt anmelden und kostenlos flirten bei Fischkopf.de der größten regionalen Singlebörse für Norddeutschland.

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    82.199.139.127
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 08 Feb 2013 18:40:14 GMT
  • server: Apache
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • x-web: 1
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for fischkopf.de

DNS Analysis


DNS servers
ns1.wavedns.de
ns2.wavedns.de


DNS Records

Answer records
fischkopf.de SOA
server: ns1.wavedns.de
email: hostmaster@wavecon.de
serial: 2012112202
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
86400s
fischkopf.de NS  ns2.wavedns.de 86400s
fischkopf.de MX
preference: 20
exchange: groupware.wavecon.de
3600s
fischkopf.de A 82.199.139.127 300s
fischkopf.de NS  ns1.wavedns.de 86400s
fischkopf.de TXT v=spf1 mx ip4:81.95.6.209/32 ip4:81.95.6.210/32 ip4:81.95.6.226/32 ip4:81.95.6.227/32 ip4:82.199.139.118/32 ip4:82.199.139.119/32 ip4:82.199.139.120/32 ip4:82.199.139.121/32 ~all 3600s

Authority records

Additional records
ns1.wavedns.de A 81.95.6.52 3600s
groupware.wavecon.de A 81.95.6.39 3600s
ns2.wavedns.de A 81.169.141.170 3600s

IP 82.199.139.127 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    EU
  • Continent Code
    51° North
  • Latitude
    9.
  • Longitude
  • No whois ip data for 82.199.139.127

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 134 Errors
  • 109 Warnings
Ratio Text/Html
  • 0.48791444515256555
Message Error
  • Error Line 2, Column 106: end tag for "html" which is not finished
    …org/1999/xhtml" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://ogp.me/ns/fb#" />

    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 2, Column 106: end tag for "html" which is not finished
    …org/1999/xhtml" xmlns:og="http://ogp.me/ns#" xmlns:fb="http://ogp.me/ns/fb#" />

    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 4, Column 6: document type does not allow element "head" here
    <head>

    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 13, Column 16: there is no attribute "property"
    <meta property="og:type" content="article" />

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

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

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

  • Error Line 40, Column 18: there is no attribute "language"
    <script language="JavaScript" type="text/javascript" src="/jscript/javascripts_…

    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 42, 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 43, Column 43: document type does not allow element "style" here
       <div id="seite"> <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 205, Column 48: cannot generate system identifier for general entity "cat_no"
    …   <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie suc…

    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 205, Column 48: general entity "cat_no" not defined and no default entity
    …   <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie suc…

    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 205, Column 54: reference not terminated by REFC delimiter
    …href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie sucht Ihn…

    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 205, Column 54: reference to external entity in attribute value
    …href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie sucht Ihn…

    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 205, Column 54: reference to entity "cat_no" for which no system identifier could be generated
    …href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie sucht Ihn…

    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 205, Column 47: entity was defined here
    …    <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie su…
  • Warning Line 206, Column 54: reference not terminated by REFC delimiter
    …href="/index.php?page=kategorie&cat_no=3" title="Kontaktanzeigen Er sucht Sie"…

    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 206, Column 54: reference to external entity in attribute value
    …href="/index.php?page=kategorie&cat_no=3" title="Kontaktanzeigen Er sucht Sie"…

    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 206, Column 54: reference to entity "cat_no" for which no system identifier could be generated
    …href="/index.php?page=kategorie&cat_no=3" title="Kontaktanzeigen Er sucht Sie"…

    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 205, Column 47: entity was defined here
    …    <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie su…
  • Warning Line 207, Column 54: reference not terminated by REFC delimiter
    …href="/index.php?page=kategorie&cat_no=4" title="Kontaktanzeigen Sie sucht Sie…

    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 207, Column 54: reference to external entity in attribute value
    …href="/index.php?page=kategorie&cat_no=4" title="Kontaktanzeigen Sie sucht Sie…

    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 207, Column 54: reference to entity "cat_no" for which no system identifier could be generated
    …href="/index.php?page=kategorie&cat_no=4" title="Kontaktanzeigen Sie sucht Sie…

    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 205, Column 47: entity was defined here
    …    <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie su…
  • Warning Line 208, Column 54: reference not terminated by REFC delimiter
    …href="/index.php?page=kategorie&cat_no=5" title="Kontaktanzeigen Er sucht Ihn"…

    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 208, Column 54: reference to external entity in attribute value
    …href="/index.php?page=kategorie&cat_no=5" title="Kontaktanzeigen Er sucht Ihn"…

    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 208, Column 54: reference to entity "cat_no" for which no system identifier could be generated
    …href="/index.php?page=kategorie&cat_no=5" title="Kontaktanzeigen Er sucht Ihn"…

    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 205, Column 47: entity was defined here
    …    <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie su…
  • Warning Line 209, Column 195: reference not terminated by REFC delimiter
    …href="/index.php?page=kategorie&cat_no=7" title="Kontaktanzeigen Freizeitpartn…

    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 209, Column 195: reference to external entity in attribute value
    …href="/index.php?page=kategorie&cat_no=7" title="Kontaktanzeigen Freizeitpartn…

    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 209, Column 195: reference to entity "cat_no" for which no system identifier could be generated
    …href="/index.php?page=kategorie&cat_no=7" title="Kontaktanzeigen Freizeitpartn…

    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 205, Column 47: entity was defined here
    …    <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie su…
  • Warning Line 246, Column 44: cannot generate system identifier for general entity "id"
    …   <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.d…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 246, Column 44: general entity "id" not defined and no default entity
    …   <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.d…

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

  • Warning Line 246, Column 46: reference not terminated by REFC delimiter
    … <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.de …

    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 246, Column 46: reference to external entity in attribute value
    … <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.de …

    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 246, Column 46: reference to entity "id" for which no system identifier could be generated
    … <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.de …

    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 246, Column 43: entity was defined here
    …    <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.…
  • Warning Line 249, Column 46: reference not terminated by REFC delimiter
    …     <a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.de …

    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 249, Column 46: reference to external entity in attribute value
    …     <a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.de …

    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 249, Column 46: reference to entity "id" for which no system identifier could be generated
    …     <a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.de …

    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 246, Column 43: entity was defined here
    …    <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.…
  • Warning Line 251, Column 46: reference not terminated by REFC delimiter
    … <h2><a href="/index.php?page=newsr&id=2740" class="teaser-title" title="Partn…

    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 251, Column 46: reference to external entity in attribute value
    … <h2><a href="/index.php?page=newsr&id=2740" class="teaser-title" title="Partn…

    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 251, Column 46: reference to entity "id" for which no system identifier could be generated
    … <h2><a href="/index.php?page=newsr&id=2740" class="teaser-title" title="Partn…

    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 246, Column 43: entity was defined here
    …    <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.…
  • Warning Line 254, Column 34: reference not terminated by REFC delimiter
    <a href="/index.php?page=newsr&id=2740" title="Partnersuche Fischkopf.de - Tipp…

    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 254, Column 34: reference to external entity in attribute value
    <a href="/index.php?page=newsr&id=2740" title="Partnersuche Fischkopf.de - Tipp…

    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 254, Column 34: reference to entity "id" for which no system identifier could be generated
    <a href="/index.php?page=newsr&id=2740" title="Partnersuche Fischkopf.de - Tipp…

    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 246, Column 43: entity was defined here
    …    <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.…
  • Warning Line 256, Column 46: reference not terminated by REFC delimiter
    … <h2><a href="/index.php?page=newsr&id=2739" class="teaser-title" title="Partn…

    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 256, Column 46: reference to external entity in attribute value
    … <h2><a href="/index.php?page=newsr&id=2739" class="teaser-title" title="Partn…

    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 256, Column 46: reference to entity "id" for which no system identifier could be generated
    … <h2><a href="/index.php?page=newsr&id=2739" class="teaser-title" title="Partn…

    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 246, Column 43: entity was defined here
    …    <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.…
  • Warning Line 259, Column 40: reference not terminated by REFC delimiter
    …     <a href="/index.php?page=newsr&id=2739" title="Partnersuche Fischkopf.de …

    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 259, Column 40: reference to external entity in attribute value
    …     <a href="/index.php?page=newsr&id=2739" title="Partnersuche Fischkopf.de …

    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 259, Column 40: reference to entity "id" for which no system identifier could be generated
    …     <a href="/index.php?page=newsr&id=2739" title="Partnersuche Fischkopf.de …

    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 246, Column 43: entity was defined here
    …    <h2><a href="/index.php?page=newsr&id=2742" title="Partnersuche Fischkopf.…
  • Error Line 269, Column 60: there is no attribute "alt"
    …  <a href="index.php?page=about" title="Über Uns" alt="Über Uns">Über Uns</a> -

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

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

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

  • Warning Line 274, Column 53: character "&" is the first character of a delimiter but occurred as data
    …<a href="index.php?page=hilfel" title="Hilfe & FAQ" alt="Hilfe & FAQ">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 274, Column 71: character "&" is the first character of a delimiter but occurred as data
    …<a href="index.php?page=hilfel" title="Hilfe & FAQ" alt="Hilfe & FAQ">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 283, Column 127: cannot generate system identifier for general entity "aktion"
    …ng:0px !important;" method="post" action="index.php?page=account&aktion=login">

    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 283, Column 127: general entity "aktion" not defined and no default entity
    …ng:0px !important;" method="post" action="index.php?page=account&aktion=login">

    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 283, Column 133: reference not terminated by REFC delimiter
    …ng:0px !important;" method="post" action="index.php?page=account&aktion=login">

    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 283, Column 133: reference to external entity in attribute value
    …ng:0px !important;" method="post" action="index.php?page=account&aktion=login">

    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 283, Column 133: reference to entity "aktion" for which no system identifier could be generated
    …ng:0px !important;" method="post" action="index.php?page=account&aktion=login">

    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 283, Column 126: entity was defined here
    …ng:0px !important;" method="post" action="index.php?page=account&aktion=login">
  • Error Line 287, Column 214: end tag for "input" omitted, but OMITTAG NO was specified
    …height:11px; border:1px solid #ccc; padding:4px; font-size:10px" tabindex="45">

    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 287, Column 45: start tag was here
    <input type="text" value="" name="lbenut…
  • Error Line 298, Column 209: end tag for "input" omitted, but OMITTAG NO was specified
    …height:11px; border:1px solid #ccc; padding:4px; font-size:10px" tabindex="46">

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

  • Info Line 298, Column 45: start tag was here
    <input type="password" name="lpasswort" …
  • Error Line 300, Column 461: end tag for "input" omitted, but OMITTAG NO was specified
    …; border-radius: 5px;" class="submit" name="Login" value="Login" tabindex="48">

    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 300, Column 173: start tag was here
    <input type="submit" style="border:1px s…
  • Warning Line 330, Column 50: cannot generate system identifier for general entity "sres"
        <li class=""><a href="/index.php?page=suchen&sres=1">Mitglieder</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 330, Column 50: general entity "sres" not defined and no default entity
        <li class=""><a href="/index.php?page=suchen&sres=1">Mitglieder</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 330, Column 54: reference not terminated by REFC delimiter
        <li class=""><a href="/index.php?page=suchen&sres=1">Mitglieder</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 330, Column 54: reference to external entity in attribute value
        <li class=""><a href="/index.php?page=suchen&sres=1">Mitglieder</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 330, Column 54: reference to entity "sres" for which no system identifier could be generated
        <li class=""><a href="/index.php?page=suchen&sres=1">Mitglieder</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 330, Column 49: entity was defined here
        <li class=""><a href="/index.php?page=suchen&sres=1">Mitglieder</a>
  • Warning Line 335, Column 53: reference not terminated by REFC delimiter
    …i><a href="/index.php?page=suchen&sres=1" title="Singlesuche: Finde Singles au…

    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 335, Column 53: reference to external entity in attribute value
    …i><a href="/index.php?page=suchen&sres=1" title="Singlesuche: Finde Singles au…

    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 335, Column 53: reference to entity "sres" for which no system identifier could be generated
    …i><a href="/index.php?page=suchen&sres=1" title="Singlesuche: Finde Singles au…

    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 330, Column 49: entity was defined here
        <li class=""><a href="/index.php?page=suchen&sres=1">Mitglieder</a>
  • Warning Line 337, Column 62: cannot generate system identifier for general entity "gbday"
    …           <li><a href="/index.php?page=gbt&gbday=3">Geburtstagsfische</a></li>

    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 337, Column 62: general entity "gbday" not defined and no default entity
    …           <li><a href="/index.php?page=gbt&gbday=3">Geburtstagsfische</a></li>

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

  • Warning Line 337, Column 67: reference not terminated by REFC delimiter
    …           <li><a href="/index.php?page=gbt&gbday=3">Geburtstagsfische</a></li>

    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 337, Column 67: reference to external entity in attribute value
    …           <li><a href="/index.php?page=gbt&gbday=3">Geburtstagsfische</a></li>

    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 337, Column 67: reference to entity "gbday" for which no system identifier could be generated
    …           <li><a href="/index.php?page=gbt&gbday=3">Geburtstagsfische</a></li>

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

  • Info Line 337, Column 61: entity was defined here
    …           <li><a href="/index.php?page=gbt&gbday=3">Geburtstagsfische</a></li>
  • Warning Line 338, Column 66: reference not terminated by REFC delimiter
    …href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie sucht Ihn…

    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 338, Column 66: reference to external entity in attribute value
    …href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie sucht Ihn…

    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 338, Column 66: reference to entity "cat_no" for which no system identifier could be generated
    …href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie sucht Ihn…

    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 205, Column 47: entity was defined here
    …    <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie su…
  • Warning Line 339, Column 70: reference not terminated by REFC delimiter
    …href="/index.php?page=kategorie&cat_no=3" title="Kontaktanzeigen Er sucht Sie"…

    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 339, Column 70: reference to external entity in attribute value
    …href="/index.php?page=kategorie&cat_no=3" title="Kontaktanzeigen Er sucht Sie"…

    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 339, Column 70: reference to entity "cat_no" for which no system identifier could be generated
    …href="/index.php?page=kategorie&cat_no=3" title="Kontaktanzeigen Er sucht Sie"…

    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 205, Column 47: entity was defined here
    …    <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie su…
  • Warning Line 340, Column 70: reference not terminated by REFC delimiter
    …href="/index.php?page=kategorie&cat_no=4" title="Kontaktanzeigen Sie sucht Sie…

    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 340, Column 70: reference to external entity in attribute value
    …href="/index.php?page=kategorie&cat_no=4" title="Kontaktanzeigen Sie sucht Sie…

    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 340, Column 70: reference to entity "cat_no" for which no system identifier could be generated
    …href="/index.php?page=kategorie&cat_no=4" title="Kontaktanzeigen Sie sucht Sie…

    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 205, Column 47: entity was defined here
    …    <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie su…
  • Warning Line 341, Column 70: reference not terminated by REFC delimiter
    …href="/index.php?page=kategorie&cat_no=5" title="Kontaktanzeigen Er sucht Ihn"…

    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 341, Column 70: reference to external entity in attribute value
    …href="/index.php?page=kategorie&cat_no=5" title="Kontaktanzeigen Er sucht Ihn"…

    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 341, Column 70: reference to entity "cat_no" for which no system identifier could be generated
    …href="/index.php?page=kategorie&cat_no=5" title="Kontaktanzeigen Er sucht Ihn"…

    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 205, Column 47: entity was defined here
    …    <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie su…
  • Warning Line 342, Column 70: reference not terminated by REFC delimiter
    …href="/index.php?page=kategorie&cat_no=7" title="Kontaktanzeigen Freizeitpartn…

    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 342, Column 70: reference to external entity in attribute value
    …href="/index.php?page=kategorie&cat_no=7" title="Kontaktanzeigen Freizeitpartn…

    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 342, Column 70: reference to entity "cat_no" for which no system identifier could be generated
    …href="/index.php?page=kategorie&cat_no=7" title="Kontaktanzeigen Freizeitpartn…

    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 205, Column 47: entity was defined here
    …    <a href="/index.php?page=kategorie&cat_no=2" title="Kontaktanzeigen Sie su…
  • Warning Line 365, Column 63: cannot generate system identifier for general entity "luckyuser"
    …"/index.php?page=goldfischverschenken&luckyuser=geschenkgutschein" title="Gesc…

    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 365, Column 63: general entity "luckyuser" not defined and no default entity
    …"/index.php?page=goldfischverschenken&luckyuser=geschenkgutschein" title="Gesc…

    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 365, Column 72: reference not terminated by REFC delimiter
    …hp?page=goldfischverschenken&luckyuser=geschenkgutschein" title="Geschenk-Guts…

    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 365, Column 72: reference to external entity in attribute value
    …hp?page=goldfischverschenken&luckyuser=geschenkgutschein" title="Geschenk-Guts…

    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 365, Column 72: reference to entity "luckyuser" for which no system identifier could be generated
    …hp?page=goldfischverschenken&luckyuser=geschenkgutschein" title="Geschenk-Guts…

    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 365, Column 62: entity was defined here
    …="/index.php?page=goldfischverschenken&luckyuser=geschenkgutschein" title="Ges…
  • Warning Line 370, Column 60: character "&" is the first character of a delimiter but occurred as data
    …ref="index.php?page=news" title="News & Party: Singleparty, Flirtfinder, Nachr…

    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 370, Column 132: character "&" is the first character of a delimiter but occurred as data
    … Nachrichten, Party-Bilder" alt="News & Party: Singleparty, Flirtfinder, Nachr…

    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 370, Column 199: character "&" is the first character of a delimiter but occurred as data
    …& Party: Singleparty, Flirtfinder, Nachrichten, Party-Bilder">News & Partys</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 377, Column 94: there is no attribute "onClick"
    …ty-Bilder" alt="Party-Bilder" onClick='window.open("http://www.nwzonline.de/in…

    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 384, Column 79: character "&" is the first character of a delimiter but occurred as data
    …motor?from=4" title="Video-Kanal Auto & Motor" alt="Video-Kanal Auto & Motor">…

    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 384, Column 110: character "&" is the first character of a delimiter but occurred as data
    …"Video-Kanal Auto & Motor" alt="Video-Kanal Auto & Motor">Auto & Motor</a></li>

    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 384, Column 124: character "&" is the first character of a delimiter but occurred as data
    …"Video-Kanal Auto & Motor" alt="Video-Kanal Auto & Motor">Auto & Motor</a></li>

    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 385, Column 90: character "&" is the first character of a delimiter but occurred as data
    …n?from=4" title="Video-Kanal Business & Finanzen" alt="Video-Kanal Business & …

    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 385, Column 128: character "&" is the first character of a delimiter but occurred as data
    … & Finanzen" alt="Video-Kanal Business & Finanzen">Business & Finanzen</a></li>

    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 385, Column 149: character "&" is the first character of a delimiter but occurred as data
    … & Finanzen" alt="Video-Kanal Business & Finanzen">Business & Finanzen</a></li>

    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 386, Column 85: character "&" is the first character of a delimiter but occurred as data
    …uter?from=4" title="Video-Kanal Games & Computer" alt="Video-Kanal Games & Com…

    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 386, Column 120: character "&" is the first character of a delimiter but occurred as data
    … Games & Computer" alt="Video-Kanal Games & Computer">Games & Computer</a></li>

    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 386, Column 138: character "&" is the first character of a delimiter but occurred as data
    … Games & Computer" alt="Video-Kanal Games & Computer">Games & Computer</a></li>

    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 388, Column 89: character "&" is the first character of a delimiter but occurred as data
    …?from=4" title="Video-Kanal Lifestyle & Mode" alt="Video-Kanal Lifestyle & Mod…

    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 388, Column 124: character "&" is the first character of a delimiter but occurred as data
    … Lifestyle & Mode" alt="Video-Kanal Lifestyle & Mode">Lifestyle & Mode</a></li>

    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 388, Column 142: character "&" is the first character of a delimiter but occurred as data
    … Lifestyle & Mode" alt="Video-Kanal Lifestyle & Mode">Lifestyle & Mode</a></li>

    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 390, Column 96: character "&" is the first character of a delimiter but occurred as data
    …rom=4" title="Video-Kanal Nachrichten & Politik" alt="Video-Kanal Nachrichten …

    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 390, Column 136: character "&" is the first character of a delimiter but occurred as data
    …Politik" alt="Video-Kanal Nachrichten & Politik">Nachrichten & Politik</a></li…

    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 390, Column 159: character "&" is the first character of a delimiter but occurred as data
    …Politik" alt="Video-Kanal Nachrichten & Politik">Nachrichten & Politik</a></li>

    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 401, Column 54: ID "content" already defined
                                                <div id="content">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 185, Column 14: ID "content" first defined here
        <div id="content">
  • Error Line 410, Column 55: document type does not allow element "style" here
                                    <style type="text/css">

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

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

  • Error Line 525, Column 67: character ";" not allowed in attribute specification list
          -webkit-border-radius: 5px; /* Saf3-4, iOS 1-3.2, Android <e;1.6 */
  • Error Line 525, Column 67: element "e" undefined
          -webkit-border-radius: 5px; /* Saf3-4, iOS 1-3.2, Android <e;1.6 */

    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 543, Column 8: end tag for "e" omitted, but OMITTAG NO was specified
    </style>

    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 525, Column 65: start tag was here
          -webkit-border-radius: 5px; /* Saf3-4, iOS 1-3.2, Android <e;1.6 */
  • Error Line 544, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 723, Column 30: document type does not allow element "style" here
           <style type="text/css">

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

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

  • Error Line 738, Column 23: value of attribute "method" cannot be "POST"; must be one of "get", "post"
        <form method="POST" action="index.php?page=fischkopf_werden_step1">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 767, Column 29: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    <option value="29"  selected>29</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 830, Column 54: ID "data_suche_alter" already defined
    <select name="data_suche_alter_bis" tabindex="3" id="data_suche_alter" >

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 755, Column 54: ID "data_suche_alter" first defined here
    <select name="data_suche_alter_von" tabindex="2" id="data_suche_alter" >
  • Error Line 852, Column 29: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    <option value="39"  selected>39</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 920, Column 72: end tag for "input" omitted, but OMITTAG NO was specified
    …name="benutzer" value="" tabindex="6"><a id="tooltip1" ><img width="16" height…

    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 920, Column 1: start tag was here
    <input type="text" id="benutzer" name="benutzer" value="" tabindex="6"><a id="t…
  • Error Line 920, Column 357: element "u" undefined
    …r</b> angezeigt wird. Benutze daher <u>nicht</u> deinen richtigen Namen und au…

    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 920, Column 463: end tag for "br" omitted, but OMITTAG NO was specified
    …ere User lächerlich wirken könnte.<br><br> Dein Nickname muss mindestens 4 Zei…

    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 920, Column 459: start tag was here
    … andere User lächerlich wirken könnte.<br><br> Dein Nickname muss mindestens 4…
  • Error Line 920, Column 467: end tag for "br" omitted, but OMITTAG NO was specified
    …User lächerlich wirken könnte.<br><br> Dein Nickname muss mindestens 4 Zeichen…

    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 920, Column 463: start tag was here
    …ere User lächerlich wirken könnte.<br><br> Dein Nickname muss mindestens 4 Zei…
  • Error Line 920, Column 596: element "u" undefined
    …n sind alle Buchstaben und Ziffern. <u>Keine</u> Leerzeichen und Sonderzeichen…

    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 920, Column 641: end tag for "br" omitted, but OMITTAG NO was specified
    …/u> Leerzeichen und Sonderzeichen.<br><br> Achtung: <b>Der Nickname kann nacht…

    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 920, Column 637: start tag was here
    …ine</u> Leerzeichen und Sonderzeichen.<br><br> Achtung: <b>Der Nickname kann n…
  • Error Line 920, Column 645: end tag for "br" omitted, but OMITTAG NO was specified
    …Leerzeichen und Sonderzeichen.<br><br> Achtung: <b>Der Nickname kann nachträgl…

    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 920, Column 641: start tag was here
    …/u> Leerzeichen und Sonderzeichen.<br><br> Achtung: <b>Der Nickname kann nacht…
  • Error Line 921, Column 15: end tag for "br" omitted, but OMITTAG NO was specified
    </p></div><br><span></span>

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

  • Info Line 921, Column 11: start tag was here
    </p></div><br><span></span>
  • Error Line 924, Column 62: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class="anmeldung-rechts" style="width : 190px !important">

    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 926, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
    …l" name="email" value="" tabindex="6"><a id="tooltip2" ><img width="16" height…

    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 926, Column 1: start tag was here
    <input type="text" id="email" name="email" value="" tabindex="6"><a id="tooltip…
  • Error Line 926, Column 254: element "u" undefined
    …ip"><h4>Email</h4><p>Bitte gib eine <u>gültige</u> E-Mail Adresse an.<br><br>D…

    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 926, Column 289: end tag for "br" omitted, but OMITTAG NO was specified
    … <u>gültige</u> E-Mail Adresse an.<br><br>Deine E-Mail-Adresse ist für andere …

    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 926, Column 285: start tag was here
    …eine <u>gültige</u> E-Mail Adresse an.<br><br>Deine E-Mail-Adresse ist für and…
  • Error Line 926, Column 293: end tag for "br" omitted, but OMITTAG NO was specified
    …gültige</u> E-Mail Adresse an.<br><br>Deine E-Mail-Adresse ist für andere User…

    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 926, Column 289: start tag was here
    … <u>gültige</u> E-Mail Adresse an.<br><br>Deine E-Mail-Adresse ist für andere …
  • Error Line 926, Column 409: end tag for "br" omitted, but OMITTAG NO was specified
    …s auch <b>nicht weitergegeben</b>.<br><br>Du bekommst auf diese E-Mail-Adresse…

    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 926, Column 405: start tag was here
    …n uns auch <b>nicht weitergegeben</b>.<br><br>Du bekommst auf diese E-Mail-Adr…
  • Error Line 926, Column 413: end tag for "br" omitted, but OMITTAG NO was specified
    …ch <b>nicht weitergegeben</b>.<br><br>Du bekommst auf diese E-Mail-Adresse ein…

    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 926, Column 409: start tag was here
    …s auch <b>nicht weitergegeben</b>.<br><br>Du bekommst auf diese E-Mail-Adresse…
  • Error Line 927, Column 15: end tag for "br" omitted, but OMITTAG NO was specified
    </p></div><br><span></span></li>

    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 927, Column 11: start tag was here
    </p></div><br><span></span></li>
  • Error Line 929, Column 24: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li style="clear:both;">

    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 931, Column 76: end tag for "input" omitted, but OMITTAG NO was specified
    …name="passwort" value="" tabindex="7"><a id="tooltip3" ><img width="16" height…

    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 931, Column 1: start tag was here
    <input type="password" id="passwort" name="passwort" value="" tabindex="7"><a i…
  • Error Line 932, Column 29: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <ul class="password-tooltip"> <li>Mindestens 2 Buchstaben und 2 Ziffern oder So…

    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 942, Column 29: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class="anmeldung-rechts">

    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 944, Column 78: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="password" name="passwort2" id="passwort2" value="" tabindex="8">

    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 944, Column 1: start tag was here
    <input type="password" name="passwort2" id="passwort2" value="" tabindex="8">
  • Error Line 955, Column 82: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    … class="list-clear" style="width:170px !important; margin-top:19px !important">

    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 958, Column 30: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li class="signup-list-last" >

    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 959, Column 130: end tag for "input" omitted, but OMITTAG NO was specified
    …kopf-anmeldebox-submit" value="Hier klicken - kostenlos flirten!" tabindex="9">

    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 959, Column 1: start tag was here
    <input type="submit" name="submit_step1" id="fischkopf-anmeldebox-submit" value…
  • Error Line 961, Column 5: 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 929, Column 1: start tag was here
    <li style="clear:both;">
  • Error Line 961, Column 5: 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 918, Column 1: start tag was here
    <li>
  • Error Line 985, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Warning Line 1018, Column 122: cannot generate system identifier for general entity "user"
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">

    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 1018, Column 122: general entity "user" not defined and no default entity
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">

    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 1018, Column 126: reference not terminated by REFC delimiter
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">

    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 1018, Column 126: reference to external entity in attribute value
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">

    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 1018, Column 126: reference to entity "user" for which no system identifier could be generated
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1019, Column 63: there is no attribute "border"
    …l-align:middle; margin: auto;" border="0" src="http://user-images.fischkopf.de…

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

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

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

  • Error Line 1019, Column 201: end tag for "img" omitted, but OMITTAG NO was specified
    …jpg"  alt="x" title="Bilder gross/Weitere Bilder von Zugewinn"></a></div></div>

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

  • Info Line 1019, Column 6: start tag was here
         <img style="vertical-align:middle; margin: auto;" border="0" src="http://u…
  • Error Line 1020, Column 43: there is no attribute "src"
    …<p class="region_username"><image src="images/symbol_f.gif" width="7" height="…

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

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

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

  • Error Line 1020, Column 71: there is no attribute "width"
    …image src="images/symbol_f.gif" width="7" height="8"><a  class="black useronli…

    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 1020, Column 82: there is no attribute "height"
    …images/symbol_f.gif" width="7" height="8"><a  class="black useronlinelink" hre…

    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 1020, Column 85: element "image" undefined
    …ges/symbol_f.gif" width="7" height="8"><a  class="black useronlinelink" href="…

    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 1020, Column 167: reference not terminated by REFC delimiter
    …x.php?page=fischkopf_werden_step1&user=Zugewinn">&nbsp;Zugewinn&nbsp;(48)</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 1020, Column 167: reference to external entity in attribute value
    …x.php?page=fischkopf_werden_step1&user=Zugewinn">&nbsp;Zugewinn&nbsp;(48)</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 1020, Column 167: reference to entity "user" for which no system identifier could be generated
    …x.php?page=fischkopf_werden_step1&user=Zugewinn">&nbsp;Zugewinn&nbsp;(48)</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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1020, Column 209: end tag for "image" omitted, but OMITTAG NO was specified
    …ge=fischkopf_werden_step1&user=Zugewinn">&nbsp;Zugewinn&nbsp;(48)</a></p></div>

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

  • Info Line 1020, Column 32: start tag was here
        <p class="region_username"><image src="images/symbol_f.gif" width="7" heigh…
  • Warning Line 1025, Column 126: reference not terminated by REFC delimiter
    …ilder von ideenlos" href="index.php?page=fischkopf_werden_step1&user=ideenlos">

    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 1025, Column 126: reference to external entity in attribute value
    …ilder von ideenlos" href="index.php?page=fischkopf_werden_step1&user=ideenlos">

    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 1025, Column 126: reference to entity "user" for which no system identifier could be generated
    …ilder von ideenlos" href="index.php?page=fischkopf_werden_step1&user=ideenlos">

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1026, Column 201: end tag for "img" omitted, but OMITTAG NO was specified
    …jpg"  alt="x" title="Bilder gross/Weitere Bilder von ideenlos"></a></div></div>

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

  • Info Line 1026, Column 6: start tag was here
         <img style="vertical-align:middle; margin: auto;" border="0" src="http://u…
  • Error Line 1027, Column 85: element "image" undefined
    …ges/symbol_m.gif" width="7" height="8"><a  class="black useronlinelink" href="…

    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 1027, Column 167: reference not terminated by REFC delimiter
    …x.php?page=fischkopf_werden_step1&user=ideenlos">&nbsp;ideenlos&nbsp;(26)</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 1027, Column 167: reference to external entity in attribute value
    …x.php?page=fischkopf_werden_step1&user=ideenlos">&nbsp;ideenlos&nbsp;(26)</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 1027, Column 167: reference to entity "user" for which no system identifier could be generated
    …x.php?page=fischkopf_werden_step1&user=ideenlos">&nbsp;ideenlos&nbsp;(26)</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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1027, Column 209: end tag for "image" omitted, but OMITTAG NO was specified
    …ge=fischkopf_werden_step1&user=ideenlos">&nbsp;ideenlos&nbsp;(26)</a></p></div>

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

  • Info Line 1027, Column 32: start tag was here
        <p class="region_username"><image src="images/symbol_m.gif" width="7" heigh…
  • Warning Line 1032, Column 129: reference not terminated by REFC delimiter
    …von rattichkeks" href="index.php?page=fischkopf_werden_step1&user=rattichkeks">

    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 1032, Column 129: reference to external entity in attribute value
    …von rattichkeks" href="index.php?page=fischkopf_werden_step1&user=rattichkeks">

    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 1032, Column 129: reference to entity "user" for which no system identifier could be generated
    …von rattichkeks" href="index.php?page=fischkopf_werden_step1&user=rattichkeks">

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1033, Column 201: end tag for "img" omitted, but OMITTAG NO was specified
    …"  alt="x" title="Bilder gross/Weitere Bilder von rattichkeks"></a></div></div>

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

  • Info Line 1033, Column 6: start tag was here
         <img style="vertical-align:middle; margin: auto;" border="0" src="http://u…
  • Error Line 1034, Column 85: element "image" undefined
    …ges/symbol_f.gif" width="7" height="8"><a  class="black useronlinelink" href="…

    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 1034, Column 167: reference not terminated by REFC delimiter
    …x.php?page=fischkopf_werden_step1&user=rattichkeks">&nbsp;rattichkeks&nbsp;(28…

    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 1034, Column 167: reference to external entity in attribute value
    …x.php?page=fischkopf_werden_step1&user=rattichkeks">&nbsp;rattichkeks&nbsp;(28…

    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 1034, Column 167: reference to entity "user" for which no system identifier could be generated
    …x.php?page=fischkopf_werden_step1&user=rattichkeks">&nbsp;rattichkeks&nbsp;(28…

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1034, Column 215: end tag for "image" omitted, but OMITTAG NO was specified
    …chkopf_werden_step1&user=rattichkeks">&nbsp;rattichkeks&nbsp;(28)</a></p></div>

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

  • Info Line 1034, Column 32: start tag was here
        <p class="region_username"><image src="images/symbol_f.gif" width="7" heigh…
  • Warning Line 1039, Column 125: reference not terminated by REFC delimiter
    …"Bilder von Hanse26" href="index.php?page=fischkopf_werden_step1&user=Hanse26">

    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 1039, Column 125: reference to external entity in attribute value
    …"Bilder von Hanse26" href="index.php?page=fischkopf_werden_step1&user=Hanse26">

    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 1039, Column 125: reference to entity "user" for which no system identifier could be generated
    …"Bilder von Hanse26" href="index.php?page=fischkopf_werden_step1&user=Hanse26">

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1040, Column 200: end tag for "img" omitted, but OMITTAG NO was specified
    ….jpg"  alt="x" title="Bilder gross/Weitere Bilder von Hanse26"></a></div></div>

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

  • Info Line 1040, Column 6: start tag was here
         <img style="vertical-align:middle; margin: auto;" border="0" src="http://u…
  • Error Line 1041, Column 85: element "image" undefined
    …ges/symbol_m.gif" width="7" height="8"><a  class="black useronlinelink" href="…

    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 1041, Column 167: reference not terminated by REFC delimiter
    …x.php?page=fischkopf_werden_step1&user=Hanse26">&nbsp;Hanse26&nbsp;(26)</a></p…

    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 1041, Column 167: reference to external entity in attribute value
    …x.php?page=fischkopf_werden_step1&user=Hanse26">&nbsp;Hanse26&nbsp;(26)</a></p…

    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 1041, Column 167: reference to entity "user" for which no system identifier could be generated
    …x.php?page=fischkopf_werden_step1&user=Hanse26">&nbsp;Hanse26&nbsp;(26)</a></p…

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1041, Column 207: end tag for "image" omitted, but OMITTAG NO was specified
    …page=fischkopf_werden_step1&user=Hanse26">&nbsp;Hanse26&nbsp;(26)</a></p></div>

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

  • Info Line 1041, Column 32: start tag was here
        <p class="region_username"><image src="images/symbol_m.gif" width="7" heigh…
  • Warning Line 1046, Column 130: reference not terminated by REFC delimiter
    …n Bremermaus48" href="index.php?page=fischkopf_werden_step1&user=Bremermaus48">

    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 1046, Column 130: reference to external entity in attribute value
    …n Bremermaus48" href="index.php?page=fischkopf_werden_step1&user=Bremermaus48">

    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 1046, Column 130: reference to entity "user" for which no system identifier could be generated
    …n Bremermaus48" href="index.php?page=fischkopf_werden_step1&user=Bremermaus48">

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1047, Column 200: end tag for "img" omitted, but OMITTAG NO was specified
    …  alt="x" title="Bilder gross/Weitere Bilder von Bremermaus48"></a></div></div>

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

  • Info Line 1047, Column 6: start tag was here
         <img style="vertical-align:middle; margin: auto;" border="0" src="http://u…
  • Error Line 1048, Column 85: element "image" undefined
    …ges/symbol_f.gif" width="7" height="8"><a  class="black useronlinelink" href="…

    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 1048, Column 167: reference not terminated by REFC delimiter
    …x.php?page=fischkopf_werden_step1&user=Bremermaus48">&nbsp;Bremermaus48&nbsp;(…

    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 1048, Column 167: reference to external entity in attribute value
    …x.php?page=fischkopf_werden_step1&user=Bremermaus48">&nbsp;Bremermaus48&nbsp;(…

    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 1048, Column 167: reference to entity "user" for which no system identifier could be generated
    …x.php?page=fischkopf_werden_step1&user=Bremermaus48">&nbsp;Bremermaus48&nbsp;(…

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1048, Column 217: end tag for "image" omitted, but OMITTAG NO was specified
    …kopf_werden_step1&user=Bremermaus48">&nbsp;Bremermaus48&nbsp;(49)</a></p></div>

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

  • Info Line 1048, Column 32: start tag was here
        <p class="region_username"><image src="images/symbol_f.gif" width="7" heigh…
  • Warning Line 1053, Column 126: reference not terminated by REFC delimiter
    …ilder von Kerl1310" href="index.php?page=fischkopf_werden_step1&user=Kerl1310">

    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 1053, Column 126: reference to external entity in attribute value
    …ilder von Kerl1310" href="index.php?page=fischkopf_werden_step1&user=Kerl1310">

    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 1053, Column 126: reference to entity "user" for which no system identifier could be generated
    …ilder von Kerl1310" href="index.php?page=fischkopf_werden_step1&user=Kerl1310">

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1054, Column 201: end tag for "img" omitted, but OMITTAG NO was specified
    …jpg"  alt="x" title="Bilder gross/Weitere Bilder von Kerl1310"></a></div></div>

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

  • Info Line 1054, Column 6: start tag was here
         <img style="vertical-align:middle; margin: auto;" border="0" src="http://u…
  • Error Line 1055, Column 85: element "image" undefined
    …ges/symbol_m.gif" width="7" height="8"><a  class="black useronlinelink" href="…

    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 1055, Column 167: reference not terminated by REFC delimiter
    …x.php?page=fischkopf_werden_step1&user=Kerl1310">&nbsp;Kerl1310&nbsp;(60)</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 1055, Column 167: reference to external entity in attribute value
    …x.php?page=fischkopf_werden_step1&user=Kerl1310">&nbsp;Kerl1310&nbsp;(60)</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 1055, Column 167: reference to entity "user" for which no system identifier could be generated
    …x.php?page=fischkopf_werden_step1&user=Kerl1310">&nbsp;Kerl1310&nbsp;(60)</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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1055, Column 209: end tag for "image" omitted, but OMITTAG NO was specified
    …ge=fischkopf_werden_step1&user=Kerl1310">&nbsp;Kerl1310&nbsp;(60)</a></p></div>

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

  • Info Line 1055, Column 32: start tag was here
        <p class="region_username"><image src="images/symbol_m.gif" width="7" heigh…
  • Warning Line 1060, Column 126: reference not terminated by REFC delimiter
    …ilder von Svenja81" href="index.php?page=fischkopf_werden_step1&user=Svenja81">

    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 1060, Column 126: reference to external entity in attribute value
    …ilder von Svenja81" href="index.php?page=fischkopf_werden_step1&user=Svenja81">

    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 1060, Column 126: reference to entity "user" for which no system identifier could be generated
    …ilder von Svenja81" href="index.php?page=fischkopf_werden_step1&user=Svenja81">

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1061, Column 201: end tag for "img" omitted, but OMITTAG NO was specified
    …jpg"  alt="x" title="Bilder gross/Weitere Bilder von Svenja81"></a></div></div>

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

  • Info Line 1061, Column 6: start tag was here
         <img style="vertical-align:middle; margin: auto;" border="0" src="http://u…
  • Error Line 1062, Column 85: element "image" undefined
    …ges/symbol_f.gif" width="7" height="8"><a  class="black useronlinelink" href="…

    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 1062, Column 167: reference not terminated by REFC delimiter
    …x.php?page=fischkopf_werden_step1&user=Svenja81">&nbsp;Svenja81&nbsp;(31)</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 1062, Column 167: reference to external entity in attribute value
    …x.php?page=fischkopf_werden_step1&user=Svenja81">&nbsp;Svenja81&nbsp;(31)</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 1062, Column 167: reference to entity "user" for which no system identifier could be generated
    …x.php?page=fischkopf_werden_step1&user=Svenja81">&nbsp;Svenja81&nbsp;(31)</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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1062, Column 209: end tag for "image" omitted, but OMITTAG NO was specified
    …ge=fischkopf_werden_step1&user=Svenja81">&nbsp;Svenja81&nbsp;(31)</a></p></div>

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

  • Info Line 1062, Column 32: start tag was here
        <p class="region_username"><image src="images/symbol_f.gif" width="7" heigh…
  • Warning Line 1067, Column 130: reference not terminated by REFC delimiter
    …n Welnessmeyer" href="index.php?page=fischkopf_werden_step1&user=Welnessmeyer">

    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 1067, Column 130: reference to external entity in attribute value
    …n Welnessmeyer" href="index.php?page=fischkopf_werden_step1&user=Welnessmeyer">

    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 1067, Column 130: reference to entity "user" for which no system identifier could be generated
    …n Welnessmeyer" href="index.php?page=fischkopf_werden_step1&user=Welnessmeyer">

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1068, Column 201: end tag for "img" omitted, but OMITTAG NO was specified
    …  alt="x" title="Bilder gross/Weitere Bilder von Welnessmeyer"></a></div></div>

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

  • Info Line 1068, Column 6: start tag was here
         <img style="vertical-align:middle; margin: auto;" border="0" src="http://u…
  • Error Line 1069, Column 85: element "image" undefined
    …ges/symbol_m.gif" width="7" height="8"><a  class="black useronlinelink" href="…

    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 1069, Column 167: reference not terminated by REFC delimiter
    …x.php?page=fischkopf_werden_step1&user=Welnessmeyer">&nbsp;Welnessmeyer&nbsp;(…

    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 1069, Column 167: reference to external entity in attribute value
    …x.php?page=fischkopf_werden_step1&user=Welnessmeyer">&nbsp;Welnessmeyer&nbsp;(…

    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 1069, Column 167: reference to entity "user" for which no system identifier could be generated
    …x.php?page=fischkopf_werden_step1&user=Welnessmeyer">&nbsp;Welnessmeyer&nbsp;(…

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1069, Column 217: end tag for "image" omitted, but OMITTAG NO was specified
    …kopf_werden_step1&user=Welnessmeyer">&nbsp;Welnessmeyer&nbsp;(43)</a></p></div>

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

  • Info Line 1069, Column 32: start tag was here
        <p class="region_username"><image src="images/symbol_m.gif" width="7" heigh…
  • Warning Line 1074, Column 125: reference not terminated by REFC delimiter
    …"Bilder von Ellinor" href="index.php?page=fischkopf_werden_step1&user=Ellinor">

    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 1074, Column 125: reference to external entity in attribute value
    …"Bilder von Ellinor" href="index.php?page=fischkopf_werden_step1&user=Ellinor">

    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 1074, Column 125: reference to entity "user" for which no system identifier could be generated
    …"Bilder von Ellinor" href="index.php?page=fischkopf_werden_step1&user=Ellinor">

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1075, Column 200: end tag for "img" omitted, but OMITTAG NO was specified
    ….jpg"  alt="x" title="Bilder gross/Weitere Bilder von Ellinor"></a></div></div>

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

  • Info Line 1075, Column 6: start tag was here
         <img style="vertical-align:middle; margin: auto;" border="0" src="http://u…
  • Error Line 1076, Column 85: element "image" undefined
    …ges/symbol_f.gif" width="7" height="8"><a  class="black useronlinelink" href="…

    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 1076, Column 167: reference not terminated by REFC delimiter
    …x.php?page=fischkopf_werden_step1&user=Ellinor">&nbsp;Ellinor&nbsp;(26)</a></p…

    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 1076, Column 167: reference to external entity in attribute value
    …x.php?page=fischkopf_werden_step1&user=Ellinor">&nbsp;Ellinor&nbsp;(26)</a></p…

    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 1076, Column 167: reference to entity "user" for which no system identifier could be generated
    …x.php?page=fischkopf_werden_step1&user=Ellinor">&nbsp;Ellinor&nbsp;(26)</a></p…

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1076, Column 207: end tag for "image" omitted, but OMITTAG NO was specified
    …page=fischkopf_werden_step1&user=Ellinor">&nbsp;Ellinor&nbsp;(26)</a></p></div>

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

  • Info Line 1076, Column 32: start tag was here
        <p class="region_username"><image src="images/symbol_f.gif" width="7" heigh…
  • Warning Line 1081, Column 125: reference not terminated by REFC delimiter
    …"Bilder von huemmer" href="index.php?page=fischkopf_werden_step1&user=huemmer">

    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 1081, Column 125: reference to external entity in attribute value
    …"Bilder von huemmer" href="index.php?page=fischkopf_werden_step1&user=huemmer">

    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 1081, Column 125: reference to entity "user" for which no system identifier could be generated
    …"Bilder von huemmer" href="index.php?page=fischkopf_werden_step1&user=huemmer">

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1082, Column 195: end tag for "img" omitted, but OMITTAG NO was specified
    ….jpg"  alt="x" title="Bilder gross/Weitere Bilder von huemmer"></a></div></div>

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

  • Info Line 1082, Column 6: start tag was here
         <img style="vertical-align:middle; margin: auto;" border="0" src="http://u…
  • Error Line 1083, Column 85: element "image" undefined
    …ges/symbol_m.gif" width="7" height="8"><a  class="black useronlinelink" href="…

    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 1083, Column 167: reference not terminated by REFC delimiter
    …x.php?page=fischkopf_werden_step1&user=huemmer">&nbsp;huemmer&nbsp;(38)</a></p…

    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 1083, Column 167: reference to external entity in attribute value
    …x.php?page=fischkopf_werden_step1&user=huemmer">&nbsp;huemmer&nbsp;(38)</a></p…

    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 1083, Column 167: reference to entity "user" for which no system identifier could be generated
    …x.php?page=fischkopf_werden_step1&user=huemmer">&nbsp;huemmer&nbsp;(38)</a></p…

    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 1018, Column 121: entity was defined here
    …ilder von Zugewinn" href="index.php?page=fischkopf_werden_step1&user=Zugewinn">
  • Error Line 1083, Column 207: end tag for "image" omitted, but OMITTAG NO was specified
    …page=fischkopf_werden_step1&user=huemmer">&nbsp;huemmer&nbsp;(38)</a></p></div>

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

  • Info Line 1083, Column 32: start tag was here
        <p class="region_username"><image src="images/symbol_m.gif" width="7" heigh…
  • Error Line 1133, Column 113: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    …com.ivwbox.de/cgi-bin/ivw/CP/set_signup1;" width="1" height="1" alt="szmtag" />

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

    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.

Visitor Analysis

Daily Visitor
  • 3.033 visits
Daily Visitor

In Page Analysis