Das größte deutsche Spaß-Portal. Tausende lustige Bilder, Witze, Videos und vieles mehr - natürlich völlig kostenlos. Jetzt klicken und mitlachen! ...

lustich.de
  • Domain Name
    lustich.de
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #61514
  • Page Size
    132.3 KB
  • Ip Address
    46.4.199.131
  • Heading
    H1: 0, H2: 4, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    47 GIF, 82 JPG, 1 PNG

Website Meta Analysis

  • Title
    Das Fun-Portal gegen Langeweile - lustig, lachen, witzig - lustich.de
  • Meta Keyword
    lustig, witzig, fun, lachen, spaß, humor, unterhaltung, entertainment
  • Meta Description
    Das größte deutsche Spaß-Portal. Tausende lustige Bilder, Witze, Videos und vieles mehr - natürlich völlig kostenlos. Jetzt klicken und mitlachen!

Technical Analysis

  • Webserver
    Apache/2.2.14 (Ubuntu)
  • Ip Address
    46.4.199.131
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 24 Aug 2013 21:48:44 GMT
  • server: Apache/2.2.14 (Ubuntu)
  • x-powered-by: PHP/5.3.2-1ubuntu4.20
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 16809
  • connection: close
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for lustich.de

DNS Analysis


DNS servers
ns1.ns-serve.net [193.254.189.162]
ns2.ns-serve.net [83.243.59.34]


DNS Records

Answer records
lustich.de NS  ns1.ns-serve.net 14400s
lustich.de MX
preference: 30
exchange: ASPMX4.GOOGLEMAIL.COM
86400s
lustich.de MX
preference: 20
exchange: ALT2.ASPMX.L.GOOGLE.COM
86400s
lustich.de MX
preference: 30
exchange: ASPMX2.GOOGLEMAIL.COM
86400s
lustich.de NS  ns2.ns-serve.net 14400s
lustich.de TXT v=spf1 ip4:46.4.199.158 include:_spf.google.com ~all 86400s
lustich.de SOA
server: ns1.ns-serve.net
email: root@ns1.ns-serve.net
serial: 1349467606
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
14400s
lustich.de MX
preference: 10
exchange: ASPMX.L.GOOGLE.COM
86400s
lustich.de MX
preference: 30
exchange: ASPMX3.GOOGLEMAIL.COM
86400s
lustich.de A 46.4.199.131 14400s
lustich.de MX
preference: 30
exchange: ASPMX5.GOOGLEMAIL.COM
86400s
lustich.de MX
preference: 20
exchange: ALT1.ASPMX.L.GOOGLE.COM
86400s

Authority records

Additional records

IP 46.4.199.131 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 153 Errors
  • 63 Warnings
Ratio Text/Html
  • 0.6544661441034498
Message Error
  • Error Line 13, Column 16: there is no attribute "property"
    <meta property="fb:admins" content="514282972,238600006" />

    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 112, Column 81: end tag for element "a" which is not open
    …a href="http://lustich.de/bilder/tiere/ich-hasse-alles/" class="plusBtn" /></a>

    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 147, Column 127: required attribute "alt" not specified
    …><img src="/img/defaults/blog_s.gif" /></a> <a href="http://lustich.de/fans/bl…

    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 160, Column 119: required attribute "alt" not specified
    …><img src="/img/defaults/blog_s.gif" /></a> <a href="http://lustich.de/fans/bl…

    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 175, Column 129: required attribute "alt" not specified
    …><img src="/img/defaults/blog_s.gif" /></a> <a href="http://lustich.de/fans/bl…

    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 191, Column 125: required attribute "alt" not specified
    …><img src="/img/defaults/blog_s.gif" /></a> <a href="http://lustich.de/fans/bl…

    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 206, Column 115: required attribute "alt" not specified
    …><img src="/img/defaults/blog_s.gif" /></a> <a href="http://lustich.de/fans/bl…

    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 626, Column 83: required attribute "alt" not specified
    … class="bottomLeftBg" src="http://lustich.de/img/la/big_box_foot_lft_bg.jpg" />

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

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

  • Error Line 628, Column 58: required attribute "alt" not specified
    				<img src="http://lustich.de/img/la/i/teas_foot.jpg" />

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

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

  • Error Line 630, Column 80: required attribute "alt" not specified
    				<img class="contentHeadline" src="http://lustich.de/img/txt/lustneui.gif" />

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

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

  • Error Line 645, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 648, Column 174: required attribute "alt" not specified
    …XxENIMANxXx/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 661, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 664, Column 172: required attribute "alt" not specified
    …/xxxHashxxx/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 677, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 680, Column 173: required attribute "alt" not specified
    …xXxjoshixXx/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 693, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 696, Column 205: required attribute "alt" not specified
    …ata7.lustich.de/userbilder/xs/8c385069cab5a2c6441fcd061ab95082.jpg" /></a></td>

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

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

  • Error Line 710, Column 167: required attribute "alt" not specified
    …ofil/Mike48/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 723, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 726, Column 189: required attribute "alt" not specified
    …g src="http://data6.lustich.de/userbilder/xs/7193864578_111948.jpg" /></a></td>

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

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

  • Error Line 739, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 742, Column 187: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/203a69a2c2_88609.jpg" /></a></td>

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

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

  • Error Line 755, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 758, Column 172: required attribute "alt" not specified
    …/xXxPataxXx/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 771, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 774, Column 190: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/f23ee2c88e_104674.jpg" /></a></td>

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

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

  • Error Line 787, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 790, Column 176: required attribute "alt" not specified
    …playaboyXxx/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 803, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 806, Column 168: required attribute "alt" not specified
    …ofil/XXXxxx/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 819, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 822, Column 169: required attribute "alt" not specified
    …fil/xxx_sex/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 835, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 838, Column 196: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/47949c6291_92645.jpg" /></a></td>

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

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

  • Error Line 851, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 854, Column 183: required attribute "alt" not specified
    …g src="http://data2.lustich.de/userbilder/xs/4d71c77b76_108982.jpg" /></a></td>

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

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

  • Error Line 868, Column 195: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/b98e5a6e50_29875.jpg" /></a></td>

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

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

  • Error Line 881, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 884, Column 171: required attribute "alt" not specified
    …l/xyzxyzxyz/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 897, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 900, Column 188: required attribute "alt" not specified
    …mg src="http://data.lustich.de/userbilder/xs/4f7310e6c6_112694.jpg" /></a></td>

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

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

  • Error Line 913, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 916, Column 188: required attribute "alt" not specified
    …mg src="http://data3.lustich.de/userbilder/xs/de2544942e_97296.jpg" /></a></td>

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

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

  • Error Line 929, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 932, Column 177: required attribute "alt" not specified
    …nkin_Park_X/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 945, Column 172: required attribute "alt" not specified
    …/namala1919/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 948, Column 187: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/73ca5254dc_103450.jpg" /></a></td>

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

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

  • Error Line 972, Column 188: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/e2e1469bd2_123931.jpg" /></a></td>

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

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

  • Error Line 987, Column 192: required attribute "alt" not specified
    …g src="http://data3.lustich.de/userbilder/xs/aa7d068379_122697.jpg" /></a></td>

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

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

  • Error Line 1002, Column 192: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/d2bb8f2878_97451.jpg" /></a></td>

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

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

  • Error Line 1017, Column 193: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/99c4d5b8b7_123535.png" /></a></td>

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

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

  • Error Line 1032, Column 99: required attribute "alt" not specified
    …                                   <img src="/img/defaults/user_xs.jpg" /></td>

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

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

  • Error Line 1047, Column 99: required attribute "alt" not specified
    …                                   <img src="/img/defaults/user_xs.jpg" /></td>

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

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

  • Error Line 1062, Column 195: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/ed7f8fc2e2_123557.jpg" /></a></td>

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

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

  • Error Line 1077, Column 192: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/d2bb8f2878_97451.jpg" /></a></td>

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

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

  • Error Line 1092, Column 169: required attribute "alt" not specified
    …ofil/schalo/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 1107, Column 190: required attribute "alt" not specified
    …g src="http://data6.lustich.de/userbilder/xs/8eecfc4f6b_122794.jpg" /></a></td>

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

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

  • Error Line 1122, Column 190: required attribute "alt" not specified
    …g src="http://data6.lustich.de/userbilder/xs/8eecfc4f6b_122794.jpg" /></a></td>

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

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

  • Error Line 1137, Column 190: required attribute "alt" not specified
    …g src="http://data6.lustich.de/userbilder/xs/8eecfc4f6b_122794.jpg" /></a></td>

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

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

  • Error Line 1152, Column 187: required attribute "alt" not specified
    …g src="http://data3.lustich.de/userbilder/xs/9f8efd00f9_101436.jpg" /></a></td>

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

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

  • Error Line 1167, Column 171: required attribute "alt" not specified
    …il/Lisa0809/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 1182, Column 170: required attribute "alt" not specified
    …fil/Tanja78/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 1197, Column 190: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/6d40ee4b40_121329.jpg" /></a></td>

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

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

  • Error Line 1212, Column 187: required attribute "alt" not specified
    …g src="http://data4.lustich.de/userbilder/xs/54589379f9_121990.jpg" /></a></td>

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

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

  • Error Line 1227, Column 200: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/404de6d1af_121481.png" /></a></td>

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

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

  • Error Line 1242, Column 186: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/949ba52c82_116830.jpg" /></a></td>

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

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

  • Error Line 1257, Column 172: required attribute "alt" not specified
    …l/Kornelius/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 1282, Column 185: required attribute "alt" not specified
    …g src="http://data2.lustich.de/userbilder/xs/b467330090_119218.jpg" /></a></td>

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

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

  • Error Line 1297, Column 184: required attribute "alt" not specified
    …mg src="http://data8.lustich.de/userbilder/xs/ad0d397c48_65103.gif" /></a></td>

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

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

  • Error Line 1312, Column 188: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/2c7b18e387_96936.jpg" /></a></td>

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

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

  • Error Line 1327, Column 188: required attribute "alt" not specified
    …g src="http://data4.lustich.de/userbilder/xs/5e52d7b092_114687.jpg" /></a></td>

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

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

  • Error Line 1342, Column 171: required attribute "alt" not specified
    …il/Sheep123/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 1357, Column 169: required attribute "alt" not specified
    …ofil/Mike48/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 1372, Column 192: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/692a4d6166_80913.gif" /></a></td>

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

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

  • Error Line 1387, Column 192: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/692a4d6166_80913.gif" /></a></td>

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

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

  • Error Line 1402, Column 188: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/2c7b18e387_96936.jpg" /></a></td>

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

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

  • Error Line 1417, Column 188: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/2c7b18e387_96936.jpg" /></a></td>

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

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

  • Error Line 1432, Column 187: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/2854b80023_114762.gif" /></a></td>

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

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

  • Error Line 1447, Column 184: required attribute "alt" not specified
    …mg src="http://data8.lustich.de/userbilder/xs/ad0d397c48_65103.gif" /></a></td>

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

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

  • Error Line 1462, Column 192: required attribute "alt" not specified
    …g src="http://data5.lustich.de/userbilder/xs/5771522168_124279.jpg" /></a></td>

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

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

  • Error Line 1477, Column 188: required attribute "alt" not specified
    …mg src="http://data7.lustich.de/userbilder/xs/2c7b18e387_96936.jpg" /></a></td>

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

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

  • Error Line 1492, Column 184: required attribute "alt" not specified
    …mg src="http://data8.lustich.de/userbilder/xs/ad0d397c48_65103.gif" /></a></td>

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

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

  • Error Line 1507, Column 186: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/cb498cc4d1_121227.gif" /></a></td>

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

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

  • Error Line 1522, Column 169: required attribute "alt" not specified
    …ofil/Mike48/"><img src="http://lustich.de/img/defaults/user_xs.jpg" /></a></td>

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

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

  • Error Line 1537, Column 184: required attribute "alt" not specified
    …mg src="http://data8.lustich.de/userbilder/xs/ad0d397c48_65103.gif" /></a></td>

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

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

  • Error Line 1552, Column 189: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/0e2a91c997_120049.jpg" /></a></td>

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

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

  • Error Line 1567, Column 196: required attribute "alt" not specified
    …g src="http://data7.lustich.de/userbilder/xs/ce7206100d_122448.gif" /></a></td>

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

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

  • Error Line 1620, Column 84: required attribute "alt" not specified
    …img src="http://lustich.de/img/txt/bistduauchlustich.gif" class="sbHeadline" />

    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 1622, Column 73: required attribute "alt" not specified
    	<img class="excalmation" src="http://lustich.de/img/icons/exmark.gif" />

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

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

  • Error Line 1625, Column 118: there is no attribute "src"
    …); return false;" class="uploadBtn"  src="http://lustich.de/img/i.gif" /></a>		

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

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

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

  • Error Line 1625, Column 153: end tag for element "a" which is not open
    …); return false;" class="uploadBtn"  src="http://lustich.de/img/i.gif" /></a>		

    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 1628, Column 71: required attribute "type" not specified
    								<script src="http://connect.facebook.net/de_DE/all.js#xfbml=1"></script>

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

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

  • Error Line 1629, Column 28: there is no attribute "profile_id"
    								<fb:fan profile_id="367268620158" href="http://www.facebook.com/lustich…

    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 1629, Column 48: there is no attribute "href"
    …fb:fan profile_id="367268620158" href="http://www.facebook.com/lustich.de" wid…

    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 1629, Column 91: there is no attribute "width"
    …://www.facebook.com/lustich.de" width="250" height="330" css="http://lustich.d…

    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 1629, Column 104: there is no attribute "height"
    …ok.com/lustich.de" width="250" height="330" css="http://lustich.de/css/fb.css?…

    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 1629, Column 114: there is no attribute "css"
    …tich.de" width="250" height="330" css="http://lustich.de/css/fb.css?1300382358…

    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 1629, Column 167: there is no attribute "show_faces"
    ….de/css/fb.css?1300382358" show_faces="true" stream="false" header="true" conn…

    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 1629, Column 181: there is no attribute "stream"
    …?1300382358" show_faces="true" stream="false" header="true" connections="12"><…

    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 1629, Column 196: there is no attribute "header"
    …2358" show_faces="true" stream="false" header="true" connections="12"></fb:fan>

    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 1629, Column 215: there is no attribute "connections"
    …2358" show_faces="true" stream="false" header="true" connections="12"></fb:fan>

    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 1629, Column 219: element "fb:fan" undefined
    …2358" show_faces="true" stream="false" header="true" connections="12"></fb:fan>

    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 1632, Column 27: there is no attribute "site"
    								<fb:activity site="lustich.de" width="250" height="300" header="true" f…

    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 1632, Column 46: there is no attribute "width"
    …	<fb:activity site="lustich.de" width="250" height="300" header="true" font=""…

    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 1632, Column 59: there is no attribute "height"
    … site="lustich.de" width="250" height="300" header="true" font="" border_color…

    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 1632, Column 72: there is no attribute "header"
    …h.de" width="250" height="300" header="true" font="" border_color="#99CCFF" re…

    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 1632, Column 84: there is no attribute "font"
    …"250" height="300" header="true" font="" border_color="#99CCFF" recommendation…

    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 1632, Column 100: there is no attribute "border_color"
    …0" header="true" font="" border_color="#99CCFF" recommendations="true"></fb:ac…

    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 1632, Column 126: there is no attribute "recommendations"
    …der="true" font="" border_color="#99CCFF" recommendations="true"></fb:activity>

    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 1632, Column 132: element "fb:activity" undefined
    …der="true" font="" border_color="#99CCFF" recommendations="true"></fb:activity>

    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 1634, Column 79: required attribute "alt" not specified
    				<img class="sbHeadline" src="http://lustich.de/img/txt/weristonline.gif" />

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

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

  • Error Line 1678, Column 7: required attribute "type" not specified
    <style>

    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 1678, Column 7: document type does not allow element "style" here
    <style>

    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 1720, Column 198: cannot generate system identifier for general entity "t"
    …eURIComponent('http://lustich.de/')+'&t=Das+Fun-Portal+gegen+Langeweile+-+lust…

    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 1720, Column 198: general entity "t" not defined and no default entity
    …eURIComponent('http://lustich.de/')+'&t=Das+Fun-Portal+gegen+Langeweile+-+lust…

    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 1720, Column 199: reference not terminated by REFC delimiter
    …URIComponent('http://lustich.de/')+'&t=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1720, Column 199: reference to external entity in attribute value
    …URIComponent('http://lustich.de/')+'&t=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1720, Column 199: reference to entity "t" for which no system identifier could be generated
    …URIComponent('http://lustich.de/')+'&t=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1720, Column 197: entity was defined here
    …deURIComponent('http://lustich.de/')+'&t=Das+Fun-Portal+gegen+Langeweile+-+lus…
  • Warning Line 1721, Column 87: cannot generate system identifier for general entity "u"
    …myspace.com/Modules/PostTo/Pages/?l=2&u=http://lustich.de/&t=Das+Fun-Portal+ge…

    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 1721, Column 87: general entity "u" not defined and no default entity
    …myspace.com/Modules/PostTo/Pages/?l=2&u=http://lustich.de/&t=Das+Fun-Portal+ge…

    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 1721, Column 88: reference not terminated by REFC delimiter
    …yspace.com/Modules/PostTo/Pages/?l=2&u=http://lustich.de/&t=Das+Fun-Portal+geg…

    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 1721, Column 88: reference to external entity in attribute value
    …yspace.com/Modules/PostTo/Pages/?l=2&u=http://lustich.de/&t=Das+Fun-Portal+geg…

    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 1721, Column 88: reference to entity "u" for which no system identifier could be generated
    …yspace.com/Modules/PostTo/Pages/?l=2&u=http://lustich.de/&t=Das+Fun-Portal+geg…

    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 1721, Column 86: entity was defined here
    ….myspace.com/Modules/PostTo/Pages/?l=2&u=http://lustich.de/&t=Das+Fun-Portal+g…
  • Warning Line 1721, Column 109: reference not terminated by REFC delimiter
    …stTo/Pages/?l=2&u=http://lustich.de/&t=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1721, Column 109: reference to external entity in attribute value
    …stTo/Pages/?l=2&u=http://lustich.de/&t=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1721, Column 109: reference to entity "t" for which no system identifier could be generated
    …stTo/Pages/?l=2&u=http://lustich.de/&t=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1720, Column 197: entity was defined here
    …deURIComponent('http://lustich.de/')+'&t=Das+Fun-Portal+gegen+Langeweile+-+lus…
  • Warning Line 1721, Column 171: cannot generate system identifier for general entity "c"
    …ngeweile+-+lustig%2C+lachen%2C+witzig&c=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9…

    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 1721, Column 171: general entity "c" not defined and no default entity
    …ngeweile+-+lustig%2C+lachen%2C+witzig&c=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9…

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

  • Warning Line 1721, Column 172: reference not terminated by REFC delimiter
    …geweile+-+lustig%2C+lachen%2C+witzig&c=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1721, Column 172: reference to external entity in attribute value
    …geweile+-+lustig%2C+lachen%2C+witzig&c=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1721, Column 172: reference to entity "c" for which no system identifier could be generated
    …geweile+-+lustig%2C+lachen%2C+witzig&c=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1721, Column 170: entity was defined here
    …angeweile+-+lustig%2C+lachen%2C+witzig&c=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%…
  • Warning Line 1722, Column 88: cannot generate system identifier for general entity "bm_url"
    …ister-wong.de/index.php?action=addurl&bm_url=http://lustich.de/&bm_description…

    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 1722, Column 88: general entity "bm_url" not defined and no default entity
    …ister-wong.de/index.php?action=addurl&bm_url=http://lustich.de/&bm_description…

    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 1722, Column 94: reference not terminated by REFC delimiter
    …wong.de/index.php?action=addurl&bm_url=http://lustich.de/&bm_description=Das+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 1722, Column 94: reference to external entity in attribute value
    …wong.de/index.php?action=addurl&bm_url=http://lustich.de/&bm_description=Das+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 1722, Column 94: reference to entity "bm_url" for which no system identifier could be generated
    …wong.de/index.php?action=addurl&bm_url=http://lustich.de/&bm_description=Das+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 1722, Column 87: entity was defined here
    …mister-wong.de/index.php?action=addurl&bm_url=http://lustich.de/&bm_descriptio…
  • Warning Line 1722, Column 114: cannot generate system identifier for general entity "bm_description"
    …tion=addurl&bm_url=http://lustich.de/&bm_description=Das+Fun-Portal+gegen+Lang…

    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 1722, Column 114: general entity "bm_description" not defined and no default entity
    …tion=addurl&bm_url=http://lustich.de/&bm_description=Das+Fun-Portal+gegen+Lang…

    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 1722, Column 128: reference not terminated by REFC delimiter
    …_url=http://lustich.de/&bm_description=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1722, Column 128: reference to external entity in attribute value
    …_url=http://lustich.de/&bm_description=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1722, Column 128: reference to entity "bm_description" for which no system identifier could be generated
    …_url=http://lustich.de/&bm_description=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1722, Column 113: entity was defined here
    …ction=addurl&bm_url=http://lustich.de/&bm_description=Das+Fun-Portal+gegen+Lan…
  • Warning Line 1722, Column 203: cannot generate system identifier for general entity "bm_notice"
    …stig%2C+lachen%2C+witzig+-+lustich.de&bm_notice=Das+gr%C3%B6%C3%9Fte+deutsche+…

    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 1722, Column 203: general entity "bm_notice" not defined and no default entity
    …stig%2C+lachen%2C+witzig+-+lustich.de&bm_notice=Das+gr%C3%B6%C3%9Fte+deutsche+…

    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 1722, Column 212: reference not terminated by REFC delimiter
    …achen%2C+witzig+-+lustich.de&bm_notice=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1722, Column 212: reference to external entity in attribute value
    …achen%2C+witzig+-+lustich.de&bm_notice=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1722, Column 212: reference to entity "bm_notice" for which no system identifier could be generated
    …achen%2C+witzig+-+lustich.de&bm_notice=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1722, Column 202: entity was defined here
    …ustig%2C+lachen%2C+witzig+-+lustich.de&bm_notice=Das+gr%C3%B6%C3%9Fte+deutsche…
  • Warning Line 1723, Column 69: cannot generate system identifier for general entity "url"
    … href="http://digg.com/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Por…

    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 1723, Column 69: general entity "url" not defined and no default entity
    … href="http://digg.com/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Por…

    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 1723, Column 72: reference not terminated by REFC delimiter
    …ef="http://digg.com/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal…

    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 1723, Column 72: reference to external entity in attribute value
    …ef="http://digg.com/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal…

    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 1723, Column 72: reference to entity "url" for which no system identifier could be generated
    …ef="http://digg.com/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal…

    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 1723, Column 68: entity was defined here
    …" href="http://digg.com/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Po…
  • Warning Line 1723, Column 92: cannot generate system identifier for general entity "title"
    …submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+…

    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 1723, Column 92: general entity "title" not defined and no default entity
    …submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+…

    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 1723, Column 97: reference not terminated by REFC delimiter
    …t?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1723, Column 97: reference to external entity in attribute value
    …t?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1723, Column 97: reference to entity "title" for which no system identifier could be generated
    …t?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1723, Column 91: entity was defined here
    …/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-…
  • Warning Line 1723, Column 172: cannot generate system identifier for general entity "topic"
    …stig%2C+lachen%2C+witzig+-+lustich.de&topic=videos_comedy" title="Diese Seite …

    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 1723, Column 172: general entity "topic" not defined and no default entity
    …stig%2C+lachen%2C+witzig+-+lustich.de&topic=videos_comedy" title="Diese Seite …

    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 1723, Column 177: reference not terminated by REFC delimiter
    …2C+lachen%2C+witzig+-+lustich.de&topic=videos_comedy" title="Diese Seite zu Di…

    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 1723, Column 177: reference to external entity in attribute value
    …2C+lachen%2C+witzig+-+lustich.de&topic=videos_comedy" title="Diese Seite zu Di…

    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 1723, Column 177: reference to entity "topic" for which no system identifier could be generated
    …2C+lachen%2C+witzig+-+lustich.de&topic=videos_comedy" title="Diese Seite zu Di…

    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 1723, Column 171: entity was defined here
    …ustig%2C+lachen%2C+witzig+-+lustich.de&topic=videos_comedy" title="Diese Seite…
  • Warning Line 1724, Column 90: reference not terminated by REFC delimiter
    …o.us/post?url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1724, Column 90: reference to external entity in attribute value
    …o.us/post?url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1724, Column 90: reference to entity "title" for which no system identifier could be generated
    …o.us/post?url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1723, Column 91: entity was defined here
    …/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-…
  • Warning Line 1724, Column 165: cannot generate system identifier for general entity "notes"
    …stig%2C+lachen%2C+witzig+-+lustich.de&notes=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%…

    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 1724, Column 165: general entity "notes" not defined and no default entity
    …stig%2C+lachen%2C+witzig+-+lustich.de&notes=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%…

    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 1724, Column 170: reference not terminated by REFC delimiter
    …2C+lachen%2C+witzig+-+lustich.de&notes=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1724, Column 170: reference to external entity in attribute value
    …2C+lachen%2C+witzig+-+lustich.de&notes=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1724, Column 170: reference to entity "notes" for which no system identifier could be generated
    …2C+lachen%2C+witzig+-+lustich.de&notes=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1724, Column 164: entity was defined here
    …ustig%2C+lachen%2C+witzig+-+lustich.de&notes=Das+gr%C3%B6%C3%9Fte+deutsche+Spa…
  • Warning Line 1725, Column 91: reference not terminated by REFC delimiter
    …om/submit?url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1725, Column 91: reference to external entity in attribute value
    …om/submit?url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1725, Column 91: reference to entity "title" for which no system identifier could be generated
    …om/submit?url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1723, Column 91: entity was defined here
    …/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-…
  • Warning Line 1726, Column 143: reference not terminated by REFC delimiter
    …tig%2C+lachen%2C+witzig+-+lustich.de&u=http://lustich.de/" title="Diese Seite …

    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 1726, Column 143: reference to external entity in attribute value
    …tig%2C+lachen%2C+witzig+-+lustich.de&u=http://lustich.de/" title="Diese Seite …

    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 1726, Column 143: reference to entity "u" for which no system identifier could be generated
    …tig%2C+lachen%2C+witzig+-+lustich.de&u=http://lustich.de/" title="Diese Seite …

    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 1721, Column 86: entity was defined here
    ….myspace.com/Modules/PostTo/Pages/?l=2&u=http://lustich.de/&t=Das+Fun-Portal+g…
  • Warning Line 1727, Column 117: reference not terminated by REFC delimiter
    …kmark.jsf?URL=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1727, Column 117: reference to external entity in attribute value
    …kmark.jsf?URL=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1727, Column 117: reference to entity "title" for which no system identifier could be generated
    …kmark.jsf?URL=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1723, Column 91: entity was defined here
    …/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-…
  • Warning Line 1728, Column 156: reference not terminated by REFC delimiter
    …g%2C+lachen%2C+witzig+-+lustich.de&url=http://lustich.de/" title="Über diese S…

    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 1728, Column 156: reference to external entity in attribute value
    …g%2C+lachen%2C+witzig+-+lustich.de&url=http://lustich.de/" title="Über diese S…

    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 1728, Column 156: reference to entity "url" for which no system identifier could be generated
    …g%2C+lachen%2C+witzig+-+lustich.de&url=http://lustich.de/" title="Über diese S…

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

  • Info Line 1723, Column 68: entity was defined here
    …" href="http://digg.com/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Po…
  • Error Line 1728, Column 299: end tag for "img" omitted, but OMITTAG NO was specified
    …lank"><img alt="Über diese Seite twittern" src="/img/icons/bm_twitter.jpg"></a>

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

  • Info Line 1728, Column 227: start tag was here
    …diese Seite twittern" target="_blank"><img alt="Über diese Seite twittern" src…
  • Warning Line 1730, Column 108: reference not terminated by REFC delimiter
    …t?url=http%3A%2F%2Flustich.de%2F&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1730, Column 108: reference to external entity in attribute value
    …t?url=http%3A%2F%2Flustich.de%2F&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1730, Column 108: reference to entity "title" for which no system identifier could be generated
    …t?url=http%3A%2F%2Flustich.de%2F&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1723, Column 91: entity was defined here
    …/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-…
  • Warning Line 1731, Column 99: reference not terminated by REFC delimiter
    …instellen?url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1731, Column 99: reference to external entity in attribute value
    …instellen?url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1731, Column 99: reference to entity "title" for which no system identifier could be generated
    …instellen?url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1723, Column 91: entity was defined here
    …/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-…
  • Warning Line 1732, Column 82: cannot generate system identifier for general entity "hl"
    …/www.google.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+…

    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 1732, Column 82: general entity "hl" not defined and no default entity
    …/www.google.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+…

    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 1732, Column 84: reference not terminated by REFC delimiter
    …ww.google.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+Fu…

    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 1732, Column 84: reference to external entity in attribute value
    …ww.google.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+Fu…

    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 1732, Column 84: reference to entity "hl" for which no system identifier could be generated
    …ww.google.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+Fu…

    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 1732, Column 81: entity was defined here
    …//www.google.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das…
  • Warning Line 1732, Column 88: cannot generate system identifier for general entity "bkmk"
    …oogle.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+Fun-Po…

    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 1732, Column 88: general entity "bkmk" not defined and no default entity
    …oogle.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+Fun-Po…

    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 1732, Column 92: reference not terminated by REFC delimiter
    …e.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+Fun-Portal…

    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 1732, Column 92: reference to external entity in attribute value
    …e.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+Fun-Portal…

    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 1732, Column 92: reference to entity "bkmk" for which no system identifier could be generated
    …e.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+Fun-Portal…

    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 1732, Column 87: entity was defined here
    …google.com/bookmarks/mark?op=add&hl=de&bkmk=http://lustich.de/&title=Das+Fun-P…
  • Warning Line 1732, Column 117: reference not terminated by REFC delimiter
    …dd&hl=de&bkmk=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1732, Column 117: reference to external entity in attribute value
    …dd&hl=de&bkmk=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1732, Column 117: reference to entity "title" for which no system identifier could be generated
    …dd&hl=de&bkmk=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-+lusti…

    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 1723, Column 91: entity was defined here
    …/submit?phase=2&url=http://lustich.de/&title=Das+Fun-Portal+gegen+Langeweile+-…
  • Warning Line 1732, Column 192: cannot generate system identifier for general entity "annotation"
    …stig%2C+lachen%2C+witzig+-+lustich.de&annotation=Das+gr%C3%B6%C3%9Fte+deutsche…

    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 1732, Column 192: general entity "annotation" not defined and no default entity
    …stig%2C+lachen%2C+witzig+-+lustich.de&annotation=Das+gr%C3%B6%C3%9Fte+deutsche…

    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 1732, Column 202: reference not terminated by REFC delimiter
    …chen%2C+witzig+-+lustich.de&annotation=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1732, Column 202: reference to external entity in attribute value
    …chen%2C+witzig+-+lustich.de&annotation=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1732, Column 202: reference to entity "annotation" for which no system identifier could be generated
    …chen%2C+witzig+-+lustich.de&annotation=Das+gr%C3%B6%C3%9Fte+deutsche+Spa%C3%9F…

    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 1732, Column 191: entity was defined here
    …ustig%2C+lachen%2C+witzig+-+lustich.de&annotation=Das+gr%C3%B6%C3%9Fte+deutsch…
  • Warning Line 1761, Column 103: character "&" is the first character of a delimiter but occurred as data
    …ei lustich.de, der größten deutschen Spaß- & Humor-Seite. Garantiert kostenlos!

    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 1785, Column 60: document type does not allow element "link" here
    <link rel="stylesheet" type="text/css" href="/js/rtl.css" />

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

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

Visitor Analysis

Daily Visitor
  • 2.567 visits