Zadovoljna.hr - online magazin za žene i obitelj ...

zadovoljna.hr
  • Domain Name
    zadovoljna.hr
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #1607698
  • Page Size
    54.5 KB
  • Ip Address
    91.202.65.146
  • Heading
    H1: 12, H2: 5, H3: 1, H4: 2, H5: 0, H6: 0
  • Images
    4 GIF, 27 JPG, 0 PNG

Website Meta Analysis

  • Title
    Naslovnica - Zadovoljna.hr
  • Meta Keyword
    Ljepota, dijeta, moda, zdravlje, veze, mame, bebe, muškarci, lifestyle, forum, Nikolina, pišek, fashion, guru, horoskop, glumičić
  • Meta Description
    Zadovoljna.hr - online magazin za žene i obitelj

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from zadovoljna.hr.

HTML Analysis

  • date: Tue, 05 Mar 2013 20:37:06 GMT
  • server: Apache
  • x-ua-compatible: IE=EmulateIE7
  • hostname: (null)
  • connection: Keep-Alive
  • content-type: text/html
  • via: CN-5000
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
No data whois for zadovoljna.hr

IP 91.202.65.146 Analysis

  • Country Code
    SI
  • Country Code3
    SVN
  • Country Name
    Slovenia
  • City
    EU
  • Continent Code
    46° North
  • Latitude
    15.
  • Longitude
  • No whois ip data for 91.202.65.146

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 107 Errors
  • 78 Warnings
Ratio Text/Html
  • 0.6430476736067599
Message Error
  • Error Line 2, Column 161: "itemscope" is not a member of a group specified for any attribute
    …/opengraphprotocol.org/schema/" itemscope itemtype="http://schema.org/WebPage">
  • Error Line 2, Column 170: there is no attribute "itemtype"
    …/opengraphprotocol.org/schema/" itemscope itemtype="http://schema.org/WebPage">

    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 33, Column 17: there is no attribute "property"
    	<meta property="fb:admins" content="100000982089975" />

    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 127, Column 12: document type does not allow element "noscript" here; assuming missing "object" start-tag
    		<noscript><img src="/bin/usrtrck-new.php?c=UNKNOWN" alt="." width="1" height=…
  • Error Line 130, Column 8: end tag for "object" omitted, but OMITTAG NO was specified
    	</head>

    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 127, Column 3: start tag was here
    		<noscript><img src="/bin/usrtrck-new.php?c=UNKNOWN" alt="." width="1" height=…
  • Error Line 172, Column 97: required attribute "alt" not specified
    …href="/"><img src="/static/hr/microsites/zadovoljna//img/logo.gif" /></a></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 173, Column 37: "itemscope" is not a member of a group specified for any attribute
    		<div class="floatRight" itemscope itemtype="http://schema.org/WPAdBlock"><scr…
  • Error Line 173, Column 46: there is no attribute "itemtype"
    …class="floatRight" itemscope itemtype="http://schema.org/WPAdBlock"><script ty…

    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 206, Column 14: required attribute "type" not specified
    </div><script>

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

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

  • Warning Line 208, Column 17: character "&" is the first character of a delimiter but occurred as data
    if (document.all&&document.getElementById) {

    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 208, Column 19: cannot generate system identifier for general entity "document.getElementById"
    if (document.all&&document.getElementById) {

    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 208, Column 19: general entity "document.getElementById" not defined and no default entity
    if (document.all&&document.getElementById) {

    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 208, Column 42: reference not terminated by REFC delimiter
    if (document.all&&document.getElementById) {

    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 208, Column 42: reference to entity "document.getElementById" for which no system identifier could be generated
    if (document.all&&document.getElementById) {

    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 208, Column 18: entity was defined here
    if (document.all&&document.getElementById) {
  • Error Line 210, Column 38: character ";" not allowed in attribute specification list
    for (i=0; i<navRoot.childNodes.length; i++) {
  • Error Line 210, Column 38: element "navRoot.childNodes.length" undefined
    for (i=0; i<navRoot.childNodes.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).
  • Error Line 223, Column 9: end tag for "navRoot.childNodes.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 210, Column 12: start tag was here
    for (i=0; i<navRoot.childNodes.length; i++) {
  • Error Line 268, Column 105: "itemscope" is not a member of a group specified for any attribute
    …ull m3_bg_content wideBanner" itemscope itemtype="http://schema.org/WPAdBlock">
  • Error Line 307, Column 52: document type does not allow element "style" here
    	<div style="display: none;"><style type="text/css">

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

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

  • Error Line 327, Column 11: required attribute "type" not specified
    <p><script>

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

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

  • Error Line 336, Column 165: document type does not allow element "a" here
    …p://www.diners.com.hr" target="_blank"><img style="position: relative; float: …

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

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

  • Error Line 336, Column 292: required attribute "alt" not specified
    …ght: 6px;" src="http://image.dnevnik.hr/media/document/60461137.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 336, Column 296: end tag for "img" omitted, but OMITTAG NO was specified
    …ght: 6px;" src="http://image.dnevnik.hr/media/document/60461137.png"></a>'))});

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

  • Info Line 336, Column 166: start tag was here
    …://www.diners.com.hr" target="_blank"><img style="position: relative; float: r…
  • Error Line 339, Column 75: document type does not allow element "span" here
    …_terms_box" style="position:relative;"><div style="position:absolute;top:0px;l…

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

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

  • Error Line 339, Column 189: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … #C6559F;background:#FFF;padding:5px;">Organizator nagradnog kviza obvezuje se…

    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 359, Column 127: document type does not allow element "li" here
    …ht: 0px; padding: 11px 20px 11px 8px;"><a href="/fotogalerija/zadovoljnadaruje…

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

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

  • Error Line 359, Column 271: required attribute "alt" not specified
    …dia/document/60393957.png" style="position: absolute; top: -11px;"></a></li>');

    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 359, Column 275: end tag for "img" omitted, but OMITTAG NO was specified
    …dia/document/60393957.png" style="position: absolute; top: -11px;"></a></li>');

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

  • Info Line 359, Column 169: start tag was here
    …href="/fotogalerija/zadovoljnadaruje"><img src="http://image.dnevnik.hr/media/…
  • Error Line 364, Column 58: document type does not allow element "li" here
    …yle="position: relative; width: 50px;"><a href="http://zadovoljna.hr/zaljublje…

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

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

  • Error Line 364, Column 212: required attribute "alt" not specified
    …eft:5px" src="http://image.dnevnik.hr/media/document/60408387.png"> </a></li>';

    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 364, Column 213: end tag for "img" omitted, but OMITTAG NO was specified
    …eft:5px" src="http://image.dnevnik.hr/media/document/60408387.png"> </a></li>';

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

  • Info Line 364, Column 102: start tag was here
    …ef="http://zadovoljna.hr/zaljubljeni"><img style="position: absolute; top: -9p…
  • Error Line 415, Column 52: "itemscope" is not a member of a group specified for any attribute
    …class="d3_g_8 d3_pb_m banner" itemscope itemtype="http://schema.org/WPAdBlock">
  • Warning Line 558, Column 57: reference not terminated by REFC delimiter
    …selected'>1</span><span class=''>&nbsp</span><span class='normal'><a href='/?&…

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

  • Warning Line 558, Column 214: cannot generate system identifier for general entity "section_id"
    …1", "/lbin/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_af…

    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 558, Column 214: general entity "section_id" not defined and no default entity
    …1", "/lbin/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_af…

    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 558, Column 224: reference not terminated by REFC delimiter
    …/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_after="); th…

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

  • Warning Line 558, Column 224: reference to external entity in attribute value
    …/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_after="); th…

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

  • Error Line 558, Column 224: reference to entity "section_id" for which no system identifier could be generated
    …/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_after="); th…

    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 558, Column 213: entity was defined here
    …11", "/lbin/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_a…
  • Warning Line 558, Column 231: cannot generate system identifier for general entity "front_id"
    …edia_list.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blur…

    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 558, Column 231: general entity "front_id" not defined and no default entity
    …edia_list.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blur…

    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 558, Column 239: reference not terminated by REFC delimiter
    …t.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Warning Line 558, Column 239: reference to external entity in attribute value
    …t.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Error Line 558, Column 239: reference to entity "front_id" for which no system identifier could be generated
    …t.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

    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 558, Column 230: entity was defined here
    …media_list.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blu…
  • Warning Line 558, Column 246: cannot generate system identifier for general entity "clear_after"
    …age=2&section_id=12001&front_id=20092&clear_after="); this.blur(); return fals…

    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 558, Column 246: general entity "clear_after" not defined and no default entity
    …age=2&section_id=12001&front_id=20092&clear_after="); this.blur(); return fals…

    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 558, Column 257: reference not terminated by REFC delimiter
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>2</a></…

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

  • Warning Line 558, Column 257: reference to external entity in attribute value
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>2</a></…

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

  • Error Line 558, Column 257: reference to entity "clear_after" for which no system identifier could be generated
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>2</a></…

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

  • Info Line 558, Column 245: entity was defined here
    …page=2&section_id=12001&front_id=20092&clear_after="); this.blur(); return fal…
  • Warning Line 558, Column 322: reference not terminated by REFC delimiter
    …lse;'>2</a></span><span class=''>&nbsp</span><span class='normal'><a href='/?&…

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

  • Warning Line 558, Column 489: reference not terminated by REFC delimiter
    …/ajax_media_list.php?page=3&section_id=12001&front_id=20092&clear_after="); th…

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

  • Warning Line 558, Column 489: reference to external entity in attribute value
    …/ajax_media_list.php?page=3&section_id=12001&front_id=20092&clear_after="); th…

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

  • Error Line 558, Column 489: reference to entity "section_id" for which no system identifier could be generated
    …/ajax_media_list.php?page=3&section_id=12001&front_id=20092&clear_after="); th…

    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 558, Column 213: entity was defined here
    …11", "/lbin/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_a…
  • Warning Line 558, Column 504: reference not terminated by REFC delimiter
    …t.php?page=3&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Warning Line 558, Column 504: reference to external entity in attribute value
    …t.php?page=3&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Error Line 558, Column 504: reference to entity "front_id" for which no system identifier could be generated
    …t.php?page=3&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

    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 558, Column 230: entity was defined here
    …media_list.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blu…
  • Warning Line 558, Column 522: reference not terminated by REFC delimiter
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>3</a></…

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

  • Warning Line 558, Column 522: reference to external entity in attribute value
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>3</a></…

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

  • Error Line 558, Column 522: reference to entity "clear_after" for which no system identifier could be generated
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>3</a></…

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

  • Info Line 558, Column 245: entity was defined here
    …page=2&section_id=12001&front_id=20092&clear_after="); this.blur(); return fal…
  • Warning Line 558, Column 587: reference not terminated by REFC delimiter
    …lse;'>3</a></span><span class=''>&nbsp</span><span class='normal'><a href='/?&…

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

  • Warning Line 558, Column 754: reference not terminated by REFC delimiter
    …/ajax_media_list.php?page=4&section_id=12001&front_id=20092&clear_after="); th…

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

  • Warning Line 558, Column 754: reference to external entity in attribute value
    …/ajax_media_list.php?page=4&section_id=12001&front_id=20092&clear_after="); th…

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

  • Error Line 558, Column 754: reference to entity "section_id" for which no system identifier could be generated
    …/ajax_media_list.php?page=4&section_id=12001&front_id=20092&clear_after="); th…

    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 558, Column 213: entity was defined here
    …11", "/lbin/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_a…
  • Warning Line 558, Column 769: reference not terminated by REFC delimiter
    …t.php?page=4&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Warning Line 558, Column 769: reference to external entity in attribute value
    …t.php?page=4&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Error Line 558, Column 769: reference to entity "front_id" for which no system identifier could be generated
    …t.php?page=4&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

    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 558, Column 230: entity was defined here
    …media_list.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blu…
  • Warning Line 558, Column 787: reference not terminated by REFC delimiter
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>4</a></…

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

  • Warning Line 558, Column 787: reference to external entity in attribute value
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>4</a></…

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

  • Error Line 558, Column 787: reference to entity "clear_after" for which no system identifier could be generated
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>4</a></…

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

  • Info Line 558, Column 245: entity was defined here
    …page=2&section_id=12001&front_id=20092&clear_after="); this.blur(); return fal…
  • Warning Line 558, Column 852: reference not terminated by REFC delimiter
    …lse;'>4</a></span><span class=''>&nbsp</span><span class='normal'><a href='/?&…

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

  • Warning Line 558, Column 1019: reference not terminated by REFC delimiter
    …/ajax_media_list.php?page=5&section_id=12001&front_id=20092&clear_after="); th…

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

  • Warning Line 558, Column 1019: reference to external entity in attribute value
    …/ajax_media_list.php?page=5&section_id=12001&front_id=20092&clear_after="); th…

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

  • Error Line 558, Column 1019: reference to entity "section_id" for which no system identifier could be generated
    …/ajax_media_list.php?page=5&section_id=12001&front_id=20092&clear_after="); th…

    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 558, Column 213: entity was defined here
    …11", "/lbin/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_a…
  • Warning Line 558, Column 1034: reference not terminated by REFC delimiter
    …t.php?page=5&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Warning Line 558, Column 1034: reference to external entity in attribute value
    …t.php?page=5&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Error Line 558, Column 1034: reference to entity "front_id" for which no system identifier could be generated
    …t.php?page=5&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

    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 558, Column 230: entity was defined here
    …media_list.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blu…
  • Warning Line 558, Column 1052: reference not terminated by REFC delimiter
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>5</a></…

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

  • Warning Line 558, Column 1052: reference to external entity in attribute value
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>5</a></…

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

  • Error Line 558, Column 1052: reference to entity "clear_after" for which no system identifier could be generated
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>5</a></…

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

  • Info Line 558, Column 245: entity was defined here
    …page=2&section_id=12001&front_id=20092&clear_after="); this.blur(); return fal…
  • Warning Line 558, Column 1117: reference not terminated by REFC delimiter
    …lse;'>5</a></span><span class=''>&nbsp</span><span class='normal'><a href='/?&…

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

  • Warning Line 558, Column 1284: reference not terminated by REFC delimiter
    …/ajax_media_list.php?page=6&section_id=12001&front_id=20092&clear_after="); th…

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

  • Warning Line 558, Column 1284: reference to external entity in attribute value
    …/ajax_media_list.php?page=6&section_id=12001&front_id=20092&clear_after="); th…

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

  • Error Line 558, Column 1284: reference to entity "section_id" for which no system identifier could be generated
    …/ajax_media_list.php?page=6&section_id=12001&front_id=20092&clear_after="); th…

    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 558, Column 213: entity was defined here
    …11", "/lbin/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_a…
  • Warning Line 558, Column 1299: reference not terminated by REFC delimiter
    …t.php?page=6&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Warning Line 558, Column 1299: reference to external entity in attribute value
    …t.php?page=6&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Error Line 558, Column 1299: reference to entity "front_id" for which no system identifier could be generated
    …t.php?page=6&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

    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 558, Column 230: entity was defined here
    …media_list.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blu…
  • Warning Line 558, Column 1317: reference not terminated by REFC delimiter
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>6</a></…

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

  • Warning Line 558, Column 1317: reference to external entity in attribute value
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>6</a></…

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

  • Error Line 558, Column 1317: reference to entity "clear_after" for which no system identifier could be generated
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>6</a></…

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

  • Info Line 558, Column 245: entity was defined here
    …page=2&section_id=12001&front_id=20092&clear_after="); this.blur(); return fal…
  • Warning Line 558, Column 1382: reference not terminated by REFC delimiter
    …lse;'>6</a></span><span class=''>&nbsp</span><span class='normal'><a href='/?&…

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

  • Warning Line 558, Column 1549: reference not terminated by REFC delimiter
    …/ajax_media_list.php?page=7&section_id=12001&front_id=20092&clear_after="); th…

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

  • Warning Line 558, Column 1549: reference to external entity in attribute value
    …/ajax_media_list.php?page=7&section_id=12001&front_id=20092&clear_after="); th…

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

  • Error Line 558, Column 1549: reference to entity "section_id" for which no system identifier could be generated
    …/ajax_media_list.php?page=7&section_id=12001&front_id=20092&clear_after="); th…

    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 558, Column 213: entity was defined here
    …11", "/lbin/ajax_media_list.php?page=2&section_id=12001&front_id=20092&clear_a…
  • Warning Line 558, Column 1564: reference not terminated by REFC delimiter
    …t.php?page=7&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Warning Line 558, Column 1564: reference to external entity in attribute value
    …t.php?page=7&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

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

  • Error Line 558, Column 1564: reference to entity "front_id" for which no system identifier could be generated
    …t.php?page=7&section_id=12001&front_id=20092&clear_after="); this.blur(); retu…

    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 558, Column 230: entity was defined here
    …media_list.php?page=2&section_id=12001&front_id=20092&clear_after="); this.blu…
  • Warning Line 558, Column 1582: reference not terminated by REFC delimiter
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>7</a></…

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

  • Warning Line 558, Column 1582: reference to external entity in attribute value
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>7</a></…

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

  • Error Line 558, Column 1582: reference to entity "clear_after" for which no system identifier could be generated
    …on_id=12001&front_id=20092&clear_after="); this.blur(); return false;'>7</a></…

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

  • Info Line 558, Column 245: entity was defined here
    …page=2&section_id=12001&front_id=20092&clear_after="); this.blur(); return fal…
  • Error Line 569, Column 43: document type does not allow element "style" here
    	<p id="jaje_style"><style type="text/css">

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

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

  • Error Line 596, Column 22: there is no attribute "css"
    </script><fb:fan css="http://static.novatv.hr/zadovoljna/facebook_1.css" border…

    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 596, Column 87: there is no attribute "border_color"
    …dovoljna/facebook_1.css" border_color="FCECEF" font="trebuchet ms" colorscheme…

    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 596, Column 101: there is no attribute "font"
    …ook_1.css" border_color="FCECEF" font="trebuchet ms" colorscheme="light" heade…

    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 596, Column 128: there is no attribute "colorscheme"
    …ECEF" font="trebuchet ms" colorscheme="light" header="true" height="449" width…

    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 596, Column 143: there is no attribute "header"
    …buchet ms" colorscheme="light" header="true" height="449" width="544" connecti…

    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 596, Column 157: there is no attribute "height"
    …orscheme="light" header="true" height="449" width="544" connections="false" si…

    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 596, Column 169: there is no attribute "width"
    …ght" header="true" height="449" width="544" connections="false" site="zadovolj…

    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 596, Column 187: there is no attribute "connections"
    … height="449" width="544" connections="false" site="zadovoljna.hr" stream="tru…

    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 596, Column 200: there is no attribute "site"
    … width="544" connections="false" site="zadovoljna.hr" stream="true" profile_id…

    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 596, Column 223: there is no attribute "stream"
    …s="false" site="zadovoljna.hr" stream="true" profile_id="125934368802"></fb:fa…

    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 596, Column 241: there is no attribute "profile_id"
    …e" site="zadovoljna.hr" stream="true" profile_id="125934368802"></fb:fan></div>

    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 596, Column 255: element "fb:fan" undefined
    …e" site="zadovoljna.hr" stream="true" profile_id="125934368802"></fb:fan></div>

    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 673, Column 39: "itemscope" is not a member of a group specified for any attribute
    				<div id="small_content" itemscope itemtype="http://schema.org/WPSideBar">
  • Error Line 696, Column 182: end tag for "img" omitted, but OMITTAG NO was specified
    … alt="Pretraživanje" onclick="doSearch(); return false;" class="search_button">

    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 696, Column 49: start tag was here
    <img src="/static/hr/microsites/default/…
  • Error Line 704, Column 82: "itemscope" is not a member of a group specified for any attribute
    …3_pb_m m3_g_4 m3_pb_m banner" itemscope itemtype="http://schema.org/WPAdBlock">
  • Error Line 736, Column 67: "itemscope" is not a member of a group specified for any attribute
    …3_pb_m m3_g_4 m3_pb_m banner" itemscope itemtype="http://schema.org/WPAdBlock">
  • Error Line 822, Column 61: "itemscope" is not a member of a group specified for any attribute
    …3_pb_m m3_g_4 m3_pb_m banner" itemscope itemtype="http://schema.org/WPAdBlock">
  • Error Line 901, Column 7: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
        <p>

    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 905, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div><div id="oyo_news" class="small_box"> <h2><a class="header" href="http://…

    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 901, Column 5: start tag was here
        <p>
  • Error Line 905, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div><div id="oyo_news" class="small_box"> <h2><a class="header" href="http://…

    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 899, Column 5: start tag was here
        <p class="title_anchor">
  • Error Line 907, Column 217: required attribute "alt" not specified
    …ik.hr/media/images/132x183/Dec2012/60731647.jpg'> Sila, epizoda 43</a><!--br />

    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 907, Column 218: end tag for "img" omitted, but OMITTAG NO was specified
    …ik.hr/media/images/132x183/Dec2012/60731647.jpg'> Sila, epizoda 43</a><!--br />

    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 907, Column 141: start tag was here
    …/8219-sila-epizoda-43" rel="PRODUCT-"><img src='http://image.dnevnik.hr/media/…
  • Error Line 910, Column 14: ID "external_item" already defined
        <div id="external_item" style="position: relative;"> <a href="http://oyo.dn…

    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 907, Column 14: ID "external_item" first defined here
        <div id="external_item" style="position: relative;"> <a href="http://oyo.dn…
  • Error Line 910, Column 233: required attribute "alt" not specified
    …a/images/132x183/Sep2012/60682015.jpg'> Larin izbor, sezona 2 - epizoda 85</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 910, Column 234: end tag for "img" omitted, but OMITTAG NO was specified
    …/images/132x183/Sep2012/60682015.jpg'> Larin izbor, sezona 2 - epizoda 85</a><…

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

  • Info Line 910, Column 157: start tag was here
    …r-sezona-2-epizoda-85" rel="PRODUCT-"><img src='http://image.dnevnik.hr/media/…
  • Error Line 947, Column 8: document type does not allow element "dt" here; assuming missing "dl" start-tag
    				<dt><h2>Kojeg se sitnog poroka ne možete odreći?</h2></dt>
  • Error Line 947, Column 12: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<dt><h2>Kojeg se sitnog poroka ne možete odreći?</h2></dt>

    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 949, Column 15: document type does not allow element "fieldset" here; missing one of "object", "applet", "map", "iframe", "ins", "del" start-tag
    					<fieldset>

    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 983, Column 10: end tag for "dl" omitted, but OMITTAG NO was specified
    			</form>

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

  • Info Line 947, Column 5: start tag was here
    				<dt><h2>Kojeg se sitnog poroka ne možete odreći?</h2></dt>
  • Warning Line 992, Column 77: cannot generate system identifier for general entity "id"
    …" href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013…

    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 992, Column 77: general entity "id" not defined and no default entity
    …" href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013…

    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 992, Column 79: reference not terminated by REFC delimiter
    …href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/0…

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

  • Warning Line 992, Column 79: reference to external entity in attribute value
    …href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/0…

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

  • Error Line 992, Column 79: reference to entity "id" for which no system identifier could be generated
    …href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/0…

    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 992, Column 76: entity was defined here
    …k" href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/201…
  • Warning Line 992, Column 85: cannot generate system identifier for general entity "url"
    …http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/1631…

    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 992, Column 85: general entity "url" not defined and no default entity
    …http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/1631…

    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 992, Column 88: reference not terminated by REFC delimiter
    …p://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/1631515…

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

  • Warning Line 992, Column 88: reference to external entity in attribute value
    …p://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/1631515…

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

  • Error Line 992, Column 88: reference to entity "url" for which no system identifier could be generated
    …p://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/1631515…

    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 992, Column 84: entity was defined here
    …"http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/163…
  • Error Line 992, Column 235: required attribute "alt" not specified
    …e.html"><img src="http://www.blog.hr/img/hr/satisfiedrss/2013/qu5copy.jpg"></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 992, Column 239: end tag for "img" omitted, but OMITTAG NO was specified
    …e.html"><img src="http://www.blog.hr/img/hr/satisfiedrss/2013/qu5copy.jpg"></a>

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

  • Info Line 992, Column 169: start tag was here
    …/brzinski-rucak-quiche-lorraine.html"><img src="http://www.blog.hr/img/hr/sati…
  • Warning Line 993, Column 79: reference not terminated by REFC delimiter
    …href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/0…

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

  • Warning Line 993, Column 79: reference to external entity in attribute value
    …href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/0…

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

  • Error Line 993, Column 79: reference to entity "id" for which no system identifier could be generated
    …href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/0…

    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 992, Column 76: entity was defined here
    …k" href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/201…
  • Warning Line 993, Column 88: reference not terminated by REFC delimiter
    …p://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/1631515…

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

  • Warning Line 993, Column 88: reference to external entity in attribute value
    …p://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/1631515…

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

  • Error Line 993, Column 88: reference to entity "url" for which no system identifier could be generated
    …p://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/1631515…

    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 992, Column 84: entity was defined here
    …"http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/163…
  • Warning Line 998, Column 79: reference not terminated by REFC delimiter
    …href="http://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/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.

  • Warning Line 998, Column 79: reference to external entity in attribute value
    …href="http://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/2…

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

  • Error Line 998, Column 79: reference to entity "id" for which no system identifier could be generated
    …href="http://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/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 992, Column 76: entity was defined here
    …k" href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/201…
  • Warning Line 998, Column 88: reference not terminated by REFC delimiter
    …p://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/2013/02/16…

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

  • Warning Line 998, Column 88: reference to external entity in attribute value
    …p://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/2013/02/16…

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

  • Error Line 998, Column 88: reference to entity "url" for which no system identifier could be generated
    …p://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/2013/02/16…

    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 992, Column 84: entity was defined here
    …"http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/163…
  • Error Line 998, Column 232: required attribute "alt" not specified
    … src="http://www.blog.hr/img/hr/satisfiedrss/2013/life_thinkstock-001.jpg"></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 998, Column 236: end tag for "img" omitted, but OMITTAG NO was specified
    … src="http://www.blog.hr/img/hr/satisfiedrss/2013/life_thinkstock-001.jpg"></a>

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

  • Info Line 998, Column 154: start tag was here
    …r/2013/02/1631515606/neizbjezno.html"><img src="http://www.blog.hr/img/hr/sati…
  • Warning Line 999, Column 79: reference not terminated by REFC delimiter
    …href="http://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/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.

  • Warning Line 999, Column 79: reference to external entity in attribute value
    …href="http://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/2…

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

  • Error Line 999, Column 79: reference to entity "id" for which no system identifier could be generated
    …href="http://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/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 992, Column 76: entity was defined here
    …k" href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/201…
  • Warning Line 999, Column 88: reference not terminated by REFC delimiter
    …p://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/2013/02/16…

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

  • Warning Line 999, Column 88: reference to external entity in attribute value
    …p://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/2013/02/16…

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

  • Error Line 999, Column 88: reference to entity "url" for which no system identifier could be generated
    …p://www.blog.hr/jump/?rn=4&id=1644&url=http://beforegoodbye.blog.hr/2013/02/16…

    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 992, Column 84: entity was defined here
    …"http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/163…
  • Warning Line 1004, Column 79: reference not terminated by REFC delimiter
    …href="http://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/16…

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

  • Warning Line 1004, Column 79: reference to external entity in attribute value
    …href="http://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/16…

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

  • Error Line 1004, Column 79: reference to entity "id" for which no system identifier could be generated
    …href="http://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/16…

    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 992, Column 76: entity was defined here
    …k" href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/201…
  • Warning Line 1004, Column 88: reference not terminated by REFC delimiter
    …p://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/1631514537/…

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

  • Warning Line 1004, Column 88: reference to external entity in attribute value
    …p://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/1631514537/…

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

  • Error Line 1004, Column 88: reference to entity "url" for which no system identifier could be generated
    …p://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/1631514537/…

    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 992, Column 84: entity was defined here
    …"http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/163…
  • Error Line 1004, Column 235: required attribute "alt" not specified
    … src="http://www.blog.hr/img/hr/satisfiedrss/2013/stripper_thinkstock.jpg"></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 1004, Column 239: end tag for "img" omitted, but OMITTAG NO was specified
    … src="http://www.blog.hr/img/hr/satisfiedrss/2013/stripper_thinkstock.jpg"></a>

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

  • Info Line 1004, Column 157: start tag was here
    …31514537/sretno-nam-valentinovo.html"><img src="http://www.blog.hr/img/hr/sati…
  • Warning Line 1005, Column 79: reference not terminated by REFC delimiter
    …href="http://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/16…

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

  • Warning Line 1005, Column 79: reference to external entity in attribute value
    …href="http://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/16…

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

  • Error Line 1005, Column 79: reference to entity "id" for which no system identifier could be generated
    …href="http://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/16…

    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 992, Column 76: entity was defined here
    …k" href="http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/201…
  • Warning Line 1005, Column 88: reference not terminated by REFC delimiter
    …p://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/1631514537/…

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

  • Warning Line 1005, Column 88: reference to external entity in attribute value
    …p://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/1631514537/…

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

  • Error Line 1005, Column 88: reference to entity "url" for which no system identifier could be generated
    …p://www.blog.hr/jump/?rn=4&id=1643&url=http://lido.blog.hr/2013/02/1631514537/…

    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 992, Column 84: entity was defined here
    …"http://www.blog.hr/jump/?rn=4&id=1645&url=http://kulerica.blog.hr/2013/02/163…
  • Error Line 1056, Column 42: required attribute "type" not specified
    …cript src="http://www2.novatv.hr/e.js"></script> <script type="text/javascript…

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

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

  • Error Line 1085, Column 7: end tag for element "div" which is not open
    	</div>

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

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

  • Warning Line 1152, Column 59: cannot generate system identifier for general entity "appId"
    …		js.src = "//connect.facebook.net/hr_HR/all.js#xfbml=1&appId=115151418518688";

    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 1152, Column 59: general entity "appId" not defined and no default entity
    …		js.src = "//connect.facebook.net/hr_HR/all.js#xfbml=1&appId=115151418518688";

    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 1152, Column 64: reference not terminated by REFC delimiter
    …		js.src = "//connect.facebook.net/hr_HR/all.js#xfbml=1&appId=115151418518688";

    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 1152, Column 64: reference to entity "appId" for which no system identifier could be generated
    …		js.src = "//connect.facebook.net/hr_HR/all.js#xfbml=1&appId=115151418518688";

    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 1152, Column 58: entity was defined here
    …		js.src = "//connect.facebook.net/hr_HR/all.js#xfbml=1&appId=115151418518688";
  • Error Line 1164, Column 9: required attribute "type" not specified
    	<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':new Date().g…

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

  • Warning Line 1164, Column 182: cannot generate system identifier for general entity "l"
    ….createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='//www.googl…

    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 1164, Column 182: general entity "l" not defined and no default entity
    ….createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='//www.googl…

    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 1164, Column 183: reference not terminated by REFC delimiter
    …createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='//www.google…

    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 1164, Column 183: reference to entity "l" for which no system identifier could be generated
    …createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='//www.google…

    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 1164, Column 181: entity was defined here
    …d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='//www.goog…

Visitor Analysis

Daily Visitor
  • 112 visits