Bravo.de - die Webseite der größten deutschen Jugendzeitschrift mit aktuellen News zu Stars, Musik, Fashion, Lifestyle und Dr.Sommer. ...

bravo.de
  • Domain Name
    bravo.de
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #22128
  • Page Size
    278.5 KB
  • Ip Address
    195.39.234.253
  • Heading
    H1: 1, H2: 21, H3: 12, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 120 JPG, 83 PNG

Website Meta Analysis

  • Title
    BRAVO Homepage | Star News, Musik, Lifestyle & Fun | BRAVO.de
  • Meta Keyword
    BRAVO, Dr.Sommer, Stars, News, Fashion, Lifestyle, Musik, Fun, Fotolovestory, Online-Games
  • Meta Description
    Bravo.de - die Webseite der größten deutschen Jugendzeitschrift mit aktuellen News zu Stars, Musik, Fashion, Lifestyle und Dr.Sommer.

Technical Analysis

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

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

HTML Analysis

  • date: Fri, 16 Aug 2013 11:38:33 GMT
  • server: Apache
  • expires: Sun, 19 Nov 1978 05:00:00 GMT
  • cache-control: store, no-cache, must-revalidate
  • x-content-age: 12
  • vary: User-Agent,Accept-Encoding
  • x-server: 15
  • content-encoding: gzip
  • content-length: 28048
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% Copyright (c) 2010 by DENIC
% Version: 2.0
%
% Restricted rights.
%
% Terms and Conditions of Use
%
% The data in this record is provided by DENIC for informational purposes only.
% DENIC does not guarantee its accuracy and cannot, under any circumstances,
% be held liable in case the stored information would prove to be wrong,
% incomplete or not accurate in any sense.
%
% All the domain data that is visible in the whois service is protected by law.
% It is not permitted to use it for any purpose other than technical or
% administrative requirements associated with the operation of the Internet.
% It is explicitly forbidden to extract, copy and/or use or re-utilise in any
% form and by any means (electronically or not) the whole or a quantitatively
% or qualitatively substantial part of the contents of the whois database
% without prior and explicit written permission by DENIC.
% It is prohibited, in particular, to use it for transmission of unsolicited
% and/or commercial and/or advertising by phone, fax, e-mail or for any similar
% purposes.
%
% By maintaining the connection you assure that you have a legitimate interest
% in the data and that you will only use it for the stated purposes. You are
% aware that DENIC maintains the right to initiate legal proceedings against
% you in the event of any breach of this assurance and to bar you from using
% its whois service.
%
% The DENIC whois service on port 43 never discloses any information concerning
% the domain holder/administrative contact. Information concerning the domain
% holder/administrative contact can be obtained through use of our web-based
% whois service available at the DENIC website:
% http://www.denic.de/en/background/whois-service/webwhois.html
%

Domain: bravo.de
Nserver: lamens.hbv.de
Nserver: megans.hbv.de
Nserver: nextns.hbv.de
Nserver: secns.hbv.de
Status: connect
Changed: 2010-09-23T15:49:14+02:00

[Tech-C]
Type: PERSON
Name: Kay-Thilo Frietzsche
Address: Burchardstr. 11
PostalCode: 20099
City: Hamburg
CountryCode: DE
Phone: +49 40 30193900
Fax: +49 40 30193910
Email: email
Changed: 2009-10-13T11:05:08+02:00

[Zone-C]
Type: PERSON
Name: Kay-Thilo Frietzsche
Address: Burchardstr. 11
PostalCode: 20099
City: Hamburg
CountryCode: DE
Phone: +49 40 30193900
Fax: +49 40 30193910
Email: email
Changed: 2009-10-13T11:05:08+02:00

DNS Analysis


DNS servers
lamens.hbv.de [195.39.235.209]
secns.hbv.de [213.191.74.120]
megans.hbv.de [195.39.235.210]
nextns.hbv.de [83.169.46.169]


DNS Records

Answer records
bravo.de SOA
server: megans.hbv.de
email: hostmaster@hbv.de
serial: 2012113000
refresh: 86400
retry: 7200
expire: 604800
minimum ttl: 3600
1800s
bravo.de NS  lamens.hbv.de 1800s
bravo.de NS  secns.hbv.de 1800s
bravo.de NS  nextns.hbv.de 1800s
bravo.de NS  megans.hbv.de 1800s
bravo.de MX
preference: 100
exchange: mgw02.bauerverlag.de
1800s
bravo.de MX
preference: 100
exchange: mgw01.bauerverlag.de
1800s
bravo.de A 195.39.234.253 1800s

Authority records

Additional records
secns.hbv.de A 213.191.74.120 300s
lamens.hbv.de A 195.39.235.209 300s
megans.hbv.de A 195.39.235.210 300s
nextns.hbv.de A 83.169.46.169 300s
mgw01.bauerverlag.de A 195.39.234.73 3600s
mgw02.bauerverlag.de A 195.39.234.74 3600s

IP 195.39.234.253 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    Hamburg
  • Continent Code
    EU
  • Latitude
    53.55
  • Longitude
    10.
  • No whois ip data for 195.39.234.253

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 172 Errors
  • 124 Warnings
Ratio Text/Html
  • 0.580056726349705
Message Error
  • Error Line 2, Column 92: there is no attribute "prefix"
    …xml:lang="de" dir="ltr"> <head prefix="og: http://ogp.me/ns# fb: http://ogp.me…

    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 4, Column 16: there is no attribute "property"
    <meta property="og:title" content='BRAVO Homepage | Dr. Sommer, Star News, Musi…

    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 4, Column 93: character "&" is the first character of a delimiter but occurred as data
    …le" content='BRAVO Homepage | Dr. Sommer, Star News, Musik, Lifestyle & Fun' />

    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 51, Column 23: document type does not allow element "style" here
    <style type="text/css">.i_ecnr_g_caa8d25221 a, .i_ecnr_g_caa8d25221 div.mb_tsh,…

    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 60, Column 15048: cannot generate system identifier for general entity "utm_medium"
    …"http://blingee.com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_…

    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 60, Column 15048: general entity "utm_medium" not defined and no default entity
    …"http://blingee.com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_…

    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 60, Column 15058: reference not terminated by REFC delimiter
    …ingee.com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250">Bling…

    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 60, Column 15058: reference to external entity in attribute value
    …ingee.com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250">Bling…

    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 60, Column 15058: reference to entity "utm_medium" for which no system identifier could be generated
    …ingee.com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250">Bling…

    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 60, Column 15047: entity was defined here
    …="http://blingee.com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen…
  • Warning Line 60, Column 15065: cannot generate system identifier for general entity "utm_campaign"
    …om/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250">Blingee</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 60, Column 15065: general entity "utm_campaign" not defined and no default entity
    …om/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250">Blingee</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 60, Column 15077: reference not terminated by REFC delimiter
    …ce=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250">Blingee</a></div></div><…

    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 60, Column 15077: reference to external entity in attribute value
    …ce=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250">Blingee</a></div></div><…

    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 60, Column 15077: reference to entity "utm_campaign" for which no system identifier could be generated
    …ce=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250">Blingee</a></div></div><…

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

  • Info Line 60, Column 15064: entity was defined here
    …com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250">Blingee</a>…
  • Warning Line 60, Column 16361: reference not terminated by REFC delimiter
    …ingee.com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250" title…

    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 60, Column 16361: reference to external entity in attribute value
    …ingee.com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250" title…

    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 60, Column 16361: reference to entity "utm_medium" for which no system identifier could be generated
    …ingee.com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250" title…

    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 60, Column 15047: entity was defined here
    …="http://blingee.com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen…
  • Warning Line 60, Column 16380: reference not terminated by REFC delimiter
    …ce=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250" title=""><img alt="" src…

    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 60, Column 16380: reference to external entity in attribute value
    …ce=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250" title=""><img alt="" src…

    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 60, Column 16380: reference to entity "utm_campaign" for which no system identifier could be generated
    …ce=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250" title=""><img alt="" src…

    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 60, Column 15064: entity was defined here
    …com/?utm_source=bravo&utm_medium=bravo&utm_campaign=bravo_gen_250">Blingee</a>…
  • Warning Line 60, Column 28050: cannot generate system identifier for general entity "et_lid"
    …/zeitschriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_su…

    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 60, Column 28050: general entity "et_lid" not defined and no default entity
    …/zeitschriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_su…

    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 60, Column 28056: reference not terminated by REFC delimiter
    …chriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_…

    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 60, Column 28056: reference to external entity in attribute value
    …chriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_…

    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 60, Column 28056: reference to entity "et_lid" for which no system identifier could be generated
    …chriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_…

    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 60, Column 28049: entity was defined here
    …o/zeitschriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_s…
  • Warning Line 60, Column 28060: cannot generate system identifier for general entity "et_sub"
    …ften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_abob…

    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 60, Column 28060: general entity "et_sub" not defined and no default entity
    …ften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_abob…

    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 60, Column 28066: reference not terminated by REFC delimiter
    …ugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_abobutton"…

    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 60, Column 28066: reference to external entity in attribute value
    …ugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_abobutton"…

    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 60, Column 28066: reference to entity "et_sub" for which no system identifier could be generated
    …ugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_abobutton"…

    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 60, Column 28059: entity was defined here
    …iften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_abo…
  • Warning Line 60, Column 29761: reference not terminated by REFC delimiter
    …chriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abo…

    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 60, Column 29761: reference to external entity in attribute value
    …chriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abo…

    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 60, Column 29761: reference to entity "et_lid" for which no system identifier could be generated
    …chriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abo…

    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 60, Column 28049: entity was defined here
    …o/zeitschriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_s…
  • Warning Line 60, Column 29771: reference not terminated by REFC delimiter
    …ugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abobutton" ti…

    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 60, Column 29771: reference to external entity in attribute value
    …ugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abobutton" ti…

    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 60, Column 29771: reference to entity "et_sub" for which no system identifier could be generated
    …ugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abobutton" ti…

    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 60, Column 28059: entity was defined here
    …iften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_abo…
  • Warning Line 60, Column 30610: reference not terminated by REFC delimiter
    …chriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abo…

    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 60, Column 30610: reference to external entity in attribute value
    …chriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abo…

    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 60, Column 30610: reference to entity "et_lid" for which no system identifier could be generated
    …chriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abo…

    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 60, Column 28049: entity was defined here
    …o/zeitschriften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_s…
  • Warning Line 60, Column 30620: reference not terminated by REFC delimiter
    …ugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abobutton" ti…

    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 60, Column 30620: reference to external entity in attribute value
    …ugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abobutton" ti…

    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 60, Column 30620: reference to entity "et_sub" for which no system identifier could be generated
    …ugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_navi_abobutton" ti…

    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 60, Column 28059: entity was defined here
    …iften/jugend/BRAVO/?et_cid=8&et_lid=33&et_sub=BV_startseite_header_subnavi_abo…
  • Error Line 74, Column 1053: required attribute "alt" not specified
    …et-k-siw.png" height="6px" width="4px"></img><h1 class="v7ggv4p grtimgv ckfuvk…

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

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

  • Error Line 74, Column 1422: document type does not allow element "form" here
    …rm method="post" action="/quicksearch"><input id="search_box" type="text" name…

    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 74, Column 1894: there is no attribute "autocomplete"
    …t 6px 5px 10px #C9C9C9;" autocomplete="off"><input type="image" src="http://br…

    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 74, Column 1900: end tag for "input" omitted, but OMITTAG NO was specified
    …5px 10px #C9C9C9;" autocomplete="off"><input type="image" src="http://brav0.de…

    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 74, Column 1423: start tag was here
    …m method="post" action="/quicksearch"><input id="search_box" type="text" name=…
  • Error Line 74, Column 2112: end tag for "input" omitted, but OMITTAG NO was specified
    … left; width: 100px; background-color: #FF8400; height: 28px;"></div></form>');

    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 74, Column 1900: start tag was here
    …5px 10px #C9C9C9;" autocomplete="off"><input type="image" src="http://brav0.de…
  • Error Line 74, Column 2112: end tag for "form" omitted, but OMITTAG NO was specified
    … left; width: 100px; background-color: #FF8400; height: 28px;"></div></form>');

    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 74, Column 1381: start tag was here
    …st Du auf BRAVO.de";document.writeln('<form method="post" action="/quicksearch…
  • Error Line 74, Column 2112: end tag for "script" omitted, but OMITTAG NO was specified
    … left; width: 100px; background-color: #FF8400; height: 28px;"></div></form>');

    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 74, Column 1235: start tag was here
    …85px; z-index: 5;"><div class="chtbr"><script type="text/javascript">var BMG_C…
  • Error Line 74, Column 2119: end tag for element "form" which is not open
    … left; width: 100px; background-color: #FF8400; height: 28px;"></div></form>');

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

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

  • Error Line 75, Column 9: end tag for element "script" which is not open
    </script></div></div><div class="tpps_i2pcem4r" style="left: 8px; top: 89px; z-…

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

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

  • Error Line 75, Column 215: required attribute "alt" not specified
    …0.de/bilder/nativex21/7dul-u8FH.png" /></a></div></div></div></div></div></div…

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

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

  • Error Line 76, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Error Line 83, Column 317: required attribute "alt" not specified
    …ize=1082x250;cookie=info;alias=bvo_pb_homepage;KEY=" border="0"></a></noscript>

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

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

  • Error Line 83, Column 321: end tag for "img" omitted, but OMITTAG NO was specified
    …ize=1082x250;cookie=info;alias=bvo_pb_homepage;KEY=" border="0"></a></noscript>

    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 83, Column 171: start tag was here
    …bvo_pb_homepage;KEY=" target="_blank"><img src="http://adserver.adtech.de/adse…
  • Error Line 86, Column 1973: invalid comment declaration: found digit outside comment but inside comment declaration
    …132x72\/star-profil-daniel-radcliffe--7hnh-_vV_.jpg","url":"\/star\/daniel-rad…
  • Info Line 85, Column 1: comment declaration started here
    <!--
  • Error Line 88, Column 5465: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …mp; Tampons: Das musst du wissen!"><h2>Sex &amp; Tampons</h2></a></div></div><…

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

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

  • Error Line 88, Column 6873: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ix: Unser Freundschafts-Geheimnis"><h2>Ihr Freundschafts-Geheimnis</h2></a></d…

    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 88, Column 8010: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … die Coaches bei 'The Voice Kids'"><h2>Das sind die Coaches</h2></a></div></di…

    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 88, Column 9051: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …arah und Pietro sind verheiratet!"><h2>Das Paar hat geheiratet!</h2></a></div>…

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

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

  • Error Line 88, Column 10135: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …y Depp: Zwei neue Rollen am Start"><h2>Zwei neue Rollen am Start</h2></a></div…

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

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

  • Error Line 88, Column 11540: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"Mein Penis ist schlaff zu klein!"><h2>Mein Penis ist schlaff zu klein!</h2></…

    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 88, Column 13425: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ch schäme mich für meinen Körper!"><h2>Ich fühle mich zu dick!</h2></a></div><…

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

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

  • Error Line 88, Column 14797: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … So klappt das Einführen richtig!"><h2>Die Tampon-Galerie!</h2></a></div></div…

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

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

  • Error Line 88, Column 16216: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="Beauty-Pflege: Schön mit Ananas"><h2>Schön mit Ananas</h2></a></div></div><d…

    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 88, Column 17253: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …scars 2013: Die Outfits der Stars"><h2>Die Outfits der Stars</h2></a></div></d…

    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 88, Column 18242: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …title="Sexy Wimpern wie die Stars"><h2>Sexy Wimpern wie Sel &amp; Co.</h2></a>…

    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 88, Column 21168: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …irtdoktor" title="Der Flirtdoktor"><h2>Der Flirtdoktor</h2></a></div></div><di…

    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 88, Column 22264: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Chancen bei einem/einer Älteren? "><h2>Hast Du Chancen bei Älteren?</h2></a></…

    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 88, Column 23298: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ewig" title="Für immer &amp; ewig"><h2>Für immer &amp; ewig</h2></a></div></di…

    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 88, Column 25153: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ie Schönheit im Frühling braucht!"><h2>Neue Frühlings-Produkte</h2></a></div><…

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

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

  • Error Line 88, Column 26675: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e="Test: Welcher Job-Typ bist Du?"><h2>Welcher Job-Typ bist Du?</h2></a></div>…

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

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

  • Error Line 88, Column 27935: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …title="Frag Julia - Folge 3/2013!"><h2>Frag Julia - Folge 3/2013!</h2></a></di…

    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 88, Column 29199: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …no Online: Aufbau-Spaß im Browser"><h2>Anno ist online</h2></a></div></div><di…

    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 88, Column 30118: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …" title="Spiele-Offensive für 3DS"><h2>Spiele-Offensive für 3DS</h2></a></div>…

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

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

  • Error Line 88, Column 31139: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …est" title="Hot-List: 10 Sätze..."><h2>10 Sätze...</h2></a></div></div><div cl…

    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 88, Column 37688: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …e="Der neue Stundenplan-Designer!"><h2>Mit vielen coolen Motiven!</h2></a></di…

    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 96, Column 768: end tag for "input" omitted, but OMITTAG NO was specified
    …="hidden" name="login" value="submit"> <input id="fib7ba6433c1" class="ma7uqtw…

    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 96, Column 719: start tag was here
    …me" value="Benutzername" type="text"/><input type="hidden" name="login" value=…
  • Error Line 96, Column 6131: there is no attribute "async"
    …status?no_cache=20130302170206" async="true"></script><!-- BRAVO-PHP_COMMUNITY…

    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 102, Column 104: cannot generate system identifier for general entity "t"
    …ravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hy…

    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 102, Column 104: general entity "t" not defined and no default entity
    …ravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hy…

    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 102, Column 105: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 102, Column 105: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 102, Column 105: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 102, Column 113: cannot generate system identifier for general entity "p"
    …oards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">…

    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 102, Column 113: general entity "p" not defined and no default entity
    …oards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">…

    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 102, Column 114: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"><…

    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 102, Column 114: reference to external entity in attribute value
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"><…

    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 102, Column 114: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"><…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 103, Column 127: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 103, Column 127: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 103, Column 127: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 103, Column 136: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">B…

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

  • Warning Line 103, Column 136: reference to external entity in attribute value
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">B…

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

  • Error Line 103, Column 136: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">B…

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

  • Info Line 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 104, Column 131: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 104, Column 131: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 104, Column 131: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 104, Column 140: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">L…

    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 104, Column 140: reference to external entity in attribute value
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">L…

    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 104, Column 140: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">L…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 106, Column 247: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 106, Column 247: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 106, Column 247: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 106, Column 256: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">z…

    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 106, Column 256: reference to external entity in attribute value
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">z…

    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 106, Column 256: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink">z…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 107, Column 237: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 107, Column 237: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 107, Column 237: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 107, Column 246: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"><…

    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 107, Column 246: reference to external entity in attribute value
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"><…

    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 107, Column 246: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"><…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Error Line 107, Column 397: end tag for "img" omitted, but OMITTAG NO was specified
    …ds/styles/bravo/imageset/platz1.png" alt="Boardspiele - Länderkette"></a></div>

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

  • Info Line 107, Column 285: start tag was here
    …11689046#p11689046" class="hyperlink"><img src="http://community.bravo.de/boar…
  • Warning Line 117, Column 129: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

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

  • Warning Line 117, Column 129: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

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

  • Error Line 117, Column 129: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 117, Column 138: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink"><…

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

  • Warning Line 117, Column 138: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink"><…

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

  • Error Line 117, Column 138: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink"><…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 118, Column 151: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 118, Column 151: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 118, Column 151: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 118, Column 160: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink">L…

    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 118, Column 160: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink">L…

    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 118, Column 160: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink">L…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 119, Column 155: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 119, Column 155: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 119, Column 155: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 119, Column 164: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink">F…

    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 119, Column 164: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink">F…

    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 119, Column 164: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink">F…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 121, Column 271: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 121, Column 271: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 121, Column 271: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 121, Column 280: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink">z…

    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 121, Column 280: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink">z…

    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 121, Column 280: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink">z…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 122, Column 261: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 122, Column 261: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 122, Column 261: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 122, Column 270: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink"><…

    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 122, Column 270: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink"><…

    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 122, Column 270: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=331818&p=11689045#p11689045" class="hyperlink"><…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Error Line 122, Column 445: end tag for "img" omitted, but OMITTAG NO was specified
    …/platz2.png" alt="Lifestyle - Foto-Lovestory: Hoffnungslos verliebt"></a></div>

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

  • Info Line 122, Column 309: start tag was here
    …11689045#p11689045" class="hyperlink"><img src="http://community.bravo.de/boar…
  • Warning Line 132, Column 136: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 132, Column 136: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 132, Column 136: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 132, Column 145: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink"><…

    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 132, Column 145: reference to external entity in attribute value
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink"><…

    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 132, Column 145: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink"><…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 133, Column 158: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 133, Column 158: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 133, Column 158: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 133, Column 167: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink">G…

    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 133, Column 167: reference to external entity in attribute value
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink">G…

    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 133, Column 167: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink">G…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 134, Column 162: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 134, Column 162: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 134, Column 162: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 134, Column 171: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink">B…

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

  • Warning Line 134, Column 171: reference to external entity in attribute value
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink">B…

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

  • Error Line 134, Column 171: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink">B…

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

  • Info Line 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 136, Column 278: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 136, Column 278: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 136, Column 278: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 136, Column 287: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink">z…

    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 136, Column 287: reference to external entity in attribute value
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink">z…

    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 136, Column 287: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink">z…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 137, Column 268: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 137, Column 268: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 137, Column 268: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 137, Column 277: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink"><…

    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 137, Column 277: reference to external entity in attribute value
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink"><…

    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 137, Column 277: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=169708&t=332151&p=11689044#p11689044" class="hyperlink"><…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Error Line 137, Column 459: end tag for "img" omitted, but OMITTAG NO was specified
    ….png" alt="Gedanken, Sorgen &amp; Kummer - Bitte gebt mir Tipps! :("></a></div>

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

  • Info Line 137, Column 316: start tag was here
    …11689044#p11689044" class="hyperlink"><img src="http://community.bravo.de/boar…
  • Warning Line 147, Column 129: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 147, Column 129: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 147, Column 129: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 147, Column 138: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink"><…

    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 147, Column 138: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink"><…

    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 147, Column 138: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink"><…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 148, Column 151: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 148, Column 151: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 148, Column 151: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 148, Column 160: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink">L…

    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 148, Column 160: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink">L…

    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 148, Column 160: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink">L…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 149, Column 155: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 149, Column 155: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 149, Column 155: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 149, Column 164: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink">F…

    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 149, Column 164: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink">F…

    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 149, Column 164: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink">F…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 151, Column 271: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 151, Column 271: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 151, Column 271: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 151, Column 280: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink">z…

    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 151, Column 280: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink">z…

    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 151, Column 280: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink">z…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 152, Column 261: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 152, Column 261: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 152, Column 261: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 152, Column 270: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink"><…

    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 152, Column 270: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink"><…

    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 152, Column 270: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=324183&p=11689043#p11689043" class="hyperlink"><…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Error Line 152, Column 445: end tag for "img" omitted, but OMITTAG NO was specified
    …/platz4.png" alt="Lifestyle - Foto-Lovestory: Das verflixte 1. Mal!"></a></div>

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

  • Info Line 152, Column 309: start tag was here
    …11689043#p11689043" class="hyperlink"><img src="http://community.bravo.de/boar…
  • Warning Line 162, Column 144: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 162, Column 144: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 162, Column 144: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 162, Column 153: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink"><…

    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 162, Column 153: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink"><…

    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 162, Column 153: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink"><…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 163, Column 166: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 163, Column 166: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 163, Column 166: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 163, Column 175: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink">L…

    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 163, Column 175: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink">L…

    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 163, Column 175: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink">L…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 164, Column 170: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 164, Column 170: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 164, Column 170: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 164, Column 179: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink">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 164, Column 179: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink">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 164, Column 179: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink">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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 166, Column 286: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 166, Column 286: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 166, Column 286: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 166, Column 295: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink">z…

    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 166, Column 295: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink">z…

    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 166, Column 295: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink">z…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Warning Line 167, Column 276: reference not terminated by REFC delimiter
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 167, Column 276: reference to external entity in attribute value
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 167, Column 276: reference to entity "t" for which no system identifier could be generated
    …avo.de/boards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyp…

    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 102, Column 103: entity was defined here
    …bravo.de/boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="h…
  • Warning Line 167, Column 285: reference not terminated by REFC delimiter
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink"><…

    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 167, Column 285: reference to external entity in attribute value
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink"><…

    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 167, Column 285: reference to entity "p" for which no system identifier could be generated
    …ards/viewtopic.php?f=248798&t=323998&p=11689042#p11689042" class="hyperlink"><…

    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 102, Column 112: entity was defined here
    …boards/viewtopic.php?f=248724&t=331307&p=11689046#p11689046" class="hyperlink"…
  • Error Line 167, Column 475: end tag for "img" omitted, but OMITTAG NO was specified
    …t="Lifestyle - Psychotest: Worauf wirst Du in 60 Jahren stolz sein?"></a></div>

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

  • Info Line 167, Column 324: start tag was here
    …11689042#p11689042" class="hyperlink"><img src="http://community.bravo.de/boar…
  • Error Line 180, Column 101: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …class="ccolor" style="background-color:#fde302"></span><h3>Stars</h3></a></div>

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

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

  • Error Line 191, Column 104: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="ccolor" style="background-color:#db020c"></span><h3>Dr. Sommer</h3></a></div>

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

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

  • Error Line 200, Column 104: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="ccolor" style="background-color:#04ac8f"></span><h3>Lifestyle</h3></a></div>

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

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

  • Error Line 210, Column 98: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …n class="ccolor" style="background-color:#31bcfd"></span><h3>Fun</h3></a></div>

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

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

  • Error Line 216, Column 98: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …n class="ccolor" style="background-color:#32F9F9"></span><h3>LoL</h3></a></div>

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

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

  • Error Line 218, Column 101: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …lass="ccolor" style="background-color:#006925"></span><h3>Wissen</h3></a></div>

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

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

  • Error Line 220, Column 127: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …s="ccolor" style="background-color:#75D802"></span><h3>Community</h3></a></div>

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

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

  • Error Line 227, Column 101: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"ccolor" style="background-color:#fde302"></span><h3>Deine Stars</h3></a></div>

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

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

  • Error Line 241, Column 101: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"ccolor" style="background-color:#fde302"></span><h3>Deine Shows</h3></a></div>

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

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

  • Error Line 254, Column 69: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …><a href="/family/"><span class="ccolor"></span><h3>BRAVO Family</h3></a></div>

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

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

  • Error Line 266, Column 69: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …href="/family/"><span class="ccolor"></span><h3>BRAVO.de Partner</h3></a></div>

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

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

  • Error Line 273, Column 85: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …//www.bravosport.de"><span class="ccolor"></span><h3>BRAVO Sport</h3></a></div>

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

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

  • Error Line 288, Column 389: document type does not allow element "div" here
    …;};document.writeln('<div id="fb-root"><scr'+'ipt type="text/javascript" src="…

    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 288, Column 394: an attribute specification must start with a name or name token
    …cument.writeln('<div id="fb-root"><scr'+'ipt type="text/javascript" src="http:…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 288, Column 394: element "scr" undefined
    …cument.writeln('<div id="fb-root"><scr'+'ipt type="text/javascript" src="http:…

    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 288, Column 490: delimiter "'" invalid: only S separators and TAGC allowed here
    ….net/de_DE/all.js" async="async"></scr'+'ipt></div>');document.writeln('<scr'+…
  • Error Line 288, Column 528: an attribute specification must start with a name or name token
    …'+'ipt></div>');document.writeln('<scr'+'ipt type="text/javascript" src="https…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 288, Column 528: element "scr" undefined
    …'+'ipt></div>');document.writeln('<scr'+'ipt type="text/javascript" src="https…

    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 288, Column 621: delimiter "'" invalid: only S separators and TAGC allowed here
    …ipt" src="https://apis.google.com/js/plusone.js" async="async"></scr'+'ipt>');}
  • Error Line 289, Column 81: an attribute specification must start with a name or name token
    …e_placement') ){document.writeln('<scr'+'ipt type="text/javascript" src="https…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 289, Column 81: element "scr" undefined
    …e_placement') ){document.writeln('<scr'+'ipt type="text/javascript" src="https…

    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 289, Column 174: delimiter "'" invalid: only S separators and TAGC allowed here
    …com/js/plusone.js" async="async"></scr'+'ipt>');document.writeln('<scr'+'ipt t…
  • Error Line 289, Column 206: an attribute specification must start with a name or name token
    …></scr'+'ipt>');document.writeln('<scr'+'ipt type="text/javascript" src="http:…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 289, Column 206: element "scr" undefined
    …></scr'+'ipt>');document.writeln('<scr'+'ipt type="text/javascript" src="http:…

    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 289, Column 287: delimiter "'" invalid: only S separators and TAGC allowed here
    …text/javascript" src="http://assets.pinterest.com/js/pinit.js"></scr'+'ipt>');}
  • Error Line 290, Column 89: end tag for element "div" which is not open
    …v style="clear: both;"></div></div></div></div></div></div></div></body></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
  • 5.717 visits