Новинарският портал на Велико Търново, Габрово, Ловеч, Плевен и Русе. Новини, репортажи, коментари, снимки, каталози и друга полезна информация за Централна Северна България. ...

sever.bg
  • Domain Name
    sever.bg
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #893913
  • Page Size
    85.5 KB
  • Ip Address
    78.128.1.40
  • Heading
    H1: 1, H2: 18, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 39 JPG, 18 PNG

Website Meta Analysis

  • Title
    Начало - sever.bg
  • Meta Keyword
    Новини, Велико Търново, Габрово, Ловеч, Плевен, Русе, справочник, снимки, информация, събития
  • Meta Description
    Новинарският портал на Велико Търново, Габрово, Ловеч, Плевен и Русе. Новини, репортажи, коментари, снимки, каталози и друга полезна информация за Централна Северна България.

Technical Analysis

  • Webserver
    nginx/1.1.19
  • Ip Address
    78.128.1.40
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from sever.bg.

HTML Analysis

  • server: nginx/1.1.19
  • date: Tue, 20 Aug 2013 14:21:33 GMT
  • content-type: text/html; charset=UTF-8
  • content-length: 19767
  • connection: close
  • x-powered-by: PHP/5.3.10-1ubuntu3.5
  • 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
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: sever.bg
requested on: 12/06/2007 13:33:17.441495 EEST
processed from: 12/06/2007 13:33:17.563757 EEST
activated on: 17/08/2007 10:19:26.407997 EEST
expires at: 12/06/2013 00:00:00 EEST
registration status: Registered

REGISTRANT:
SEVER.BG OOD
zhk Borovo, bl. 234, vh. B, ap. 1, pk 1
SOFIA, 1680
BULGARIA

ADMINISTRATIVE CONTACT:
Nikola Nikolov
email
SEVER.BG OOD
zhk Borovo, bl. 234, vh. B, ap. 1
SOFIA, 1680
BULGARIA
tel: +359 898 656091
fax:
NIC handle: NN18722

TECHNICAL CONTACT(S):

Ivan Slavkov
email
SEVER.BG OOD
zhk Mladost 1, bl. 22, vh. 3, ap.53
SOFIA, 1000
BULGARIA
tel: +359 895 650640
fax:
NIC handle: IS18743

NAME SERVER INFORMATION:
ns.sever.bg (213.145.97.20)
ns2.sever.bg (92.247.14.2)

DNSSEC: Inactive

DNS Analysis


DNS servers
ns.sever.bg [213.145.97.20]
ns2.sever.bg [92.247.14.2]


DNS Records

Answer records
sever.bg SOA
server: sever.bg
email: root@sever.bg
serial: 2012062001
refresh: 600
retry: 300
expire: 600
minimum ttl: 500
86400s
sever.bg NS  ns1.3bay.bg 86400s
sever.bg NS  ns2.3bay.bg 86400s
sever.bg A 78.128.1.40 86400s
sever.bg MX
preference: 1
exchange: aspmx.l.google.com
86400s
sever.bg MX
preference: 5
exchange: alt1.aspmx.l.google.com
86400s
sever.bg MX
preference: 5
exchange: alt2.aspmx.l.google.com
86400s
sever.bg MX
preference: 10
exchange: aspmx2.googlemail.com
86400s
sever.bg MX
preference: 10
exchange: aspmx3.googlemail.com
86400s
sever.bg MX
preference: 10
exchange: aspmx4.googlemail.com
86400s
sever.bg MX
preference: 10
exchange: aspmx5.googlemail.com
86400s

Authority records

Additional records
ns1.3bay.bg A 78.128.1.34 8640029s
ns2.3bay.bg A 92.247.14.2 8640029s

IP 78.128.1.40 Analysis

  • Country Code
    BG
  • Country Code3
    BGR
  • Country Name
    Bulgaria
  • City
    Sofia
  • Continent Code
    EU
  • Latitude
    42.6833
  • Longitude
    23.3167
  • No whois ip data for 78.128.1.40

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 88 Errors
  • 25 Warnings
Ratio Text/Html
  • 0.5714807793335008
Message Error
  • Error Line 18, Column 85: there is no attribute "class"
    …xt/javascript" src="/_javascript/webkbd.Bulgarian.js" class="skipped"></script>

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

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

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

  • Warning Line 20, Column 22: character "&" is the first character of a delimiter but occurred as data
                // tools & ui incompatibility

    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 64, Column 44: there is no attribute "target"
    …    <a href="http://inews.bg/" target="_blank" class="" title="Вътрешни, между…

    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 64, Column 114: there is no attribute "alt"
    …и, международни и спортни новини" alt="Вътрешни, международни и спортни новини…

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

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

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

  • Warning Line 103, Column 85: cannot generate system identifier for general entity "languagePreference"
    …b\\Open\\Services\\LoginDialogService&languagePreference=bg&tokenUrl='+encodeU…

    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 103, Column 85: general entity "languagePreference" not defined and no default entity
    …b\\Open\\Services\\LoginDialogService&languagePreference=bg&tokenUrl='+encodeU…

    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 103, Column 103: reference not terminated by REFC delimiter
    …\LoginDialogService&languagePreference=bg&tokenUrl='+encodeURIComponent('http:…

    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 103, Column 103: reference to entity "languagePreference" for which no system identifier could be generated
    …\LoginDialogService&languagePreference=bg&tokenUrl='+encodeURIComponent('http:…

    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 103, Column 84: entity was defined here
    …ib\\Open\\Services\\LoginDialogService&languagePreference=bg&tokenUrl='+encode…
  • Warning Line 103, Column 107: cannot generate system identifier for general entity "tokenUrl"
    …inDialogService&languagePreference=bg&tokenUrl='+encodeURIComponent('http://'+…

    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 103, Column 107: general entity "tokenUrl" not defined and no default entity
    …inDialogService&languagePreference=bg&tokenUrl='+encodeURIComponent('http://'+…

    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 103, Column 115: reference not terminated by REFC delimiter
    …Service&languagePreference=bg&tokenUrl='+encodeURIComponent('http://'+location…

    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 103, Column 115: reference to entity "tokenUrl" for which no system identifier could be generated
    …Service&languagePreference=bg&tokenUrl='+encodeURIComponent('http://'+location…

    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 103, Column 106: entity was defined here
    …ginDialogService&languagePreference=bg&tokenUrl='+encodeURIComponent('http://'…
  • Warning Line 103, Column 214: cannot generate system identifier for general entity "returnTo"
    …en\\Services\\LoginDialogResponse')+'&returnTo='+encodeURIComponent(document.U…

    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 103, Column 214: general entity "returnTo" not defined and no default entity
    …en\\Services\\LoginDialogResponse')+'&returnTo='+encodeURIComponent(document.U…

    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 103, Column 222: reference not terminated by REFC delimiter
    …\Services\\LoginDialogResponse')+'&returnTo='+encodeURIComponent(document.URL);

    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 103, Column 222: reference to entity "returnTo" for which no system identifier could be generated
    …\Services\\LoginDialogResponse')+'&returnTo='+encodeURIComponent(document.URL);

    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 103, Column 213: entity was defined here
    …pen\\Services\\LoginDialogResponse')+'&returnTo='+encodeURIComponent(document.…
  • Warning Line 118, Column 131: reference not terminated by REFC delimiter
    …\LoginDialogService&languagePreference=bg&tokenUrl=http%3A%2F%2F'+location.hos…

    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 118, Column 131: reference to entity "languagePreference" for which no system identifier could be generated
    …\LoginDialogService&languagePreference=bg&tokenUrl=http%3A%2F%2F'+location.hos…

    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 103, Column 84: entity was defined here
    …ib\\Open\\Services\\LoginDialogService&languagePreference=bg&tokenUrl='+encode…
  • Warning Line 118, Column 143: reference not terminated by REFC delimiter
    …Service&languagePreference=bg&tokenUrl=http%3A%2F%2F'+location.host.+'/?load=L…

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

  • Error Line 118, Column 143: reference to entity "tokenUrl" for which no system identifier could be generated
    …Service&languagePreference=bg&tokenUrl=http%3A%2F%2F'+location.host.+'/?load=L…

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

  • Info Line 103, Column 106: entity was defined here
    …ginDialogService&languagePreference=bg&tokenUrl='+encodeURIComponent('http://'…
  • Warning Line 126, Column 40: cannot generate system identifier for general entity "action"
    			//$.getJSON('/?load=Services\\Users&action=signout');

    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 126, Column 40: general entity "action" not defined and no default entity
    			//$.getJSON('/?load=Services\\Users&action=signout');

    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 126, Column 46: reference not terminated by REFC delimiter
    			//$.getJSON('/?load=Services\\Users&action=signout');

    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 126, Column 46: reference to entity "action" for which no system identifier could be generated
    			//$.getJSON('/?load=Services\\Users&action=signout');

    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 126, Column 39: entity was defined here
    			//$.getJSON('/?load=Services\\Users&action=signout');
  • Warning Line 129, Column 40: reference not terminated by REFC delimiter
    				url :'/?load=Services\\Users&action=signout',

    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 129, Column 40: reference to entity "action" for which no system identifier could be generated
    				url :'/?load=Services\\Users&action=signout',

    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 126, Column 39: entity was defined here
    			//$.getJSON('/?load=Services\\Users&action=signout');
  • Error Line 141, Column 41: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id="overlay" class="overlay hidden">

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

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

  • Error Line 143, Column 19: there is no attribute "tabIndex"
    	<iframe tabIndex="-1" src="javascript:false;" class="bgiframe" frameBorder="0"…

    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 143, Column 28: there is no attribute "src"
    	<iframe tabIndex="-1" src="javascript:false;" class="bgiframe" frameBorder="0"…

    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 143, Column 54: there is no attribute "class"
    …abIndex="-1" src="javascript:false;" class="bgiframe" frameBorder="0"></iframe>

    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 143, Column 77: there is no attribute "frameBorder"
    …abIndex="-1" src="javascript:false;" class="bgiframe" frameBorder="0"></iframe>

    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 143, Column 80: element "iframe" undefined
    …abIndex="-1" src="javascript:false;" class="bgiframe" frameBorder="0"></iframe>

    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 148, Column 17: there is no attribute "name"
    			<iframe name="loginDialogFrame" scrolling="no" frameBorder="no" marginheight…

    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 148, Column 46: there is no attribute "scrolling"
    …ame name="loginDialogFrame" scrolling="no" frameBorder="no" marginheight="0px"…

    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 148, Column 81: there is no attribute "marginheight"
    …ng="no" frameBorder="no" marginheight="0px" marginwidth="0px" id="loginDialogI…

    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 148, Column 99: there is no attribute "marginwidth"
    …r="no" marginheight="0px" marginwidth="0px" id="loginDialogIframe" allowtransp…

    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 148, Column 108: there is no attribute "id"
    …rginheight="0px" marginwidth="0px" id="loginDialogIframe" allowtransparency="t…

    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 148, Column 146: there is no attribute "allowtransparency"
    …"loginDialogIframe" allowtransparency="true" style="width:735px; height:260px;…

    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 148, Column 159: there is no attribute "style"
    …loginDialogIframe" allowtransparency="true" style="width:735px; height:260px;">

    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 148, Column 187: element "iframe" undefined
    …loginDialogIframe" allowtransparency="true" style="width:735px; height:260px;">

    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 176, Column 25: character "&" is the first character of a delimiter but occurred as data
                    if(data && data.status){

    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 176, Column 26: character "&" is the first character of a delimiter but occurred as data
                    if(data && data.status){

    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 209, Column 75: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                            <input type="hidden" name="load" value="Results" />

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

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

  • Error Line 210, Column 82: there is no attribute "rel"
    … <input name="search" class="searchInput" type="text" rel="Търси в север.бг" />

    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 210, Column 102: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    … <input name="search" class="searchInput" type="text" rel="Търси в север.бг" />

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

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

  • Error Line 211, Column 77: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                            <input value="" class="searchButton" type="submit" />

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

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

  • Warning Line 597, Column 5: S separator in comment declaration
    <!--

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 598, Column 1: invalid comment declaration: found character "$" outside comment but inside comment declaration
    $(function(){

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 595, Column 1: comment declaration started here
    <!--
  • Warning Line 608, Column 40: character "&" is the first character of a delimiter but occurred as data
          $('#regionsList').is(':visible') &&

    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 608, Column 41: character "&" is the first character of a delimiter but occurred as data
          $('#regionsList').is(':visible') &&

    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 609, Column 52: character "&" is the first character of a delimiter but occurred as data
             $(evt.target).attr('id') != 'regionsList' &&

    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 609, Column 53: character "&" is the first character of a delimiter but occurred as data
             $(evt.target).attr('id') != 'regionsList' &&

    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 610, Column 52: character "&" is the first character of a delimiter but occurred as data
             $(evt.target).attr('id') != 'regionsLink' &&

    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 610, Column 53: character "&" is the first character of a delimiter but occurred as data
             $(evt.target).attr('id') != 'regionsLink' &&

    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 625, Column 52: reference not terminated by REFC delimiter
    …/?load=\\Open\\Services\\Region&action=setRegion&newRegionId='+ regionId, func…

    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 625, Column 52: reference to entity "action" for which no system identifier could be generated
    …/?load=\\Open\\Services\\Region&action=setRegion&newRegionId='+ regionId, func…

    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 126, Column 39: entity was defined here
    			//$.getJSON('/?load=Services\\Users&action=signout');
  • Warning Line 625, Column 63: cannot generate system identifier for general entity "newRegionId"
    …pen\\Services\\Region&action=setRegion&newRegionId='+ regionId, function(data){

    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 625, Column 63: general entity "newRegionId" not defined and no default entity
    …pen\\Services\\Region&action=setRegion&newRegionId='+ regionId, function(data){

    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 625, Column 74: reference not terminated by REFC delimiter
    …pen\\Services\\Region&action=setRegion&newRegionId='+ regionId, function(data){

    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 625, Column 74: reference to entity "newRegionId" for which no system identifier could be generated
    …pen\\Services\\Region&action=setRegion&newRegionId='+ regionId, function(data){

    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 625, Column 62: entity was defined here
    …pen\\Services\\Region&action=setRegion&newRegionId='+ regionId, function(data)…
  • Error Line 658, Column 15: syntax of attribute value does not conform to declared value
    					<img id="" width="392" height="219" src="http://sever.bg/pictures/829668_3…

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

  • Error Line 658, Column 102: there is no attribute "realwidth"
    …ight="219" src="http://sever.bg/pictures/829668_392_219.jpg" realwidth="800" />

    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 658, Column 109: required attribute "alt" not specified
    …ight="219" src="http://sever.bg/pictures/829668_392_219.jpg" realwidth="800" />

    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 666, Column 15: syntax of attribute value does not conform to declared value
    					<img id="" width="392" height="219" src="http://sever.bg/pictures/829596_3…

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

  • Error Line 666, Column 110: required attribute "alt" not specified
    …ght="219" src="http://sever.bg/pictures/829596_392_219.jpg" realwidth="1800" />

    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 674, Column 15: syntax of attribute value does not conform to declared value
    					<img id="" width="392" height="219" src="http://sever.bg/pictures/829555_3…

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

  • Error Line 674, Column 110: required attribute "alt" not specified
    …ght="219" src="http://sever.bg/pictures/829555_392_219.jpg" realwidth="4000" />

    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 736, Column 210: required attribute "alt" not specified
    …ght="119" src="http://sever.bg/pictures/829700_212_119.jpg" realwidth="4320" />

    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 762, Column 219: required attribute "alt" not specified
    …ight="119" src="http://sever.bg/pictures/829676_212_119.jpg" realwidth="760" />

    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 203: required attribute "alt" not specified
    …ight="119" src="http://sever.bg/pictures/829663_212_119.jpg" realwidth="375" />

    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 883, Column 134: syntax of attribute value does not conform to declared value
    …ierd.html"><img class="thumbnail" id="" width="161" height="224" src="http://s…

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

  • Error Line 883, Column 229: required attribute "alt" not specified
    …ght="224" src="http://sever.bg/pictures/824962_161_224.jpg" realwidth="3216" />

    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 921, Column 122: syntax of attribute value does not conform to declared value
    …-изложба_l.sd_i.265783.html"><img id="" width="204" height="158" src="http://s…

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

  • Error Line 921, Column 219: required attribute "alt" not specified
    …t="158" src="http://sever.bg/pictures/251918_204_158_2.jpg" realwidth="3000" />

    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 952, Column 111: syntax of attribute value does not conform to declared value
    …-канавка_l.sd_i.267199.html"><img id="" width="204" height="158" src="http://s…

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

  • Error Line 952, Column 205: required attribute "alt" not specified
    …ight="158" src="http://sever.bg/pictures/828996_204_158.jpg" realwidth="483" />

    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 1126, Column 244: required attribute "alt" not specified
    …ght="108" src="http://sever.bg/pictures/829555_194_108.jpg" realwidth="4000" />

    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 1135, Column 246: required attribute "alt" not specified
    …ight="108" src="http://sever.bg/pictures/828385_194_108.jpg" realwidth="643" />

    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 1143, Column 265: required attribute "alt" not specified
    …ght="108" src="http://sever.bg/pictures/827651_194_108.jpg" realwidth="4000" />

    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 34: syntax of attribute value does not conform to declared value
    						<img class="thumbnail" id="" width="220" height="167" title="Водолазен це…

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

  • Error Line 1210, Column 36: syntax of attribute value does not conform to declared value
    								<img class="thumbnail" id="" width="137" height="107" title="Рибарници …

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

  • Error Line 1222, Column 36: syntax of attribute value does not conform to declared value
    								<img class="thumbnail" id="" width="137" height="107" title="Футболно и…

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

  • Error Line 1338, Column 39: ID "freeTimeHighlight" already defined
                    <div class="left" id="freeTimeHighlight">

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

  • Info Line 1270, Column 39: ID "freeTimeHighlight" first defined here
                    <div class="left" id="freeTimeHighlight">
  • Error Line 1402, Column 31: invalid comment declaration: found character ";" outside comment but inside comment declaration
                    currentIndex--;

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1392, Column 5: comment declaration started here
        <!--
  • Warning Line 1406, Column 30: character "<" is the first character of a delimiter but occurred as data
                if (currentIndex < 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.
  • Error Line 1441, Column 174: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19070_381_215_1.jpg" realwidth="632" />

    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 1445, Column 174: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19069_381_215_1.jpg" realwidth="627" />

    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 1449, Column 174: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19068_381_215_1.jpg" realwidth="631" />

    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 1453, Column 174: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19067_381_215_1.jpg" realwidth="632" />

    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 1457, Column 174: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19066_381_215_1.jpg" realwidth="630" />

    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 1463, Column 61: there is no attribute "rel"
                                    <span class="navigator" rel="32430">

    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 1482, Column 190: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19282_381_215_1.jpg" realwidth="470" />

    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 1499, Column 178: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19071_381_215_1.jpg" realwidth="400" />

    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 1516, Column 174: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19418_381_215_1.jpg" realwidth="780" />

    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 1520, Column 174: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19417_381_215_1.jpg" realwidth="780" />

    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 1524, Column 174: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19416_381_215_1.jpg" realwidth="777" />

    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 1528, Column 174: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19415_381_215_1.jpg" realwidth="768" />

    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 1532, Column 174: required attribute "alt" not specified
    …ght="215" src="http://sever.bg/pictures/19414_381_215_1.jpg" realwidth="775" />

    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 1684, Column 242: required attribute "alt" not specified
    …ght="105" src="http://sever.bg/pictures/828442_134_105.jpg" realwidth="4608" />

    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 1709, Column 136: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …www/delivery/ck.php?n=a8996cb7&amp;cb=5136d69fd169c7.93902318" target="_blank">

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

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

  • Error Line 1710, Column 175: there is no attribute "border"
    …8&amp;n=a8996cb7&amp;ct0={clickurl}&amp;wmode=transperant" border="0" alt="" />

    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 1892, Column 134: required attribute "alt" not specified
    …12_r.1545.html"><img class="selected" src="/img/public/horoscope/12.png" /></a>

    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 1949, Column 15: syntax of attribute value does not conform to declared value
    					<img id="" width="284" src="http://sever.bg/pictures/20935_284__1.jpg" rea…

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

  • Error Line 1949, Column 94: required attribute "alt" not specified
    … width="284" src="http://sever.bg/pictures/20935_284__1.jpg" realwidth="500" />

    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 2000, Column 73: required attribute "alt" not specified
    …="item"><img src="/img/public/flags/usd.png" /> <!--1--> USD 1.50056 BGN </div>

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

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

  • Error Line 2002, Column 73: required attribute "alt" not specified
    …="item"><img src="/img/public/flags/gbp.png" /> <!--1--> GBP 2.27475 BGN </div>

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

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

  • Error Line 2021, Column 255: there is no attribute "frameborder"
    …ale=bg_BG" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 2021, Column 342: there is no attribute "allowTransparency"
    …overflow:hidden; width:292px; height:262px;" allowTransparency="true"></iframe>

    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 2021, Column 348: element "iframe" undefined
    …overflow:hidden; width:292px; height:262px;" allowTransparency="true"></iframe>

    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 2062, Column 127: required attribute "alt" not specified
    …://bta.bg" rel="nofollow" target="_blank"><img src="/img/public/bta.png" /></a>

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

Visitor Analysis

Daily Visitor
  • 150 visits