MMORPG Metin2 ...

metin2.de
  • Domain Name
    metin2.de
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #67073
  • Page Size
    90 B
  • Ip Address
    79.110.92.75
  • Heading
    H1: 0, H2: 5, H3: 11, H4: 6, H5: 3, H6: 0
  • Images
    1 GIF, 6 JPG, 5 PNG

Website Meta Analysis

  • Title
    Metin2 - Oriental Action MMORPG
  • Meta Keyword
  • Meta Description
    MMORPG Metin2

Technical Analysis

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

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

HTML Analysis

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

Domain: metin2.de
Nserver: ns1.gfsrv.net
Nserver: ns2.gfsrv.net
Nserver: ns3.gfsrv.net
Status: connect
Changed: 2011-02-18T16:29:33+01:00

[Tech-C]
Type: PERSON
Name: Alexander Roesner
Organisation: Gameforge Productions GmbH
Address: Albert-Nestler-Str. 8
PostalCode: 76131
City: Karlsruhe
CountryCode: DE
Phone: +49.7213548080
Fax: +49.721354808152
Email: email
Remarks: Gameforge Productions GmbH, technical office - no game support
Changed: 2010-02-02T12:08:31+01:00

[Zone-C]
Type: PERSON
Name: Alexander Roesner
Organisation: Gameforge Productions GmbH
Address: Albert-Nestler-Str. 8
PostalCode: 76131
City: Karlsruhe
CountryCode: DE
Phone: +49.7213548080
Fax: +49.721354808152
Email: email
Remarks: Gameforge Productions GmbH, technical office - no game support
Changed: 2010-02-02T12:08:31+01:00

IP 79.110.92.75 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 52 Errors
  • 53 Warnings
Ratio Text/Html
  • 0.8888888888888888
Message Error
  • Error Line 85, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Warning Line 94, Column 314: character "<" is the first character of a delimiter but occurred as data
    …r minus=((mmoActive_select.activeid-1)<=0)?'0':(mmoActive_select.activeid-1);m…

    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 94, Column 695: character ";" not allowed in attribute specification list
    …nd=false;for(var i=0;i<mmoitems.length;i++){var _a=mmoitems[i].getElementsByTa…
  • Error Line 94, Column 695: element "mmoitems.length" undefined
    …nd=false;for(var i=0;i<mmoitems.length;i++){var _a=mmoitems[i].getElementsByTa…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 96, Column 10: character "&" is the first character of a delimiter but occurred as data
    if(!found&&(thecode.toLowerCase()==txtContent.charAt(0).toLowerCase())){mmoActi…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 96, Column 11: character "&" is the first character of a delimiter but occurred as data
    if(!found&&(thecode.toLowerCase()==txtContent.charAt(0).toLowerCase())){mmoActi…

    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 99, Column 30: character ";" not allowed in attribute specification list
    for(var i=0;i<mmoitems.length;i++){if(mmoitems[i].className=='mmoActive'){mmoAc…
  • Error Line 99, Column 30: element "mmoitems.length" undefined
    for(var i=0;i<mmoitems.length;i++){if(mmoitems[i].className=='mmoActive'){mmoAc…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 101, Column 102: character "&" is the first character of a delimiter but occurred as data
    …moOptionsDiv"+g);if((mmoActive_select)&&(mmoActive_select!=_elem)){mmoActive_s…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 101, Column 103: character "&" is the first character of a delimiter but occurred as data
    …oOptionsDiv"+g);if((mmoActive_select)&&(mmoActive_select!=_elem)){mmoActive_se…

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 105, Column 100: character "&" is the first character of a delimiter but occurred as data
    …arent=_parent.parentNode;while(_parent&&(_parent.className!=null)&&(_parent.cl…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 105, Column 101: character "&" is the first character of a delimiter but occurred as data
    …rent=_parent.parentNode;while(_parent&&(_parent.className!=null)&&(_parent.cla…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 105, Column 127: character "&" is the first character of a delimiter but occurred as data
    …ile(_parent&&(_parent.className!=null)&&(_parent.className.indexOf(_class)==-1…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 105, Column 128: character "&" is the first character of a delimiter but occurred as data
    …le(_parent&&(_parent.className!=null)&&(_parent.className.indexOf(_class)==-1)…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 106, Column 25: character "&" is the first character of a delimiter but occurred as data
    return(_parent.className&&(_parent.className.indexOf(_class)!=-1))?1:0;}

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 106, Column 26: character "&" is the first character of a delimiter but occurred as data
    return(_parent.className&&(_parent.className.indexOf(_class)!=-1))?1:0;}

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 107, Column 83: character "&" is the first character of a delimiter but occurred as data
    … ie6browser=((ua.indexOf("msie 6")>-1)&&(ua.indexOf("opera")<0))?true:false;fu…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 107, Column 84: character "&" is the first character of a delimiter but occurred as data
    …ie6browser=((ua.indexOf("msie 6")>-1)&&(ua.indexOf("opera")<0))?true:false;fun…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 107, Column 105: character "<" is the first character of a delimiter but occurred as data
    …Of("msie 6")>-1)&&(ua.indexOf("opera")<0))?true:false;function highlight(el,mo…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 107, Column 172: character "&" is the first character of a delimiter but occurred as data
    …light(el,mod){if(ie6browser){if(mod==1&&!el.className.match(/highlight/))el.cl…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 107, Column 173: character "&" is the first character of a delimiter but occurred as data
    …ight(el,mod){if(ie6browser){if(mod==1&&!el.className.match(/highlight/))el.cla…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 110, Column 202: character "&" is the first character of a delimiter but occurred as data
    …dOf:function(child,parent){while(child&&child!=parent){child=child.parentNode;…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 110, Column 204: cannot generate system identifier for general entity "child"
    …dOf:function(child,parent){while(child&&child!=parent){child=child.parentNode;}

    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 110, Column 204: general entity "child" not defined and no default entity
    …dOf:function(child,parent){while(child&&child!=parent){child=child.parentNode;}

    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 110, Column 209: reference not terminated by REFC delimiter
    …dOf:function(child,parent){while(child&&child!=parent){child=child.parentNode;}

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

  • Error Line 110, Column 209: reference to entity "child" for which no system identifier could be generated
    …dOf:function(child,parent){while(child&&child!=parent){child=child.parentNode;}

    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 110, Column 203: entity was defined here
    …dOf:function(child,parent){while(child&&child!=parent){child=child.parentNode;}
  • Warning Line 111, Column 463: character "&" is the first character of a delimiter but occurred as data
    …dOf((e.target||e.srcElement),wrapper))&&panel.style.display!="none"){mmoToggle…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 111, Column 465: cannot generate system identifier for general entity "panel.style.display"
    …f((e.target||e.srcElement),wrapper))&&panel.style.display!="none"){mmoToggleDi…

    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 111, Column 465: general entity "panel.style.display" not defined and no default entity
    …f((e.target||e.srcElement),wrapper))&&panel.style.display!="none"){mmoToggleDi…

    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 111, Column 484: reference not terminated by REFC delimiter
    …lement),wrapper))&&panel.style.display!="none"){mmoToggleDisplay.toggle(link,p…

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

  • Error Line 111, Column 484: reference to entity "panel.style.display" for which no system identifier could be generated
    …lement),wrapper))&&panel.style.display!="none"){mmoToggleDisplay.toggle(link,p…

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

  • Info Line 111, Column 464: entity was defined here
    …Of((e.target||e.srcElement),wrapper))&&panel.style.display!="none"){mmoToggleD…
  • Error Line 112, Column 133: end tag for "mmoitems.length" omitted, but OMITTAG NO was specified
    …""+data[gameName];gameImg.alt="";gameSpan.appendChild(gameImg);}}}    </script>

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

  • Info Line 99, Column 14: start tag was here
    for(var i=0;i<mmoitems.length;i++){if(mmoitems[i].className=='mmoActive'){mmoAc…
  • Error Line 112, Column 133: end tag for "mmoitems.length" omitted, but OMITTAG NO was specified
    …""+data[gameName];gameImg.alt="";gameSpan.appendChild(gameImg);}}}    </script>

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

  • Info Line 94, Column 679: start tag was here
    …thecode);var found=false;for(var i=0;i<mmoitems.length;i++){var _a=mmoitems[i]…
  • Warning Line 256, Column 40: character "&" is the first character of a delimiter but occurred as data
                    var gArr=strGET.split('&');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 257, Column 38: character ";" not allowed in attribute specification list
                    for(i=0;i<gArr.length;++i){
  • Error Line 257, Column 38: element "gArr.length" undefined
                    for(i=0;i<gArr.length;++i){

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 278, Column 40: cannot generate system identifier for general entity "source"
    …           	var params = 'zoneid=1568&source=Quelle&cb=INSERT_RANDOM_NUMBER_HE…

    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 278, Column 40: general entity "source" not defined and no default entity
    …           	var params = 'zoneid=1568&source=Quelle&cb=INSERT_RANDOM_NUMBER_HE…

    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 278, Column 46: reference not terminated by REFC delimiter
    …     	var params = 'zoneid=1568&source=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&lay…

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

  • Error Line 278, Column 46: reference to entity "source" for which no system identifier could be generated
    …     	var params = 'zoneid=1568&source=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&lay…

    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 278, Column 39: entity was defined here
                	var params = 'zoneid=1568&source=Quelle&cb=INSERT_RANDOM_NUMBER_HE…
  • Warning Line 278, Column 54: cannot generate system identifier for general entity "cb"
    …r params = 'zoneid=1568&source=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&layerstyle=…

    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 278, Column 54: general entity "cb" not defined and no default entity
    …r params = 'zoneid=1568&source=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&layerstyle=…

    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 278, Column 56: reference not terminated by REFC delimiter
    …params = 'zoneid=1568&source=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&layerstyle=si…

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

  • Error Line 278, Column 56: reference to entity "cb" for which no system identifier could be generated
    …params = 'zoneid=1568&source=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&layerstyle=si…

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

  • Info Line 278, Column 53: entity was defined here
    …ar params = 'zoneid=1568&source=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&layerstyle…
  • Warning Line 278, Column 83: cannot generate system identifier for general entity "layerstyle"
    …e=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&layerstyle=simple&align=left&valign=top&…

    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 278, Column 83: general entity "layerstyle" not defined and no default entity
    …e=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&layerstyle=simple&align=left&valign=top&…

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

  • Warning Line 278, Column 93: reference not terminated by REFC delimiter
    …b=INSERT_RANDOM_NUMBER_HERE&layerstyle=simple&align=left&valign=top&padding=2&…

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

  • Error Line 278, Column 93: reference to entity "layerstyle" for which no system identifier could be generated
    …b=INSERT_RANDOM_NUMBER_HERE&layerstyle=simple&align=left&valign=top&padding=2&…

    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 278, Column 82: entity was defined here
    …ce=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&layerstyle=simple&align=left&valign=top…
  • Warning Line 278, Column 101: cannot generate system identifier for general entity "align"
    …_RANDOM_NUMBER_HERE&layerstyle=simple&align=left&valign=top&padding=2&shifth=3…

    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 278, Column 101: general entity "align" not defined and no default entity
    …_RANDOM_NUMBER_HERE&layerstyle=simple&align=left&valign=top&padding=2&shifth=3…

    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 278, Column 106: reference not terminated by REFC delimiter
    …OM_NUMBER_HERE&layerstyle=simple&align=left&valign=top&padding=2&shifth=30&shi…

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

  • Error Line 278, Column 106: reference to entity "align" for which no system identifier could be generated
    …OM_NUMBER_HERE&layerstyle=simple&align=left&valign=top&padding=2&shifth=30&shi…

    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 278, Column 100: entity was defined here
    …T_RANDOM_NUMBER_HERE&layerstyle=simple&align=left&valign=top&padding=2&shifth=…
  • Warning Line 278, Column 112: cannot generate system identifier for general entity "valign"
    …BER_HERE&layerstyle=simple&align=left&valign=top&padding=2&shifth=30&shiftv=20…

    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 278, Column 112: general entity "valign" not defined and no default entity
    …BER_HERE&layerstyle=simple&align=left&valign=top&padding=2&shifth=30&shiftv=20…

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

  • Warning Line 278, Column 118: reference not terminated by REFC delimiter
    …RE&layerstyle=simple&align=left&valign=top&padding=2&shifth=30&shiftv=20&close…

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

  • Error Line 278, Column 118: reference to entity "valign" for which no system identifier could be generated
    …RE&layerstyle=simple&align=left&valign=top&padding=2&shifth=30&shiftv=20&close…

    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 278, Column 111: entity was defined here
    …MBER_HERE&layerstyle=simple&align=left&valign=top&padding=2&shifth=30&shiftv=2…
  • Warning Line 278, Column 123: cannot generate system identifier for general entity "padding"
    …yerstyle=simple&align=left&valign=top&padding=2&shifth=30&shiftv=20&closebutto…

    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 278, Column 123: general entity "padding" not defined and no default entity
    …yerstyle=simple&align=left&valign=top&padding=2&shifth=30&shiftv=20&closebutto…

    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 278, Column 130: reference not terminated by REFC delimiter
    …e=simple&align=left&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&bac…

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

  • Error Line 278, Column 130: reference to entity "padding" for which no system identifier could be generated
    …e=simple&align=left&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&bac…

    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 278, Column 122: entity was defined here
    …ayerstyle=simple&align=left&valign=top&padding=2&shifth=30&shiftv=20&closebutt…
  • Warning Line 278, Column 133: cannot generate system identifier for general entity "shifth"
    …imple&align=left&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backco…

    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 278, Column 133: general entity "shifth" not defined and no default entity
    …imple&align=left&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backco…

    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 278, Column 139: reference not terminated by REFC delimiter
    …align=left&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4…

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

  • Error Line 278, Column 139: reference to entity "shifth" for which no system identifier could be generated
    …align=left&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4…

    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 278, Column 132: entity was defined here
    …simple&align=left&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backc…
  • Warning Line 278, Column 143: cannot generate system identifier for general entity "shiftv"
    …n=left&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296…

    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 278, Column 143: general entity "shiftv" not defined and no default entity
    …n=left&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296…

    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 278, Column 149: reference not terminated by REFC delimiter
    …&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&borde…

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

  • Error Line 278, Column 149: reference to entity "shiftv" for which no system identifier could be generated
    …&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&borde…

    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 278, Column 142: entity was defined here
    …gn=left&valign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C29…
  • Warning Line 278, Column 153: cannot generate system identifier for general entity "closebutton"
    …ign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercol…

    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 278, Column 153: general entity "closebutton" not defined and no default entity
    …ign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercol…

    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 278, Column 164: reference not terminated by REFC delimiter
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';

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

  • Error Line 278, Column 164: reference to entity "closebutton" for which no system identifier could be generated
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';

    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 278, Column 152: entity was defined here
    …lign=top&padding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&borderco…
  • Warning Line 278, Column 167: cannot generate system identifier for general entity "backcolor"
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';

    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 278, Column 167: general entity "backcolor" not defined and no default entity
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';

    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 278, Column 176: reference not terminated by REFC delimiter
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';

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

  • Error Line 278, Column 176: reference to entity "backcolor" for which no system identifier could be generated
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';

    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 278, Column 166: entity was defined here
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';
  • Warning Line 278, Column 184: cannot generate system identifier for general entity "bordercolor"
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';

    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 278, Column 184: general entity "bordercolor" not defined and no default entity
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';

    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 278, Column 195: reference not terminated by REFC delimiter
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';

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

  • Error Line 278, Column 195: reference to entity "bordercolor" for which no system identifier could be generated
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';

    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 278, Column 183: entity was defined here
    …dding=2&shifth=30&shiftv=20&closebutton=t&backcolor=D4C296&bordercolor=B10000';
  • Warning Line 281, Column 32: cannot generate system identifier for general entity "kid"
                	params = params+'&kid='+GET('kid');

    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 281, Column 32: general entity "kid" not defined and no default entity
                	params = params+'&kid='+GET('kid');

    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 281, Column 35: reference not terminated by REFC delimiter
                	params = params+'&kid='+GET('kid');

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

  • Error Line 281, Column 35: reference to entity "kid" for which no system identifier could be generated
                	params = params+'&kid='+GET('kid');

    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 281, Column 31: entity was defined here
                	params = params+'&kid='+GET('kid');
  • Warning Line 282, Column 32: cannot generate system identifier for general entity "zindex"
                	params = params+'&zindex=9999999';

    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 282, Column 32: general entity "zindex" not defined and no default entity
                	params = params+'&zindex=9999999';

    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 282, Column 38: reference not terminated by REFC delimiter
                	params = params+'&zindex=9999999';

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

  • Error Line 282, Column 38: reference to entity "zindex" for which no system identifier could be generated
                	params = params+'&zindex=9999999';

    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 282, Column 31: entity was defined here
                	params = params+'&zindex=9999999';
  • Warning Line 283, Column 42: reference not terminated by REFC delimiter
                	params = params+'&layerstyle=gameforge'

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

  • Error Line 283, Column 42: reference to entity "layerstyle" for which no system identifier could be generated
                	params = params+'&layerstyle=gameforge'

    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 278, Column 82: entity was defined here
    …ce=Quelle&cb=INSERT_RANDOM_NUMBER_HERE&layerstyle=simple&align=left&valign=top…
  • Error Line 284, Column 34: an attribute specification must start with a name or name token
                	document.write("<scr"+"ipt type='text/javascript' src='http://deli…

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

  • Error Line 284, Column 34: element "scr" undefined
                	document.write("<scr"+"ipt type='text/javascript' src='http://deli…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 284, Column 118: character "<" is the first character of a delimiter but occurred as data
    …pt' src='http://delivery.ads.gfsrv.net/al.php?"+params+"'><\/scr"+"ipt>");     

    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 286, Column 10: end tag for "scr" omitted, but OMITTAG NO was specified
    	</script>

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

  • Info Line 284, Column 30: start tag was here
                	document.write("<scr"+"ipt type='text/javascript' src='http://deli…
  • Error Line 286, Column 10: end tag for "gArr.length" omitted, but OMITTAG NO was specified
    	</script>

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

  • Info Line 257, Column 26: start tag was here
                    for(i=0;i<gArr.length;++i){
  • Error Line 362, Column 64: there is no attribute "wmode"
                            <object width="221" height="131" wmode="opaque">

    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 366, Column 40: there is no attribute "src"
    …                           <embed src="http://gf1.geo.gfsrv.net/cdnca/370d1b91…

    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 366, Column 113: there is no attribute "type"
    …d1b91cfe3e8c658f3ade2d7e3cc.swf" type="application/x-shockwave-flash" allowful…

    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 366, Column 161: there is no attribute "allowfullscreen"
    …on/x-shockwave-flash" allowfullscreen="true" width="221" height="131" wmode="o…

    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 366, Column 174: there is no attribute "width"
    …ckwave-flash" allowfullscreen="true" width="221" height="131" wmode="opaque" />

    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 366, Column 187: there is no attribute "height"
    …ckwave-flash" allowfullscreen="true" width="221" height="131" wmode="opaque" />

    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 366, Column 199: there is no attribute "wmode"
    …ckwave-flash" allowfullscreen="true" width="221" height="131" wmode="opaque" />

    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 366, Column 209: element "embed" undefined
    …ckwave-flash" allowfullscreen="true" width="221" height="131" wmode="opaque" />

    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).

Visitor Analysis

Daily Visitor
  • 3.150 visits
Daily Visitor