Internet Monitor pop kulturni e-zine koji pokriva vijesti iz politike, kulture, sporta, zdravlja i zabave. ...

monitor.hr
  • Domain Name
    monitor.hr
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #34847
  • Page Size
    244.7 KB
  • Ip Address
    46.4.100.141
  • Heading
    H1: 0, H2: 44, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    89 GIF, 55 JPG, 6 PNG

Website Meta Analysis

  • Title
    Internet Monitor
  • Meta Keyword
  • Meta Description
    Internet Monitor pop kulturni e-zine koji pokriva vijesti iz politike, kulture, sporta, zdravlja i zabave.

Technical Analysis

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

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

HTML Analysis

  • date: Wed, 26 Jun 2013 22:30:27 GMT
  • server: Apache
  • last-modified: Wed, 26 Jun 2013 22:30:05 GMT
  • accept-ranges: bytes
  • content-length: 235521
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for monitor.hr

DNS Analysis


DNS servers
ns16.orbis.hr
ns.orbis.hr [195.29.89.100]


DNS Records

Answer records
monitor.hr A 46.4.100.141 3600s
monitor.hr SOA
server: ns.orbis.hr
email: serverbuddy@orbis.hr
serial: 2008061856
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
monitor.hr NS  ns16.orbis.hr 86400s
monitor.hr NS  ns.orbis.hr 86400s
monitor.hr MX
preference: 0
exchange: mail.monitor.hr
3600s

Authority records

Additional records
ns.orbis.hr A 195.29.89.100 14400s
ns16.orbis.hr A 88.198.53.80 14400s
mail.monitor.hr A 46.4.100.141 3600s

IP 46.4.100.141 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 462 Errors
  • 344 Warnings
Ratio Text/Html
  • 0.6991826765745848
Message Error
  • Error Line 22, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 26, Column 57: cannot generate system identifier for general entity "cookie"
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";

    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 26, Column 57: general entity "cookie" not defined and no default entity
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";

    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 26, Column 63: reference not terminated by REFC delimiter
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";

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

    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 26, Column 56: entity was defined here
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";
  • Warning Line 26, Column 66: cannot generate system identifier for general entity "status"
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";

    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 26, Column 66: general entity "status" not defined and no default entity
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";

    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 26, Column 72: reference not terminated by REFC delimiter
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";

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

    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 26, Column 65: entity was defined here
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";
  • Warning Line 26, Column 75: cannot generate system identifier for general entity "appId"
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";

    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 26, Column 75: general entity "appId" not defined and no default entity
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";

    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 26, Column 80: reference not terminated by REFC delimiter
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";

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

    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 26, Column 74: entity was defined here
    …connect.facebook.net/hr_HR/all.js#xfbml=1&cookie=1&status=1&appId=63308471719";
  • Warning Line 40, Column 80: cannot generate system identifier for general entity "label"
    …onitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1"…

    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 40, Column 80: general entity "label" not defined and no default entity
    …onitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1"…

    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 40, Column 85: reference not terminated by REFC delimiter
    …r.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Foru…

    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 40, Column 85: reference to external entity in attribute value
    …r.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Foru…

    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 40, Column 85: reference to entity "label" for which no system identifier could be generated
    …r.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Foru…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 40, Column 116: cannot generate system identifier for general entity "s"
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>

    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 40, Column 116: general entity "s" not defined and no default entity
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>

    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 40, Column 117: reference not terminated by REFC delimiter
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>

    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 40, Column 117: reference to external entity in attribute value
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>

    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 40, Column 117: reference to entity "s" for which no system identifier could be generated
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 42, Column 102: reference not terminated by REFC delimiter
    …hr/jump2.php?url=www.jutarnji.hr&label=Hrvatski%20web%20-%20Jutarnji&s=1">Juta…

    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 42, Column 102: reference to external entity in attribute value
    …hr/jump2.php?url=www.jutarnji.hr&label=Hrvatski%20web%20-%20Jutarnji&s=1">Juta…

    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 42, Column 102: reference to entity "label" for which no system identifier could be generated
    …hr/jump2.php?url=www.jutarnji.hr&label=Hrvatski%20web%20-%20Jutarnji&s=1">Juta…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 42, Column 134: reference not terminated by REFC delimiter
    …?url=www.jutarnji.hr&label=Hrvatski%20web%20-%20Jutarnji&s=1">Jutarnji</a></li>

    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 42, Column 134: reference to external entity in attribute value
    …?url=www.jutarnji.hr&label=Hrvatski%20web%20-%20Jutarnji&s=1">Jutarnji</a></li>

    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 42, Column 134: reference to entity "s" for which no system identifier could be generated
    …?url=www.jutarnji.hr&label=Hrvatski%20web%20-%20Jutarnji&s=1">Jutarnji</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 44, Column 102: reference not terminated by REFC delimiter
    …hr/jump2.php?url=www.vecernji.hr&label=Hrvatski%20web%20-%20Večernji&s=1">Veče…

    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 44, Column 102: reference to external entity in attribute value
    …hr/jump2.php?url=www.vecernji.hr&label=Hrvatski%20web%20-%20Večernji&s=1">Veče…

    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 44, Column 102: reference to entity "label" for which no system identifier could be generated
    …hr/jump2.php?url=www.vecernji.hr&label=Hrvatski%20web%20-%20Večernji&s=1">Veče…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 44, Column 134: reference not terminated by REFC delimiter
    …?url=www.vecernji.hr&label=Hrvatski%20web%20-%20Večernji&s=1">Večernji</a></li>

    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 44, Column 134: reference to external entity in attribute value
    …?url=www.vecernji.hr&label=Hrvatski%20web%20-%20Večernji&s=1">Večernji</a></li>

    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 44, Column 134: reference to entity "s" for which no system identifier could be generated
    …?url=www.vecernji.hr&label=Hrvatski%20web%20-%20Večernji&s=1">Večernji</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 46, Column 112: reference not terminated by REFC delimiter
    …hp?url=www.slobodnadalmacija.com&label=Hrvatski%20web%20-%20Slobodna%20Dal.&s=…

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

  • Warning Line 46, Column 112: reference to external entity in attribute value
    …hp?url=www.slobodnadalmacija.com&label=Hrvatski%20web%20-%20Slobodna%20Dal.&s=…

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

  • Error Line 46, Column 112: reference to entity "label" for which no system identifier could be generated
    …hp?url=www.slobodnadalmacija.com&label=Hrvatski%20web%20-%20Slobodna%20Dal.&s=…

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

  • Info Line 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 46, Column 151: reference not terminated by REFC delimiter
    …cija.com&label=Hrvatski%20web%20-%20Slobodna%20Dal.&s=1">Slobodna Dal.</a></li>

    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 46, Column 151: reference to external entity in attribute value
    …cija.com&label=Hrvatski%20web%20-%20Slobodna%20Dal.&s=1">Slobodna Dal.</a></li>

    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 46, Column 151: reference to entity "s" for which no system identifier could be generated
    …cija.com&label=Hrvatski%20web%20-%20Slobodna%20Dal.&s=1">Slobodna Dal.</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 48, Column 102: reference not terminated by REFC delimiter
    …hr/jump2.php?url=www.tportal.hr/&label=Hrvatski%20web%20-%20T%20portal&s=1">Tp…

    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 48, Column 102: reference to external entity in attribute value
    …hr/jump2.php?url=www.tportal.hr/&label=Hrvatski%20web%20-%20T%20portal&s=1">Tp…

    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 48, Column 102: reference to entity "label" for which no system identifier could be generated
    …hr/jump2.php?url=www.tportal.hr/&label=Hrvatski%20web%20-%20T%20portal&s=1">Tp…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 48, Column 136: reference not terminated by REFC delimiter
    …url=www.tportal.hr/&label=Hrvatski%20web%20-%20T%20portal&s=1">Tportal</a></li>

    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 48, Column 136: reference to external entity in attribute value
    …url=www.tportal.hr/&label=Hrvatski%20web%20-%20T%20portal&s=1">Tportal</a></li>

    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 48, Column 136: reference to entity "s" for which no system identifier could be generated
    …url=www.tportal.hr/&label=Hrvatski%20web%20-%20T%20portal&s=1">Tportal</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 50, Column 97: reference not terminated by REFC delimiter
    …itor.hr/jump2.php?url=www.net.hr&label=Hrvatski%20web%20-%20Net&s=1">Net.hr</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 50, Column 97: reference to external entity in attribute value
    …itor.hr/jump2.php?url=www.net.hr&label=Hrvatski%20web%20-%20Net&s=1">Net.hr</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 50, Column 97: reference to entity "label" for which no system identifier could be generated
    …itor.hr/jump2.php?url=www.net.hr&label=Hrvatski%20web%20-%20Net&s=1">Net.hr</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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 50, Column 124: reference not terminated by REFC delimiter
    …hr/jump2.php?url=www.net.hr&label=Hrvatski%20web%20-%20Net&s=1">Net.hr</a></li>

    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 50, Column 124: reference to external entity in attribute value
    …hr/jump2.php?url=www.net.hr&label=Hrvatski%20web%20-%20Net&s=1">Net.hr</a></li>

    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 50, Column 124: reference to entity "s" for which no system identifier could be generated
    …hr/jump2.php?url=www.net.hr&label=Hrvatski%20web%20-%20Net&s=1">Net.hr</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 52, Column 99: reference not terminated by REFC delimiter
    …or.hr/jump2.php?url=www.index.hr&label=Hrvatski%20web%20-%20Index&s=1">Index</…

    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 52, Column 99: reference to external entity in attribute value
    …or.hr/jump2.php?url=www.index.hr&label=Hrvatski%20web%20-%20Index&s=1">Index</…

    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 52, Column 99: reference to entity "label" for which no system identifier could be generated
    …or.hr/jump2.php?url=www.index.hr&label=Hrvatski%20web%20-%20Index&s=1">Index</…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 52, Column 128: reference not terminated by REFC delimiter
    …jump2.php?url=www.index.hr&label=Hrvatski%20web%20-%20Index&s=1">Index</a></li>

    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 52, Column 128: reference to external entity in attribute value
    …jump2.php?url=www.index.hr&label=Hrvatski%20web%20-%20Index&s=1">Index</a></li>

    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 52, Column 128: reference to entity "s" for which no system identifier could be generated
    …jump2.php?url=www.index.hr&label=Hrvatski%20web%20-%20Index&s=1">Index</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 54, Column 102: reference not terminated by REFC delimiter
    …hr/jump2.php?url=www.dnevnik.hr/&label=Hrvatski%20web%20-%20www.dnevnik.hr&s=1…

    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 54, Column 102: reference to external entity in attribute value
    …hr/jump2.php?url=www.dnevnik.hr/&label=Hrvatski%20web%20-%20www.dnevnik.hr&s=1…

    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 54, Column 102: reference to entity "label" for which no system identifier could be generated
    …hr/jump2.php?url=www.dnevnik.hr/&label=Hrvatski%20web%20-%20www.dnevnik.hr&s=1…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 54, Column 140: reference not terminated by REFC delimiter
    ….dnevnik.hr/&label=Hrvatski%20web%20-%20www.dnevnik.hr&s=1">Dnevnik.hr</a></li>

    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 54, Column 140: reference to external entity in attribute value
    ….dnevnik.hr/&label=Hrvatski%20web%20-%20www.dnevnik.hr&s=1">Dnevnik.hr</a></li>

    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 54, Column 140: reference to entity "s" for which no system identifier could be generated
    ….dnevnik.hr/&label=Hrvatski%20web%20-%20www.dnevnik.hr&s=1">Dnevnik.hr</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 56, Column 100: reference not terminated by REFC delimiter
    …r.hr/jump2.php?url=www.24sata.hr&label=Hrvatski%20web%20-%2024%20sata&s=1">24s…

    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 56, Column 100: reference to external entity in attribute value
    …r.hr/jump2.php?url=www.24sata.hr&label=Hrvatski%20web%20-%2024%20sata&s=1">24s…

    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 56, Column 100: reference to entity "label" for which no system identifier could be generated
    …r.hr/jump2.php?url=www.24sata.hr&label=Hrvatski%20web%20-%2024%20sata&s=1">24s…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 56, Column 133: reference not terminated by REFC delimiter
    …php?url=www.24sata.hr&label=Hrvatski%20web%20-%2024%20sata&s=1">24sata</a></li>

    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 56, Column 133: reference to external entity in attribute value
    …php?url=www.24sata.hr&label=Hrvatski%20web%20-%2024%20sata&s=1">24sata</a></li>

    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 56, Column 133: reference to entity "s" for which no system identifier could be generated
    …php?url=www.24sata.hr&label=Hrvatski%20web%20-%2024%20sata&s=1">24sata</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 59, Column 26: reference not terminated by REFC delimiter
    url=www.novilist.hr&label=Hrvatski%20web%20-%20Novilist&s=1">Novi list</a></li>

    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 59, Column 26: reference to external entity in attribute value
    url=www.novilist.hr&label=Hrvatski%20web%20-%20Novilist&s=1">Novi list</a></li>

    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 59, Column 26: reference to entity "label" for which no system identifier could be generated
    url=www.novilist.hr&label=Hrvatski%20web%20-%20Novilist&s=1">Novi list</a></li>

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 59, Column 58: reference not terminated by REFC delimiter
    url=www.novilist.hr&label=Hrvatski%20web%20-%20Novilist&s=1">Novi list</a></li>

    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 59, Column 58: reference to external entity in attribute value
    url=www.novilist.hr&label=Hrvatski%20web%20-%20Novilist&s=1">Novi list</a></li>

    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 59, Column 58: reference to entity "s" for which no system identifier could be generated
    url=www.novilist.hr&label=Hrvatski%20web%20-%20Novilist&s=1">Novi list</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 61, Column 84: cannot generate system identifier for general entity "a_bid"
    …tiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></li…

    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 61, Column 84: general entity "a_bid" not defined and no default entity
    …tiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></li…

    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 61, Column 89: reference not terminated by REFC delimiter
    …tiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></li>

    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 61, Column 89: reference to external entity in attribute value
    …tiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></li>

    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 61, Column 89: reference to entity "a_bid" for which no system identifier could be generated
    …tiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></li>

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 63, Column 106: reference not terminated by REFC delimiter
    …ump2.php?url=www.metro-portal.hr&label=Hrvatski%20web%20-%20Metro%20portal&s=1…

    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 63, Column 106: reference to external entity in attribute value
    …ump2.php?url=www.metro-portal.hr&label=Hrvatski%20web%20-%20Metro%20portal&s=1…

    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 63, Column 106: reference to entity "label" for which no system identifier could be generated
    …ump2.php?url=www.metro-portal.hr&label=Hrvatski%20web%20-%20Metro%20portal&s=1…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 63, Column 144: reference not terminated by REFC delimiter
    …-portal.hr&label=Hrvatski%20web%20-%20Metro%20portal&s=1">Metro portal</a></li>

    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 63, Column 144: reference to external entity in attribute value
    …-portal.hr&label=Hrvatski%20web%20-%20Metro%20portal&s=1">Metro portal</a></li>

    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 63, Column 144: reference to entity "s" for which no system identifier could be generated
    …-portal.hr&label=Hrvatski%20web%20-%20Metro%20portal&s=1">Metro portal</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 65, Column 97: reference not terminated by REFC delimiter
    …itor.hr/jump2.php?url=www.hrt.hr&label=Hrvatski%20web%20-%20HRT%20vijesti&s=1"…

    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 65, Column 97: reference to external entity in attribute value
    …itor.hr/jump2.php?url=www.hrt.hr&label=Hrvatski%20web%20-%20HRT%20vijesti&s=1"…

    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 65, Column 97: reference to entity "label" for which no system identifier could be generated
    …itor.hr/jump2.php?url=www.hrt.hr&label=Hrvatski%20web%20-%20HRT%20vijesti&s=1"…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 65, Column 134: reference not terminated by REFC delimiter
    …l=www.hrt.hr&label=Hrvatski%20web%20-%20HRT%20vijesti&s=1">HRT vijesti</a></li>

    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 65, Column 134: reference to external entity in attribute value
    …l=www.hrt.hr&label=Hrvatski%20web%20-%20HRT%20vijesti&s=1">HRT vijesti</a></li>

    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 65, Column 134: reference to entity "s" for which no system identifier could be generated
    …l=www.hrt.hr&label=Hrvatski%20web%20-%20HRT%20vijesti&s=1">HRT vijesti</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 67, Column 102: reference not terminated by REFC delimiter
    …hr/jump2.php?url=www.radio101.hr&label=Hrvatski%20web%20-%20Radio%20101&s=1">R…

    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 67, Column 102: reference to external entity in attribute value
    …hr/jump2.php?url=www.radio101.hr&label=Hrvatski%20web%20-%20Radio%20101&s=1">R…

    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 67, Column 102: reference to entity "label" for which no system identifier could be generated
    …hr/jump2.php?url=www.radio101.hr&label=Hrvatski%20web%20-%20Radio%20101&s=1">R…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 67, Column 137: reference not terminated by REFC delimiter
    …=www.radio101.hr&label=Hrvatski%20web%20-%20Radio%20101&s=1">Radio 101</a></li>

    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 67, Column 137: reference to external entity in attribute value
    …=www.radio101.hr&label=Hrvatski%20web%20-%20Radio%20101&s=1">Radio 101</a></li>

    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 67, Column 137: reference to entity "s" for which no system identifier could be generated
    …=www.radio101.hr&label=Hrvatski%20web%20-%20Radio%20101&s=1">Radio 101</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 69, Column 107: reference not terminated by REFC delimiter
    …mp2.php?url=www.zagrebancija.com&label=Hrvatski%20web%20-%20Zagrebancija&s=1">…

    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 69, Column 107: reference to external entity in attribute value
    …mp2.php?url=www.zagrebancija.com&label=Hrvatski%20web%20-%20Zagrebancija&s=1">…

    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 69, Column 107: reference to entity "label" for which no system identifier could be generated
    …mp2.php?url=www.zagrebancija.com&label=Hrvatski%20web%20-%20Zagrebancija&s=1">…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 69, Column 143: reference not terminated by REFC delimiter
    …ebancija.com&label=Hrvatski%20web%20-%20Zagrebancija&s=1">Zagrebancija</a></li>

    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 69, Column 143: reference to external entity in attribute value
    …ebancija.com&label=Hrvatski%20web%20-%20Zagrebancija&s=1">Zagrebancija</a></li>

    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 69, Column 143: reference to entity "s" for which no system identifier could be generated
    …ebancija.com&label=Hrvatski%20web%20-%20Zagrebancija&s=1">Zagrebancija</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 71, Column 81: reference not terminated by REFC delimiter
    …ow.hr/jump2.php?url=www.show.hr/&label=Hrvatski%20web%20-%20show.hr&s=1" rel="…

    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 71, Column 81: reference to external entity in attribute value
    …ow.hr/jump2.php?url=www.show.hr/&label=Hrvatski%20web%20-%20show.hr&s=1" rel="…

    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 71, Column 81: reference to entity "label" for which no system identifier could be generated
    …ow.hr/jump2.php?url=www.show.hr/&label=Hrvatski%20web%20-%20show.hr&s=1" rel="…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 71, Column 112: reference not terminated by REFC delimiter
    …how.hr/&label=Hrvatski%20web%20-%20show.hr&s=1" rel="nofollow">Show.hr</a></li>

    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 71, Column 112: reference to external entity in attribute value
    …how.hr/&label=Hrvatski%20web%20-%20show.hr&s=1" rel="nofollow">Show.hr</a></li>

    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 71, Column 112: reference to entity "s" for which no system identifier could be generated
    …how.hr/&label=Hrvatski%20web%20-%20show.hr&s=1" rel="nofollow">Show.hr</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 77, Column 102: reference not terminated by REFC delimiter
    …hr/jump2.php?url=www.znanost.com&label=Hrvatski%20web%20-%20Znanost.com&s=1">Z…

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

  • Warning Line 77, Column 102: reference to external entity in attribute value
    …hr/jump2.php?url=www.znanost.com&label=Hrvatski%20web%20-%20Znanost.com&s=1">Z…

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

  • Error Line 77, Column 102: reference to entity "label" for which no system identifier could be generated
    …hr/jump2.php?url=www.znanost.com&label=Hrvatski%20web%20-%20Znanost.com&s=1">Z…

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

  • Info Line 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 77, Column 137: reference not terminated by REFC delimiter
    …ww.znanost.com&label=Hrvatski%20web%20-%20Znanost.com&s=1">Znanost.com</a></li>

    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 77, Column 137: reference to external entity in attribute value
    …ww.znanost.com&label=Hrvatski%20web%20-%20Znanost.com&s=1">Znanost.com</a></li>

    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 77, Column 137: reference to entity "s" for which no system identifier could be generated
    …ww.znanost.com&label=Hrvatski%20web%20-%20Znanost.com&s=1">Znanost.com</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 80, Column 31: reference not terminated by REFC delimiter
    url=www.bankamagazine.hr&label=Hrvatski%20web%20-%20Banka&s=1">Banka</a></li>

    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 80, Column 31: reference to external entity in attribute value
    url=www.bankamagazine.hr&label=Hrvatski%20web%20-%20Banka&s=1">Banka</a></li>

    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 80, Column 31: reference to entity "label" for which no system identifier could be generated
    url=www.bankamagazine.hr&label=Hrvatski%20web%20-%20Banka&s=1">Banka</a></li>

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 80, Column 60: reference not terminated by REFC delimiter
    url=www.bankamagazine.hr&label=Hrvatski%20web%20-%20Banka&s=1">Banka</a></li>

    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 80, Column 60: reference to external entity in attribute value
    url=www.bankamagazine.hr&label=Hrvatski%20web%20-%20Banka&s=1">Banka</a></li>

    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 80, Column 60: reference to entity "s" for which no system identifier could be generated
    url=www.bankamagazine.hr&label=Hrvatski%20web%20-%20Banka&s=1">Banka</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 82, Column 97: reference not terminated by REFC delimiter
    …itor.hr/jump2.php?url=www.bug.hr&label=Hrvatski%20web%20-%20Bug&s=1">Bug</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 82, Column 97: reference to external entity in attribute value
    …itor.hr/jump2.php?url=www.bug.hr&label=Hrvatski%20web%20-%20Bug&s=1">Bug</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 82, Column 97: reference to entity "label" for which no system identifier could be generated
    …itor.hr/jump2.php?url=www.bug.hr&label=Hrvatski%20web%20-%20Bug&s=1">Bug</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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 82, Column 124: reference not terminated by REFC delimiter
    …or.hr/jump2.php?url=www.bug.hr&label=Hrvatski%20web%20-%20Bug&s=1">Bug</a></li>

    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 82, Column 124: reference to external entity in attribute value
    …or.hr/jump2.php?url=www.bug.hr&label=Hrvatski%20web%20-%20Bug&s=1">Bug</a></li>

    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 82, Column 124: reference to entity "s" for which no system identifier could be generated
    …or.hr/jump2.php?url=www.bug.hr&label=Hrvatski%20web%20-%20Bug&s=1">Bug</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 84, Column 101: reference not terminated by REFC delimiter
    ….hr/jump2.php?url=www.recepti.hr&label=Hrvatski%20web%20-%20Recepti.hr&s=1">Hr…

    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 84, Column 101: reference to external entity in attribute value
    ….hr/jump2.php?url=www.recepti.hr&label=Hrvatski%20web%20-%20Recepti.hr&s=1">Hr…

    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 84, Column 101: reference to entity "label" for which no system identifier could be generated
    ….hr/jump2.php?url=www.recepti.hr&label=Hrvatski%20web%20-%20Recepti.hr&s=1">Hr…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 84, Column 135: reference not terminated by REFC delimiter
    …recepti.hr&label=Hrvatski%20web%20-%20Recepti.hr&s=1">Hrvatski recepti</a></li>

    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 84, Column 135: reference to external entity in attribute value
    …recepti.hr&label=Hrvatski%20web%20-%20Recepti.hr&s=1">Hrvatski recepti</a></li>

    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 84, Column 135: reference to entity "s" for which no system identifier could be generated
    …recepti.hr&label=Hrvatski%20web%20-%20Recepti.hr&s=1">Hrvatski recepti</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 88, Column 96: reference not terminated by REFC delimiter
    …/jump2.php?url=www.automobili.hr&label=Hrvatski%20web%20-%20Auti&s=1">Auti</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 88, Column 96: reference to external entity in attribute value
    …/jump2.php?url=www.automobili.hr&label=Hrvatski%20web%20-%20Auti&s=1">Auti</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 88, Column 96: reference to entity "label" for which no system identifier could be generated
    …/jump2.php?url=www.automobili.hr&label=Hrvatski%20web%20-%20Auti&s=1">Auti</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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 88, Column 124: reference not terminated by REFC delimiter
    …p2.php?url=www.automobili.hr&label=Hrvatski%20web%20-%20Auti&s=1">Auti</a></li>

    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 88, Column 124: reference to external entity in attribute value
    …p2.php?url=www.automobili.hr&label=Hrvatski%20web%20-%20Auti&s=1">Auti</a></li>

    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 88, Column 124: reference to entity "s" for which no system identifier could be generated
    …p2.php?url=www.automobili.hr&label=Hrvatski%20web%20-%20Auti&s=1">Auti</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 90, Column 85: reference not terminated by REFC delimiter
    …r.hr/jump2.php?url=www.1klik.hr/&label=Hrvatski%20web%20-%201klik.net&s=1">1Kl…

    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 90, Column 85: reference to external entity in attribute value
    …r.hr/jump2.php?url=www.1klik.hr/&label=Hrvatski%20web%20-%201klik.net&s=1">1Kl…

    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 90, Column 85: reference to entity "label" for which no system identifier could be generated
    …r.hr/jump2.php?url=www.1klik.hr/&label=Hrvatski%20web%20-%201klik.net&s=1">1Kl…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 90, Column 118: reference not terminated by REFC delimiter
    …www.1klik.hr/&label=Hrvatski%20web%20-%201klik.net&s=1">1Klik do svega</a></li>

    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 90, Column 118: reference to external entity in attribute value
    …www.1klik.hr/&label=Hrvatski%20web%20-%201klik.net&s=1">1Klik do svega</a></li>

    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 90, Column 118: reference to entity "s" for which no system identifier could be generated
    …www.1klik.hr/&label=Hrvatski%20web%20-%201klik.net&s=1">1Klik do svega</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 92, Column 106: reference not terminated by REFC delimiter
    …tp://www.jelovnik.hr/?ref=17590/&label=Hrvatski%20web%20-%20Jelovnik.hr&s=1">J…

    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 92, Column 106: reference to external entity in attribute value
    …tp://www.jelovnik.hr/?ref=17590/&label=Hrvatski%20web%20-%20Jelovnik.hr&s=1">J…

    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 92, Column 106: reference to entity "label" for which no system identifier could be generated
    …tp://www.jelovnik.hr/?ref=17590/&label=Hrvatski%20web%20-%20Jelovnik.hr&s=1">J…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 92, Column 141: reference not terminated by REFC delimiter
    …hr/?ref=17590/&label=Hrvatski%20web%20-%20Jelovnik.hr&s=1">Jelovnik.hr</a></li>

    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 92, Column 141: reference to external entity in attribute value
    …hr/?ref=17590/&label=Hrvatski%20web%20-%20Jelovnik.hr&s=1">Jelovnik.hr</a></li>

    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 92, Column 141: reference to entity "s" for which no system identifier could be generated
    …hr/?ref=17590/&label=Hrvatski%20web%20-%20Jelovnik.hr&s=1">Jelovnik.hr</a></li>

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 98, Column 100: reference not terminated by REFC delimiter
    …r.hr/jump2.php?url=www.gmail.com&label=World Wide web - Gmail&s=1" onclick="pa…

    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 98, Column 100: reference to external entity in attribute value
    …r.hr/jump2.php?url=www.gmail.com&label=World Wide web - Gmail&s=1" onclick="pa…

    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 98, Column 100: reference to entity "label" for which no system identifier could be generated
    …r.hr/jump2.php?url=www.gmail.com&label=World Wide web - Gmail&s=1" onclick="pa…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 98, Column 125: reference not terminated by REFC delimiter
    …ail.com&label=World Wide web - Gmail&s=1" onclick="pageTracker._trackEvent('Ou…

    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 98, Column 125: reference to external entity in attribute value
    …ail.com&label=World Wide web - Gmail&s=1" onclick="pageTracker._trackEvent('Ou…

    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 98, Column 125: reference to entity "s" for which no system identifier could be generated
    …ail.com&label=World Wide web - Gmail&s=1" onclick="pageTracker._trackEvent('Ou…

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 100, Column 102: reference not terminated by REFC delimiter
    …hr/jump2.php?url=www.youtube.com&label=World Wide web - YouTube&s=1" onclick="…

    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 100, Column 102: reference to external entity in attribute value
    …hr/jump2.php?url=www.youtube.com&label=World Wide web - YouTube&s=1" onclick="…

    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 100, Column 102: reference to entity "label" for which no system identifier could be generated
    …hr/jump2.php?url=www.youtube.com&label=World Wide web - YouTube&s=1" onclick="…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 100, Column 129: reference not terminated by REFC delimiter
    …e.com&label=World Wide web - YouTube&s=1" onclick="pageTracker._trackEvent('Ou…

    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 100, Column 129: reference to external entity in attribute value
    …e.com&label=World Wide web - YouTube&s=1" onclick="pageTracker._trackEvent('Ou…

    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 100, Column 129: reference to entity "s" for which no system identifier could be generated
    …e.com&label=World Wide web - YouTube&s=1" onclick="pageTracker._trackEvent('Ou…

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 102, Column 102: reference not terminated by REFC delimiter
    …hr/jump2.php?url=www.twitter.com&label=World Wide web - Twitter&s=1" onclick="…

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

  • Warning Line 102, Column 102: reference to external entity in attribute value
    …hr/jump2.php?url=www.twitter.com&label=World Wide web - Twitter&s=1" onclick="…

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

  • Error Line 102, Column 102: reference to entity "label" for which no system identifier could be generated
    …hr/jump2.php?url=www.twitter.com&label=World Wide web - Twitter&s=1" onclick="…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 102, Column 129: reference not terminated by REFC delimiter
    …r.com&label=World Wide web - Twitter&s=1" onclick="pageTracker._trackEvent('Ou…

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

  • Warning Line 102, Column 129: reference to external entity in attribute value
    …r.com&label=World Wide web - Twitter&s=1" onclick="pageTracker._trackEvent('Ou…

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

  • Error Line 102, Column 129: reference to entity "s" for which no system identifier could be generated
    …r.com&label=World Wide web - Twitter&s=1" onclick="pageTracker._trackEvent('Ou…

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Warning Line 104, Column 103: reference not terminated by REFC delimiter
    …r/jump2.php?url=www.facebook.com&label=World Wide web - Facebook&s=1" onclick=…

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

  • Warning Line 104, Column 103: reference to external entity in attribute value
    …r/jump2.php?url=www.facebook.com&label=World Wide web - Facebook&s=1" onclick=…

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

  • Error Line 104, Column 103: reference to entity "label" for which no system identifier could be generated
    …r/jump2.php?url=www.facebook.com&label=World Wide web - Facebook&s=1" onclick=…

    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 40, Column 79: entity was defined here
    …monitor.hr/jump2.php?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1…
  • Warning Line 104, Column 131: reference not terminated by REFC delimiter
    ….com&label=World Wide web - Facebook&s=1" onclick="pageTracker._trackEvent('Ou…

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

  • Warning Line 104, Column 131: reference to external entity in attribute value
    ….com&label=World Wide web - Facebook&s=1" onclick="pageTracker._trackEvent('Ou…

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

  • Error Line 104, Column 131: reference to entity "s" for which no system identifier could be generated
    ….com&label=World Wide web - Facebook&s=1" onclick="pageTracker._trackEvent('Ou…

    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 40, Column 115: entity was defined here
    …hp?url=www.forum.hr/&label=Hrvatski%20web%20-%20forum.hr&s=1">Forum.hr</a></li>
  • Error Line 106, Column 1014: there is no attribute "info"
    …="hr" /></form><div class="news" info="226565"><div class="flash"><img src="ht…

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

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

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

  • Warning Line 106, Column 2399: cannot generate system identifier for general entity "utm_content"
    …2dgxwoZBLRMD9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Six…

    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 106, Column 2399: general entity "utm_content" not defined and no default entity
    …2dgxwoZBLRMD9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Six…

    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 106, Column 2410: reference not terminated by REFC delimiter
    …D9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Six" target="_…

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

  • Warning Line 106, Column 2410: reference to external entity in attribute value
    …D9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Six" target="_…

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

  • Error Line 106, Column 2410: reference to entity "utm_content" for which no system identifier could be generated
    …D9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Six" target="_…

    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 106, Column 2398: entity was defined here
    …_2dgxwoZBLRMD9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Si…
  • Warning Line 106, Column 3975: reference not terminated by REFC delimiter
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Warning Line 106, Column 3975: reference to external entity in attribute value
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Error Line 106, Column 3975: reference to entity "a_bid" for which no system identifier could be generated
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 106, Column 3985: cannot generate system identifier for general entity "utm_source"
    …?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&ut…

    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 106, Column 3985: general entity "utm_source" not defined and no default entity
    …?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&ut…

    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 106, Column 3995: reference not terminated by REFC delimiter
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Warning Line 106, Column 3995: reference to external entity in attribute value
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Error Line 106, Column 3995: reference to entity "utm_source" for which no system identifier could be generated
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 106, Column 4006: cannot generate system identifier for general entity "utm_medium"
    …r&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&…

    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 106, Column 4006: general entity "utm_medium" not defined and no default entity
    …r&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&…

    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 106, Column 4016: reference not terminated by REFC delimiter
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Warning Line 106, Column 4016: reference to external entity in attribute value
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Error Line 106, Column 4016: reference to entity "utm_medium" for which no system identifier could be generated
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 106, Column 4034: reference not terminated by REFC delimiter
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Warning Line 106, Column 4034: reference to external entity in attribute value
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Error Line 106, Column 4034: reference to entity "utm_content" for which no system identifier could be generated
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

    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 106, Column 2398: entity was defined here
    …_2dgxwoZBLRMD9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Si…
  • Warning Line 106, Column 4046: cannot generate system identifier for general entity "utm_campaign"
    …m_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank"…

    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 106, Column 4046: general entity "utm_campaign" not defined and no default entity
    …m_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank"…

    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 106, Column 4058: reference not terminated by REFC delimiter
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Warning Line 106, Column 4058: reference to external entity in attribute value
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Error Line 106, Column 4058: reference to entity "utm_campaign" for which no system identifier could be generated
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Warning Line 106, Column 4581: reference not terminated by REFC delimiter
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Warning Line 106, Column 4581: reference to external entity in attribute value
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Error Line 106, Column 4581: reference to entity "a_bid" for which no system identifier could be generated
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 106, Column 4601: reference not terminated by REFC delimiter
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Warning Line 106, Column 4601: reference to external entity in attribute value
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Error Line 106, Column 4601: reference to entity "utm_source" for which no system identifier could be generated
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 106, Column 4622: reference not terminated by REFC delimiter
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Warning Line 106, Column 4622: reference to external entity in attribute value
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Error Line 106, Column 4622: reference to entity "utm_medium" for which no system identifier could be generated
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 106, Column 4640: reference not terminated by REFC delimiter
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Warning Line 106, Column 4640: reference to external entity in attribute value
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Error Line 106, Column 4640: reference to entity "utm_content" for which no system identifier could be generated
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

    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 106, Column 2398: entity was defined here
    …_2dgxwoZBLRMD9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Si…
  • Warning Line 106, Column 4664: reference not terminated by REFC delimiter
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Warning Line 106, Column 4664: reference to external entity in attribute value
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Error Line 106, Column 4664: reference to entity "utm_campaign" for which no system identifier could be generated
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Warning Line 106, Column 4891: reference not terminated by REFC delimiter
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Warning Line 106, Column 4891: reference to external entity in attribute value
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Error Line 106, Column 4891: reference to entity "a_bid" for which no system identifier could be generated
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 106, Column 4911: reference not terminated by REFC delimiter
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Warning Line 106, Column 4911: reference to external entity in attribute value
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Error Line 106, Column 4911: reference to entity "utm_source" for which no system identifier could be generated
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 106, Column 4932: reference not terminated by REFC delimiter
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Warning Line 106, Column 4932: reference to external entity in attribute value
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Error Line 106, Column 4932: reference to entity "utm_medium" for which no system identifier could be generated
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 106, Column 4950: reference not terminated by REFC delimiter
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Warning Line 106, Column 4950: reference to external entity in attribute value
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Error Line 106, Column 4950: reference to entity "utm_content" for which no system identifier could be generated
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

    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 106, Column 2398: entity was defined here
    …_2dgxwoZBLRMD9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Si…
  • Warning Line 106, Column 4974: reference not terminated by REFC delimiter
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Warning Line 106, Column 4974: reference to external entity in attribute value
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Error Line 106, Column 4974: reference to entity "utm_campaign" for which no system identifier could be generated
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Error Line 106, Column 5331: there is no attribute "href"
    …ink" /></a></span></div><fb:like href="http://www.monitor.hr/vijesti/pet-tretm…

    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 106, Column 5436: there is no attribute "send"
    …urom-uski-za-samo-199kn/226546/" send="false" layout="button_count" width="130…

    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 106, Column 5451: there is no attribute "layout"
    …mo-199kn/226546/" send="false" layout="button_count" width="130" show_faces="f…

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

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

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

  • Error Line 106, Column 5472: there is no attribute "width"
    …d="false" layout="button_count" width="130" show_faces="false"></fb:like><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 106, Column 5489: there is no attribute "show_faces"
    …"button_count" width="130" show_faces="false"></fb:like><div class="categories…

    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 106, Column 5496: element "fb:like" undefined
    …_count" width="130" show_faces="false"></fb:like><div class="categories"><a hr…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 107, Column 2095: cannot generate system identifier for general entity "tx_ttnews"
    …ww.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a…

    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 107, Column 2095: general entity "tx_ttnews" not defined and no default entity
    …ww.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a…

    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 107, Column 2104: reference not terminated by REFC delimiter
    …/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" t…

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

  • Warning Line 107, Column 2104: reference to external entity in attribute value
    …/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" t…

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

  • Error Line 107, Column 2104: reference to entity "tx_ttnews" for which no system identifier could be generated
    …/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" t…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 107, Column 2125: cannot generate system identifier for general entity "cHash"
    …-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="n…

    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 107, Column 2125: general entity "cHash" not defined and no default entity
    …-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="n…

    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 107, Column 2130: reference not terminated by REFC delimiter
    …ak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="nofoll…

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

  • Warning Line 107, Column 2130: reference to external entity in attribute value
    …ak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="nofoll…

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

  • Error Line 107, Column 2130: reference to entity "cHash" for which no system identifier could be generated
    …ak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="nofoll…

    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 107, Column 2124: entity was defined here
    …i-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="…
  • Warning Line 107, Column 3029: reference not terminated by REFC delimiter
    …-od-119kn-4293_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Warning Line 107, Column 3029: reference to external entity in attribute value
    …-od-119kn-4293_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Error Line 107, Column 3029: reference to entity "a_bid" for which no system identifier could be generated
    …-od-119kn-4293_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 107, Column 3049: reference not terminated by REFC delimiter
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Warning Line 107, Column 3049: reference to external entity in attribute value
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Error Line 107, Column 3049: reference to entity "utm_source" for which no system identifier could be generated
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 107, Column 3070: reference not terminated by REFC delimiter
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Warning Line 107, Column 3070: reference to external entity in attribute value
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Error Line 107, Column 3070: reference to entity "utm_medium" for which no system identifier could be generated
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 107, Column 3091: reference not terminated by REFC delimiter
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Warning Line 107, Column 3091: reference to external entity in attribute value
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Error Line 107, Column 3091: reference to entity "utm_campaign" for which no system identifier could be generated
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Warning Line 108, Column 4041: reference not terminated by REFC delimiter
    …/index.php?id=vijesti-clanak&tx_ttnews[tt_news]=199642&tx_ttnews[backPid]=850&…

    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 108, Column 4041: reference to external entity in attribute value
    …/index.php?id=vijesti-clanak&tx_ttnews[tt_news]=199642&tx_ttnews[backPid]=850&…

    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 108, Column 4041: reference to entity "tx_ttnews" for which no system identifier could be generated
    …/index.php?id=vijesti-clanak&tx_ttnews[tt_news]=199642&tx_ttnews[backPid]=850&…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 108, Column 4067: reference not terminated by REFC delimiter
    …ak&tx_ttnews[tt_news]=199642&tx_ttnews[backPid]=850&cHash=c46ea3727f" target="…

    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 108, Column 4067: reference to external entity in attribute value
    …ak&tx_ttnews[tt_news]=199642&tx_ttnews[backPid]=850&cHash=c46ea3727f" target="…

    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 108, Column 4067: reference to entity "tx_ttnews" for which no system identifier could be generated
    …ak&tx_ttnews[tt_news]=199642&tx_ttnews[backPid]=850&cHash=c46ea3727f" target="…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 108, Column 4086: reference not terminated by REFC delimiter
    …s]=199642&tx_ttnews[backPid]=850&cHash=c46ea3727f" target="_blank" rel="nofoll…

    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 108, Column 4086: reference to external entity in attribute value
    …s]=199642&tx_ttnews[backPid]=850&cHash=c46ea3727f" target="_blank" rel="nofoll…

    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 108, Column 4086: reference to entity "cHash" for which no system identifier could be generated
    …s]=199642&tx_ttnews[backPid]=850&cHash=c46ea3727f" target="_blank" rel="nofoll…

    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 107, Column 2124: entity was defined here
    …i-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="…
  • Warning Line 108, Column 4996: cannot generate system identifier for general entity "mreza"
    …f="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" …

    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 108, Column 4996: general entity "mreza" not defined and no default entity
    …f="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" …

    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 108, Column 5001: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" targe…

    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 108, Column 5001: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" targe…

    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 108, Column 5001: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" targe…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 108, Column 5004: cannot generate system identifier for general entity "datum"
    …//raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="…

    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 108, Column 5004: general entity "datum" not defined and no default entity
    …//raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="…

    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 108, Column 5009: reference not terminated by REFC delimiter
    …pored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blan…

    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 108, Column 5009: reference to external entity in attribute value
    …pored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blan…

    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 108, Column 5009: reference to entity "datum" for which no system identifier could be generated
    …pored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blan…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Warning Line 108, Column 5021: cannot generate system identifier for general entity "najava"
    …/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nofo…

    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 108, Column 5021: general entity "najava" not defined and no default entity
    …/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nofo…

    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 108, Column 5027: reference not terminated by REFC delimiter
    …ored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nofollow">…

    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 108, Column 5027: reference to external entity in attribute value
    …ored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nofollow">…

    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 108, Column 5027: reference to entity "najava" for which no system identifier could be generated
    …ored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nofollow">…

    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 108, Column 5020: entity was defined here
    …r/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nof…
  • Warning Line 109, Column 153: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=66629" target…

    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 109, Column 153: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=66629" target…

    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 109, Column 153: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=66629" target…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 109, Column 161: reference not terminated by REFC delimiter
    …pored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=66629" target="_blank…

    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 109, Column 161: reference to external entity in attribute value
    …pored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=66629" target="_blank…

    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 109, Column 161: reference to entity "datum" for which no system identifier could be generated
    …pored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=66629" target="_blank…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Warning Line 109, Column 179: reference not terminated by REFC delimiter
    …ored=1&mreza=3&datum=2013-01-30&najava=66629" target="_blank" rel="nofollow">H…

    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 109, Column 179: reference to external entity in attribute value
    …ored=1&mreza=3&datum=2013-01-30&najava=66629" target="_blank" rel="nofollow">H…

    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 109, Column 179: reference to entity "najava" for which no system identifier could be generated
    …ored=1&mreza=3&datum=2013-01-30&najava=66629" target="_blank" rel="nofollow">H…

    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 108, Column 5020: entity was defined here
    …r/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nof…
  • Warning Line 110, Column 168: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106632" targe…

    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 110, Column 168: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106632" targe…

    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 110, Column 168: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106632" targe…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 110, Column 176: reference not terminated by REFC delimiter
    …pored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106632" target="_blan…

    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 110, Column 176: reference to external entity in attribute value
    …pored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106632" target="_blan…

    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 110, Column 176: reference to entity "datum" for which no system identifier could be generated
    …pored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106632" target="_blan…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Warning Line 110, Column 194: reference not terminated by REFC delimiter
    …ored=1&mreza=4&datum=2013-01-30&najava=106632" target="_blank" rel="nofollow">…

    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 110, Column 194: reference to external entity in attribute value
    …ored=1&mreza=4&datum=2013-01-30&najava=106632" target="_blank" rel="nofollow">…

    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 110, Column 194: reference to entity "najava" for which no system identifier could be generated
    …ored=1&mreza=4&datum=2013-01-30&najava=106632" target="_blank" rel="nofollow">…

    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 108, Column 5020: entity was defined here
    …r/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nof…
  • Warning Line 111, Column 80: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30&najava=107021" targ…

    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 111, Column 80: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30&najava=107021" targ…

    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 111, Column 80: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30&najava=107021" targ…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 111, Column 89: reference not terminated by REFC delimiter
    …ored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30&najava=107021" target="_blan…

    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 111, Column 89: reference to external entity in attribute value
    …ored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30&najava=107021" target="_blan…

    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 111, Column 89: reference to entity "datum" for which no system identifier could be generated
    …ored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30&najava=107021" target="_blan…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Warning Line 111, Column 107: reference not terminated by REFC delimiter
    …red=1&mreza=40&datum=2013-01-30&najava=107021" target="_blank" rel="nofollow">…

    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 111, Column 107: reference to external entity in attribute value
    …red=1&mreza=40&datum=2013-01-30&najava=107021" target="_blank" rel="nofollow">…

    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 111, Column 107: reference to entity "najava" for which no system identifier could be generated
    …red=1&mreza=40&datum=2013-01-30&najava=107021" target="_blank" rel="nofollow">…

    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 108, Column 5020: entity was defined here
    …r/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nof…
  • Warning Line 112, Column 155: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=106578" targe…

    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 112, Column 155: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=106578" targe…

    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 112, Column 155: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=106578" targe…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 112, Column 163: reference not terminated by REFC delimiter
    …pored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=106578" target="_blan…

    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 112, Column 163: reference to external entity in attribute value
    …pored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=106578" target="_blan…

    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 112, Column 163: reference to entity "datum" for which no system identifier could be generated
    …pored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30&najava=106578" target="_blan…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Warning Line 112, Column 181: reference not terminated by REFC delimiter
    …ored=1&mreza=3&datum=2013-01-30&najava=106578" target="_blank" rel="nofollow">…

    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 112, Column 181: reference to external entity in attribute value
    …ored=1&mreza=3&datum=2013-01-30&najava=106578" target="_blank" rel="nofollow">…

    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 112, Column 181: reference to entity "najava" for which no system identifier could be generated
    …ored=1&mreza=3&datum=2013-01-30&najava=106578" target="_blank" rel="nofollow">…

    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 108, Column 5020: entity was defined here
    …r/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nof…
  • Warning Line 113, Column 159: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106973" targe…

    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 113, Column 159: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106973" targe…

    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 113, Column 159: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106973" targe…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 113, Column 167: reference not terminated by REFC delimiter
    …pored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106973" target="_blan…

    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 113, Column 167: reference to external entity in attribute value
    …pored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106973" target="_blan…

    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 113, Column 167: reference to entity "datum" for which no system identifier could be generated
    …pored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30&najava=106973" target="_blan…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Warning Line 113, Column 185: reference not terminated by REFC delimiter
    …ored=1&mreza=4&datum=2013-01-30&najava=106973" target="_blank" rel="nofollow">…

    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 113, Column 185: reference to external entity in attribute value
    …ored=1&mreza=4&datum=2013-01-30&najava=106973" target="_blank" rel="nofollow">…

    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 113, Column 185: reference to entity "najava" for which no system identifier could be generated
    …ored=1&mreza=4&datum=2013-01-30&najava=106973" target="_blank" rel="nofollow">…

    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 108, Column 5020: entity was defined here
    …r/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nof…
  • Warning Line 114, Column 92: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=107231" targe…

    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 114, Column 92: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=107231" targe…

    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 114, Column 92: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=107231" targe…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 114, Column 100: reference not terminated by REFC delimiter
    …pored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=107231" target="_blan…

    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 114, Column 100: reference to external entity in attribute value
    …pored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=107231" target="_blan…

    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 114, Column 100: reference to entity "datum" for which no system identifier could be generated
    …pored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=107231" target="_blan…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Warning Line 114, Column 118: reference not terminated by REFC delimiter
    …ored=1&mreza=2&datum=2013-01-30&najava=107231" target="_blank" rel="nofollow">…

    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 114, Column 118: reference to external entity in attribute value
    …ored=1&mreza=2&datum=2013-01-30&najava=107231" target="_blank" rel="nofollow">…

    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 114, Column 118: reference to entity "najava" for which no system identifier could be generated
    …ored=1&mreza=2&datum=2013-01-30&najava=107231" target="_blank" rel="nofollow">…

    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 108, Column 5020: entity was defined here
    …r/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target="_blank" rel="nof…
  • Warning Line 117, Column 70: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30" target="_blank" rel…

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

  • Warning Line 117, Column 70: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30" target="_blank" rel…

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

  • Error Line 117, Column 70: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30" target="_blank" rel…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 117, Column 78: reference not terminated by REFC delimiter
    …pored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30" target="_blank" rel="nofoll…

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

  • Warning Line 117, Column 78: reference to external entity in attribute value
    …pored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30" target="_blank" rel="nofoll…

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

  • Error Line 117, Column 78: reference to entity "datum" for which no system identifier could be generated
    …pored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30" target="_blank" rel="nofoll…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Warning Line 117, Column 181: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30" target="_blank" rel…

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

  • Warning Line 117, Column 181: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30" target="_blank" rel…

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

  • Error Line 117, Column 181: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30" target="_blank" rel…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 117, Column 189: reference not terminated by REFC delimiter
    …pored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30" target="_blank" rel="nofoll…

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

  • Warning Line 117, Column 189: reference to external entity in attribute value
    …pored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30" target="_blank" rel="nofoll…

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

  • Error Line 117, Column 189: reference to entity "datum" for which no system identifier could be generated
    …pored.hrt.hr/?raspored=1&mreza=3&datum=2013-01-30" target="_blank" rel="nofoll…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Warning Line 117, Column 292: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30" target="_blank" rel…

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

  • Warning Line 117, Column 292: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30" target="_blank" rel…

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

  • Error Line 117, Column 292: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30" target="_blank" rel…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 117, Column 300: reference not terminated by REFC delimiter
    …pored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30" target="_blank" rel="nofoll…

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

  • Warning Line 117, Column 300: reference to external entity in attribute value
    …pored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30" target="_blank" rel="nofoll…

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

  • Error Line 117, Column 300: reference to entity "datum" for which no system identifier could be generated
    …pored.hrt.hr/?raspored=1&mreza=4&datum=2013-01-30" target="_blank" rel="nofoll…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Warning Line 117, Column 403: reference not terminated by REFC delimiter
    …tp://raspored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30" target="_blank" re…

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

  • Warning Line 117, Column 403: reference to external entity in attribute value
    …tp://raspored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30" target="_blank" re…

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

  • Error Line 117, Column 403: reference to entity "mreza" for which no system identifier could be generated
    …tp://raspored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30" target="_blank" re…

    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 108, Column 4995: entity was defined here
    …ef="http://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648"…
  • Warning Line 117, Column 412: reference not terminated by REFC delimiter
    …ored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30" target="_blank" rel="nofoll…

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

  • Warning Line 117, Column 412: reference to external entity in attribute value
    …ored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30" target="_blank" rel="nofoll…

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

  • Error Line 117, Column 412: reference to entity "datum" for which no system identifier could be generated
    …ored.hrt.hr/?raspored=1&mreza=40&datum=2013-01-30" target="_blank" rel="nofoll…

    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 108, Column 5003: entity was defined here
    …://raspored.hrt.hr/?raspored=1&mreza=2&datum=2013-01-30&najava=106648" target=…
  • Error Line 117, Column 1069: element "fb:like" undefined
    …_count" width="130" show_faces="false"></fb:like></div></div><div class="news"…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 133, Column 91: cannot generate system identifier for general entity "cb"
    …tor.hr/www/delivery/ck.php?n=a2ce82a4&cb=INSERT_RANDOM_NUMBER_HERE' target='_b…

    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 133, Column 91: general entity "cb" not defined and no default entity
    …tor.hr/www/delivery/ck.php?n=a2ce82a4&cb=INSERT_RANDOM_NUMBER_HERE' target='_b…

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

  • Warning Line 133, Column 93: reference not terminated by REFC delimiter
    …r.hr/www/delivery/ck.php?n=a2ce82a4&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

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

  • Warning Line 133, Column 93: reference to external entity in attribute value
    …r.hr/www/delivery/ck.php?n=a2ce82a4&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

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

  • Error Line 133, Column 93: reference to entity "cb" for which no system identifier could be generated
    …r.hr/www/delivery/ck.php?n=a2ce82a4&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 133, Column 90: entity was defined here
    …itor.hr/www/delivery/ck.php?n=a2ce82a4&cb=INSERT_RANDOM_NUMBER_HERE' target='_…
  • Warning Line 133, Column 206: cannot generate system identifier for general entity "n"
    …r/www/delivery/avw.php?campaignid=463&n=a2ce82a4' border='0' alt='' /></a></no…

    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 133, Column 206: general entity "n" not defined and no default entity
    …r/www/delivery/avw.php?campaignid=463&n=a2ce82a4' border='0' alt='' /></a></no…

    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 133, Column 207: reference not terminated by REFC delimiter
    …/www/delivery/avw.php?campaignid=463&n=a2ce82a4' border='0' alt='' /></a></nos…

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

  • Warning Line 133, Column 207: reference to external entity in attribute value
    …/www/delivery/avw.php?campaignid=463&n=a2ce82a4' border='0' alt='' /></a></nos…

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

  • Error Line 133, Column 207: reference to entity "n" for which no system identifier could be generated
    …/www/delivery/avw.php?campaignid=463&n=a2ce82a4' border='0' alt='' /></a></nos…

    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 133, Column 205: entity was defined here
    …hr/www/delivery/avw.php?campaignid=463&n=a2ce82a4' border='0' alt='' /></a></n…
  • Warning Line 133, Column 3356: reference not terminated by REFC delimiter
    …/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199641&cHash=5246f92dcb" t…

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

  • Warning Line 133, Column 3356: reference to external entity in attribute value
    …/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199641&cHash=5246f92dcb" t…

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

  • Error Line 133, Column 3356: reference to entity "tx_ttnews" for which no system identifier could be generated
    …/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199641&cHash=5246f92dcb" t…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 133, Column 3382: reference not terminated by REFC delimiter
    …ak&tx_ttnews%5Btt_news%5D=199641&cHash=5246f92dcb" target="_blank" rel="nofoll…

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

  • Warning Line 133, Column 3382: reference to external entity in attribute value
    …ak&tx_ttnews%5Btt_news%5D=199641&cHash=5246f92dcb" target="_blank" rel="nofoll…

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

  • Error Line 133, Column 3382: reference to entity "cHash" for which no system identifier could be generated
    …ak&tx_ttnews%5Btt_news%5D=199641&cHash=5246f92dcb" target="_blank" rel="nofoll…

    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 107, Column 2124: entity was defined here
    …i-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="…
  • Warning Line 133, Column 4185: reference not terminated by REFC delimiter
    …/index.php?id=vijesti-clanak&tx_ttnews[tt_news]=199498&tx_ttnews[backPid]=850&…

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

  • Warning Line 133, Column 4185: reference to external entity in attribute value
    …/index.php?id=vijesti-clanak&tx_ttnews[tt_news]=199498&tx_ttnews[backPid]=850&…

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

  • Error Line 133, Column 4185: reference to entity "tx_ttnews" for which no system identifier could be generated
    …/index.php?id=vijesti-clanak&tx_ttnews[tt_news]=199498&tx_ttnews[backPid]=850&…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 133, Column 4211: reference not terminated by REFC delimiter
    …ak&tx_ttnews[tt_news]=199498&tx_ttnews[backPid]=850&cHash=8c7b964a59" target="…

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

  • Warning Line 133, Column 4211: reference to external entity in attribute value
    …ak&tx_ttnews[tt_news]=199498&tx_ttnews[backPid]=850&cHash=8c7b964a59" target="…

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

  • Error Line 133, Column 4211: reference to entity "tx_ttnews" for which no system identifier could be generated
    …ak&tx_ttnews[tt_news]=199498&tx_ttnews[backPid]=850&cHash=8c7b964a59" target="…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 133, Column 4230: reference not terminated by REFC delimiter
    …s]=199498&tx_ttnews[backPid]=850&cHash=8c7b964a59" target="_blank" rel="nofoll…

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

  • Warning Line 133, Column 4230: reference to external entity in attribute value
    …s]=199498&tx_ttnews[backPid]=850&cHash=8c7b964a59" target="_blank" rel="nofoll…

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

  • Error Line 133, Column 4230: reference to entity "cHash" for which no system identifier could be generated
    …s]=199498&tx_ttnews[backPid]=850&cHash=8c7b964a59" target="_blank" rel="nofoll…

    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 107, Column 2124: entity was defined here
    …i-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="…
  • Warning Line 133, Column 9289: reference not terminated by REFC delimiter
    …/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199645&cHash=4141217372" t…

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

  • Warning Line 133, Column 9289: reference to external entity in attribute value
    …/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199645&cHash=4141217372" t…

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

  • Error Line 133, Column 9289: reference to entity "tx_ttnews" for which no system identifier could be generated
    …/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199645&cHash=4141217372" t…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 133, Column 9315: reference not terminated by REFC delimiter
    …ak&tx_ttnews%5Btt_news%5D=199645&cHash=4141217372" target="_blank" rel="nofoll…

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

  • Warning Line 133, Column 9315: reference to external entity in attribute value
    …ak&tx_ttnews%5Btt_news%5D=199645&cHash=4141217372" target="_blank" rel="nofoll…

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

  • Error Line 133, Column 9315: reference to entity "cHash" for which no system identifier could be generated
    …ak&tx_ttnews%5Btt_news%5D=199645&cHash=4141217372" target="_blank" rel="nofoll…

    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 107, Column 2124: entity was defined here
    …i-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="…
  • Warning Line 133, Column 10776: reference not terminated by REFC delimiter
    …o-2-400kn-4235_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Warning Line 133, Column 10776: reference to external entity in attribute value
    …o-2-400kn-4235_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Error Line 133, Column 10776: reference to entity "a_bid" for which no system identifier could be generated
    …o-2-400kn-4235_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 133, Column 10796: reference not terminated by REFC delimiter
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Warning Line 133, Column 10796: reference to external entity in attribute value
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Error Line 133, Column 10796: reference to entity "utm_source" for which no system identifier could be generated
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 133, Column 10817: reference not terminated by REFC delimiter
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Warning Line 133, Column 10817: reference to external entity in attribute value
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Error Line 133, Column 10817: reference to entity "utm_medium" for which no system identifier could be generated
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 133, Column 10838: reference not terminated by REFC delimiter
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Warning Line 133, Column 10838: reference to external entity in attribute value
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Error Line 133, Column 10838: reference to entity "utm_campaign" for which no system identifier could be generated
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Warning Line 133, Column 11103: reference not terminated by REFC delimiter
    …o-1-000kn-4275_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Warning Line 133, Column 11103: reference to external entity in attribute value
    …o-1-000kn-4275_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Error Line 133, Column 11103: reference to entity "a_bid" for which no system identifier could be generated
    …o-1-000kn-4275_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 133, Column 11123: reference not terminated by REFC delimiter
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Warning Line 133, Column 11123: reference to external entity in attribute value
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Error Line 133, Column 11123: reference to entity "utm_source" for which no system identifier could be generated
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 133, Column 11144: reference not terminated by REFC delimiter
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Warning Line 133, Column 11144: reference to external entity in attribute value
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Error Line 133, Column 11144: reference to entity "utm_medium" for which no system identifier could be generated
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 133, Column 11165: reference not terminated by REFC delimiter
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Warning Line 133, Column 11165: reference to external entity in attribute value
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Error Line 133, Column 11165: reference to entity "utm_campaign" for which no system identifier could be generated
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Warning Line 133, Column 11451: reference not terminated by REFC delimiter
    …3-mjeseca-4048_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Warning Line 133, Column 11451: reference to external entity in attribute value
    …3-mjeseca-4048_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Error Line 133, Column 11451: reference to entity "a_bid" for which no system identifier could be generated
    …3-mjeseca-4048_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 133, Column 11471: reference not terminated by REFC delimiter
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Warning Line 133, Column 11471: reference to external entity in attribute value
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Error Line 133, Column 11471: reference to entity "utm_source" for which no system identifier could be generated
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 133, Column 11492: reference not terminated by REFC delimiter
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Warning Line 133, Column 11492: reference to external entity in attribute value
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Error Line 133, Column 11492: reference to entity "utm_medium" for which no system identifier could be generated
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 133, Column 11513: reference not terminated by REFC delimiter
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Warning Line 133, Column 11513: reference to external entity in attribute value
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Error Line 133, Column 11513: reference to entity "utm_campaign" for which no system identifier could be generated
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Warning Line 133, Column 11816: reference not terminated by REFC delimiter
    …tru-Aurea-4298_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Warning Line 133, Column 11816: reference to external entity in attribute value
    …tru-Aurea-4298_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Error Line 133, Column 11816: reference to entity "a_bid" for which no system identifier could be generated
    …tru-Aurea-4298_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 133, Column 11836: reference not terminated by REFC delimiter
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Warning Line 133, Column 11836: reference to external entity in attribute value
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Error Line 133, Column 11836: reference to entity "utm_source" for which no system identifier could be generated
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 133, Column 11857: reference not terminated by REFC delimiter
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Warning Line 133, Column 11857: reference to external entity in attribute value
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Error Line 133, Column 11857: reference to entity "utm_medium" for which no system identifier could be generated
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 133, Column 11878: reference not terminated by REFC delimiter
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Warning Line 133, Column 11878: reference to external entity in attribute value
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Error Line 133, Column 11878: reference to entity "utm_campaign" for which no system identifier could be generated
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Warning Line 133, Column 12041: reference not terminated by REFC delimiter
    …a.hr/mrsavljenje?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Warning Line 133, Column 12041: reference to external entity in attribute value
    …a.hr/mrsavljenje?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Error Line 133, Column 12041: reference to entity "a_bid" for which no system identifier could be generated
    …a.hr/mrsavljenje?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 133, Column 12061: reference not terminated by REFC delimiter
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Warning Line 133, Column 12061: reference to external entity in attribute value
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Error Line 133, Column 12061: reference to entity "utm_source" for which no system identifier could be generated
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 133, Column 12082: reference not terminated by REFC delimiter
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Warning Line 133, Column 12082: reference to external entity in attribute value
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Error Line 133, Column 12082: reference to entity "utm_medium" for which no system identifier could be generated
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 133, Column 12103: reference not terminated by REFC delimiter
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Warning Line 133, Column 12103: reference to external entity in attribute value
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

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

  • Error Line 133, Column 12103: reference to entity "utm_campaign" for which no system identifier could be generated
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" rel="nofoll…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Error Line 133, Column 12633: element "fb:like" undefined
    …_count" width="130" show_faces="false"></fb:like><div class="categories"><a hr…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 133, Column 34240: cannot generate system identifier for general entity "set"
    …ok.com/photo.php?fbid=587926914554180&set=a.260905783922963.82517.260895413924…

    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 133, Column 34240: general entity "set" not defined and no default entity
    …ok.com/photo.php?fbid=587926914554180&set=a.260905783922963.82517.260895413924…

    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 133, Column 34243: reference not terminated by REFC delimiter
    …com/photo.php?fbid=587926914554180&set=a.260905783922963.82517.260895413924000…

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

  • Warning Line 133, Column 34243: reference to external entity in attribute value
    …com/photo.php?fbid=587926914554180&set=a.260905783922963.82517.260895413924000…

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

  • Error Line 133, Column 34243: reference to entity "set" for which no system identifier could be generated
    …com/photo.php?fbid=587926914554180&set=a.260905783922963.82517.260895413924000…

    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 133, Column 34239: entity was defined here
    …ook.com/photo.php?fbid=587926914554180&set=a.260905783922963.82517.26089541392…
  • Warning Line 133, Column 34284: cannot generate system identifier for general entity "type"
    …260905783922963.82517.260895413924000&type=1" target="_blank" rel="nofollow">F…

    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 133, Column 34284: general entity "type" not defined and no default entity
    …260905783922963.82517.260895413924000&type=1" target="_blank" rel="nofollow">F…

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

  • Warning Line 133, Column 34288: reference not terminated by REFC delimiter
    …05783922963.82517.260895413924000&type=1" target="_blank" rel="nofollow">Faceb…

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

  • Warning Line 133, Column 34288: reference to external entity in attribute value
    …05783922963.82517.260895413924000&type=1" target="_blank" rel="nofollow">Faceb…

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

  • Error Line 133, Column 34288: reference to entity "type" for which no system identifier could be generated
    …05783922963.82517.260895413924000&type=1" target="_blank" rel="nofollow">Faceb…

    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 133, Column 34283: entity was defined here
    ….260905783922963.82517.260895413924000&type=1" target="_blank" rel="nofollow">…
  • Warning Line 133, Column 40522: reference not terminated by REFC delimiter
    …/index.php?id=vijesti-clanak&tx_ttnews[tt_news]=199540&tx_ttnews[backPid]=850&…

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

  • Warning Line 133, Column 40522: reference to external entity in attribute value
    …/index.php?id=vijesti-clanak&tx_ttnews[tt_news]=199540&tx_ttnews[backPid]=850&…

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

  • Error Line 133, Column 40522: reference to entity "tx_ttnews" for which no system identifier could be generated
    …/index.php?id=vijesti-clanak&tx_ttnews[tt_news]=199540&tx_ttnews[backPid]=850&…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 133, Column 40548: reference not terminated by REFC delimiter
    …ak&tx_ttnews[tt_news]=199540&tx_ttnews[backPid]=850&cHash=ac3953664d" target="…

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

  • Warning Line 133, Column 40548: reference to external entity in attribute value
    …ak&tx_ttnews[tt_news]=199540&tx_ttnews[backPid]=850&cHash=ac3953664d" target="…

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

  • Error Line 133, Column 40548: reference to entity "tx_ttnews" for which no system identifier could be generated
    …ak&tx_ttnews[tt_news]=199540&tx_ttnews[backPid]=850&cHash=ac3953664d" target="…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 133, Column 40567: reference not terminated by REFC delimiter
    …s]=199540&tx_ttnews[backPid]=850&cHash=ac3953664d" target="_blank" rel="nofoll…

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

  • Warning Line 133, Column 40567: reference to external entity in attribute value
    …s]=199540&tx_ttnews[backPid]=850&cHash=ac3953664d" target="_blank" rel="nofoll…

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

  • Error Line 133, Column 40567: reference to entity "cHash" for which no system identifier could be generated
    …s]=199540&tx_ttnews[backPid]=850&cHash=ac3953664d" target="_blank" rel="nofoll…

    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 107, Column 2124: entity was defined here
    …i-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="…
  • Error Line 133, Column 63229: there is no attribute "info"
    …tion"><a href="#" rel="nofollow" info="0" class="prev disabled" title="Natrag"…

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

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

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

  • Warning Line 149, Column 93: reference not terminated by REFC delimiter
    …r.hr/www/delivery/ck.php?n=a4dbb4ef&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

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

  • Warning Line 149, Column 93: reference to external entity in attribute value
    …r.hr/www/delivery/ck.php?n=a4dbb4ef&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

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

  • Error Line 149, Column 93: reference to entity "cb" for which no system identifier could be generated
    …r.hr/www/delivery/ck.php?n=a4dbb4ef&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 133, Column 90: entity was defined here
    …itor.hr/www/delivery/ck.php?n=a2ce82a4&cb=INSERT_RANDOM_NUMBER_HERE' target='_…
  • Warning Line 149, Column 207: reference not terminated by REFC delimiter
    …/www/delivery/avw.php?campaignid=449&n=a4dbb4ef' border='0' alt='' /></a></nos…

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

  • Warning Line 149, Column 207: reference to external entity in attribute value
    …/www/delivery/avw.php?campaignid=449&n=a4dbb4ef' border='0' alt='' /></a></nos…

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

  • Error Line 149, Column 207: reference to entity "n" for which no system identifier could be generated
    …/www/delivery/avw.php?campaignid=449&n=a4dbb4ef' border='0' alt='' /></a></nos…

    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 133, Column 205: entity was defined here
    …hr/www/delivery/avw.php?campaignid=463&n=a2ce82a4' border='0' alt='' /></a></n…
  • Warning Line 165, Column 93: reference not terminated by REFC delimiter
    …r.hr/www/delivery/ck.php?n=a6eb761e&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 165, Column 93: reference to external entity in attribute value
    …r.hr/www/delivery/ck.php?n=a6eb761e&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 165, Column 93: reference to entity "cb" for which no system identifier could be generated
    …r.hr/www/delivery/ck.php?n=a6eb761e&cb=INSERT_RANDOM_NUMBER_HERE' target='_bla…

    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 133, Column 90: entity was defined here
    …itor.hr/www/delivery/ck.php?n=a2ce82a4&cb=INSERT_RANDOM_NUMBER_HERE' target='_…
  • Warning Line 165, Column 207: reference not terminated by REFC delimiter
    …/www/delivery/avw.php?campaignid=509&n=a6eb761e' border='0' alt='' /></a></nos…

    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 165, Column 207: reference to external entity in attribute value
    …/www/delivery/avw.php?campaignid=509&n=a6eb761e' border='0' alt='' /></a></nos…

    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 165, Column 207: reference to entity "n" for which no system identifier could be generated
    …/www/delivery/avw.php?campaignid=509&n=a6eb761e' border='0' alt='' /></a></nos…

    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 133, Column 205: entity was defined here
    …hr/www/delivery/avw.php?campaignid=463&n=a2ce82a4' border='0' alt='' /></a></n…
  • Warning Line 166, Column 657: reference not terminated by REFC delimiter
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Warning Line 166, Column 657: reference to external entity in attribute value
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Error Line 166, Column 657: reference to entity "a_bid" for which no system identifier could be generated
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 166, Column 677: reference not terminated by REFC delimiter
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Warning Line 166, Column 677: reference to external entity in attribute value
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Error Line 166, Column 677: reference to entity "utm_source" for which no system identifier could be generated
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 166, Column 698: reference not terminated by REFC delimiter
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Warning Line 166, Column 698: reference to external entity in attribute value
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Error Line 166, Column 698: reference to entity "utm_medium" for which no system identifier could be generated
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 166, Column 716: reference not terminated by REFC delimiter
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Warning Line 166, Column 716: reference to external entity in attribute value
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Error Line 166, Column 716: reference to entity "utm_content" for which no system identifier could be generated
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

    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 106, Column 2398: entity was defined here
    …_2dgxwoZBLRMD9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Si…
  • Warning Line 166, Column 740: reference not terminated by REFC delimiter
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" info="22655…

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

  • Warning Line 166, Column 740: reference to external entity in attribute value
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" info="22655…

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

  • Error Line 166, Column 740: reference to entity "utm_campaign" for which no system identifier could be generated
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" info="22655…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Warning Line 166, Column 3725: cannot generate system identifier for general entity "mm"
    …92.net/info/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=6817…

    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 166, Column 3725: general entity "mm" not defined and no default entity
    …92.net/info/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=6817…

    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 166, Column 3727: reference not terminated by REFC delimiter
    ….net/info/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754…

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

  • Warning Line 166, Column 3727: reference to external entity in attribute value
    ….net/info/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754…

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

  • Error Line 166, Column 3727: reference to entity "mm" for which no system identifier could be generated
    ….net/info/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754…

    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 166, Column 3724: entity was defined here
    …b92.net/info/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681…
  • Warning Line 166, Column 3731: cannot generate system identifier for general entity "dd"
    …/info/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" ta…

    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 166, Column 3731: general entity "dd" not defined and no default entity
    …/info/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" ta…

    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 166, Column 3733: reference not terminated by REFC delimiter
    …nfo/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" targ…

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

  • Warning Line 166, Column 3733: reference to external entity in attribute value
    …nfo/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" targ…

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

  • Error Line 166, Column 3733: reference to entity "dd" for which no system identifier could be generated
    …nfo/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" targ…

    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 166, Column 3730: entity was defined here
    …t/info/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" t…
  • Warning Line 166, Column 3737: cannot generate system identifier for general entity "nav_category"
    …vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" target="…

    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 166, Column 3737: general entity "nav_category" not defined and no default entity
    …vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" target="…

    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 166, Column 3749: reference not terminated by REFC delimiter
    …php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" target="_blank" info…

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

  • Warning Line 166, Column 3749: reference to external entity in attribute value
    …php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" target="_blank" info…

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

  • Error Line 166, Column 3749: reference to entity "nav_category" for which no system identifier could be generated
    …php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" target="_blank" info…

    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 166, Column 3736: entity was defined here
    …/vesti/index.php?yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" target=…
  • Warning Line 166, Column 3754: cannot generate system identifier for general entity "nav_id"
    …yyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" target="_blank" info="226…

    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 166, Column 3754: general entity "nav_id" not defined and no default entity
    …yyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" target="_blank" info="226…

    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 166, Column 3760: reference not terminated by REFC delimiter
    …13&mm=01&dd=29&nav_category=167&nav_id=681754" target="_blank" info="226481" r…

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

  • Warning Line 166, Column 3760: reference to external entity in attribute value
    …13&mm=01&dd=29&nav_category=167&nav_id=681754" target="_blank" info="226481" r…

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

  • Error Line 166, Column 3760: reference to entity "nav_id" for which no system identifier could be generated
    …13&mm=01&dd=29&nav_category=167&nav_id=681754" target="_blank" info="226481" r…

    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 166, Column 3753: entity was defined here
    …yyyy=2013&mm=01&dd=29&nav_category=167&nav_id=681754" target="_blank" info="22…
  • Warning Line 166, Column 7355: reference not terminated by REFC delimiter
    …atija.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Warning Line 166, Column 7355: reference to external entity in attribute value
    …atija.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Error Line 166, Column 7355: reference to entity "a_bid" for which no system identifier could be generated
    …atija.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 166, Column 7375: reference not terminated by REFC delimiter
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Warning Line 166, Column 7375: reference to external entity in attribute value
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Error Line 166, Column 7375: reference to entity "utm_source" for which no system identifier could be generated
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 166, Column 7396: reference not terminated by REFC delimiter
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Warning Line 166, Column 7396: reference to external entity in attribute value
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Error Line 166, Column 7396: reference to entity "utm_medium" for which no system identifier could be generated
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 166, Column 7414: reference not terminated by REFC delimiter
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Warning Line 166, Column 7414: reference to external entity in attribute value
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Error Line 166, Column 7414: reference to entity "utm_content" for which no system identifier could be generated
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

    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 106, Column 2398: entity was defined here
    …_2dgxwoZBLRMD9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Si…
  • Warning Line 166, Column 7438: reference not terminated by REFC delimiter
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" info="22643…

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

  • Warning Line 166, Column 7438: reference to external entity in attribute value
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" info="22643…

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

  • Error Line 166, Column 7438: reference to entity "utm_campaign" for which no system identifier could be generated
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" info="22643…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Warning Line 166, Column 10793: reference not terminated by REFC delimiter
    …_fakultet-3691_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Warning Line 166, Column 10793: reference to external entity in attribute value
    …_fakultet-3691_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Error Line 166, Column 10793: reference to entity "a_bid" for which no system identifier could be generated
    …_fakultet-3691_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 166, Column 10813: reference not terminated by REFC delimiter
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Warning Line 166, Column 10813: reference to external entity in attribute value
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Error Line 166, Column 10813: reference to entity "utm_source" for which no system identifier could be generated
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 166, Column 10834: reference not terminated by REFC delimiter
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Warning Line 166, Column 10834: reference to external entity in attribute value
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Error Line 166, Column 10834: reference to entity "utm_medium" for which no system identifier could be generated
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 166, Column 10855: reference not terminated by REFC delimiter
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22633…

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

  • Warning Line 166, Column 10855: reference to external entity in attribute value
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22633…

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

  • Error Line 166, Column 10855: reference to entity "utm_campaign" for which no system identifier could be generated
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22633…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Error Line 166, Column 11416: required attribute "src" not specified
    …/files/images/icons/s/seks_2795.gif" /><a href="http://www.tportal.hr/lifestyl…

    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 166, Column 11710: required attribute "src" not specified
    …iles/images/icons/g/gitara_1069.gif" /><a href="http://www.tportal.hr/showtime…

    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 166, Column 12043: required attribute "src" not specified
    …les/images/icons/b/bundy2_25508.jpg" /><a href="http://www.tportal.hr/funbox/f…

    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 166, Column 12337: required attribute "src" not specified
    …les/images/icons/n/novac-3_3779.png" /><a href="http://www.vecernji.hr/sport/o…

    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 166, Column 12650: required attribute "src" not specified
    …s/images/icons/m/madonna5_25303.jpg" /><a href="http://dnevnik.hr/showbuzz/cel…

    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 166, Column 13001: required attribute "src" not specified
    …les/images/icons/s/stopalo_3021.gif" /><a href="http://www.24sata.hr/sudbine/s…

    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 166, Column 13331: required attribute "src" not specified
    …mages/icons/h/heartbroken_23987.gif" /><a href="http://www.index.hr/clanak.asp…

    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 166, Column 13563: required attribute "src" not specified
    …/files/images/icons/c/coke_5042.gif" /><a href="http://www.bbc.co.uk/news/maga…

    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 166, Column 13636: cannot generate system identifier for general entity "ns_source"
    …/magazine-21201680#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank…

    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 166, Column 13636: general entity "ns_source" not defined and no default entity
    …/magazine-21201680#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank…

    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 166, Column 13645: reference not terminated by REFC delimiter
    …-21201680#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 13645: reference to external entity in attribute value
    …-21201680#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 13645: reference to entity "ns_source" for which no system identifier could be generated
    …-21201680#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 13635: entity was defined here
    …s/magazine-21201680#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blan…
  • Error Line 166, Column 13848: required attribute "src" not specified
    …files/images/icons/s/sport_3623.gif" /><a href="http://www.tportal.hr/sport/ko…

    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 166, Column 14173: required attribute "src" not specified
    …iles/images/icons/g/glazba_3612.gif" /><a href="http://www.tportal.hr/lifestyl…

    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 166, Column 14464: required attribute "src" not specified
    …/files/images/icons/i/igla_1308.gif" /><a href="http://www.plivazdravlje.hr/vi…

    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 166, Column 14746: required attribute "src" not specified
    …es/images/icons/t/tvdjeca_27810.jpg" /><a href="http://dnevnik.hr/vijesti/zani…

    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 166, Column 15057: required attribute "src" not specified
    …images/icons/c/celebrities_3606.gif" /><a href="http://www.vecernji.hr/scena/l…

    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 166, Column 15373: required attribute "src" not specified
    …les/images/icons/b/brkovi_25459.jpg" /><a href="http://www.hrt.hr/index.php?id…

    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 166, Column 15426: reference not terminated by REFC delimiter
    …//www.hrt.hr/index.php?id=48&tx_ttnews[tt_news]=199200&tx_ttnews[backPid]=850&…

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

  • Warning Line 166, Column 15426: reference to external entity in attribute value
    …//www.hrt.hr/index.php?id=48&tx_ttnews[tt_news]=199200&tx_ttnews[backPid]=850&…

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

  • Error Line 166, Column 15426: reference to entity "tx_ttnews" for which no system identifier could be generated
    …//www.hrt.hr/index.php?id=48&tx_ttnews[tt_news]=199200&tx_ttnews[backPid]=850&…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 166, Column 15452: reference not terminated by REFC delimiter
    …48&tx_ttnews[tt_news]=199200&tx_ttnews[backPid]=850&cHash=c5cce841b5" target="…

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

  • Warning Line 166, Column 15452: reference to external entity in attribute value
    …48&tx_ttnews[tt_news]=199200&tx_ttnews[backPid]=850&cHash=c5cce841b5" target="…

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

  • Error Line 166, Column 15452: reference to entity "tx_ttnews" for which no system identifier could be generated
    …48&tx_ttnews[tt_news]=199200&tx_ttnews[backPid]=850&cHash=c5cce841b5" target="…

    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 107, Column 2094: entity was defined here
    …www.hrt.hr/index.php?id=vijesti-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15…
  • Warning Line 166, Column 15471: reference not terminated by REFC delimiter
    …s]=199200&tx_ttnews[backPid]=850&cHash=c5cce841b5" target="_blank" info="22623…

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

  • Warning Line 166, Column 15471: reference to external entity in attribute value
    …s]=199200&tx_ttnews[backPid]=850&cHash=c5cce841b5" target="_blank" info="22623…

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

  • Error Line 166, Column 15471: reference to entity "cHash" for which no system identifier could be generated
    …s]=199200&tx_ttnews[backPid]=850&cHash=c5cce841b5" target="_blank" info="22623…

    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 107, Column 2124: entity was defined here
    …i-clanak&tx_ttnews%5Btt_news%5D=199663&cHash=e15a15b810" target="_blank" rel="…
  • Error Line 166, Column 15675: required attribute "src" not specified
    …les/images/icons/p/pingvin_2372.gif" /><a href="http://www.klix.ba/magazin/fot…

    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 166, Column 15981: required attribute "src" not specified
    …images/icons/m/marihuana4_27799.jpg" /><a href="http://www.huffingtonpost.com/…

    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 166, Column 16285: required attribute "src" not specified
    …les/images/icons/d/detroit_4987.gif" /><a href="http://edition.cnn.com/2013/01…

    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 166, Column 16563: required attribute "src" not specified
    …files/images/icons/m/munja_2082.gif" /><a href="http://feeds.popsci.com/c/3456…

    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 166, Column 16897: required attribute "src" not specified
    …files/images/icons/d/darth_3976.jpg" /><a href="http://www.klix.ba/magazin/fil…

    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 166, Column 17199: required attribute "src" not specified
    …files/images/icons/n/nemo_26132.jpg" /><a href="http://www.cracktwo.com/2013/0…

    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 166, Column 17462: required attribute "src" not specified
    …iles/images/icons/a/auti1_26874.png" /><a href="http://www.automobili.hr/clana…

    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 166, Column 17739: required attribute "src" not specified
    …/files/images/icons/s/saka_4531.gif" /><a href="http://feeds.mashable.com/~r/M…

    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 166, Column 17998: required attribute "src" not specified
    …files/images/icons/z/zena_25455.jpg" /><a href="http://www.salon.com/2013/01/2…

    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 166, Column 18258: required attribute "src" not specified
    …iles/images/icons/g/google_1131.jpg" /><a href="http://feedproxy.google.com/~r…

    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 166, Column 18555: required attribute "src" not specified
    …r/files/images/icons/d/duh_3829.gif" /><a href="http://www.tportal.hr/funbox/f…

    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 166, Column 18862: required attribute "src" not specified
    …iles/images/icons/p/pizza_28594.gif" /><a href="http://www.ponudadana.hr/Dvije…

    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 166, Column 18967: reference not terminated by REFC delimiter
    …samo-35kn-4240_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Warning Line 166, Column 18967: reference to external entity in attribute value
    …samo-35kn-4240_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Error Line 166, Column 18967: reference to entity "a_bid" for which no system identifier could be generated
    …samo-35kn-4240_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 166, Column 18987: reference not terminated by REFC delimiter
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Warning Line 166, Column 18987: reference to external entity in attribute value
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Error Line 166, Column 18987: reference to entity "utm_source" for which no system identifier could be generated
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 166, Column 19008: reference not terminated by REFC delimiter
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Warning Line 166, Column 19008: reference to external entity in attribute value
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Error Line 166, Column 19008: reference to entity "utm_medium" for which no system identifier could be generated
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 166, Column 19029: reference not terminated by REFC delimiter
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22613…

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

  • Warning Line 166, Column 19029: reference to external entity in attribute value
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22613…

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

  • Error Line 166, Column 19029: reference to entity "utm_campaign" for which no system identifier could be generated
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22613…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Error Line 166, Column 19281: required attribute "src" not specified
    …es/images/icons/p/politika_3617.gif" /><a href="http://www.24sata.hr/strane-zv…

    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 166, Column 19593: required attribute "src" not specified
    …/files/images/icons/s/seks_2795.gif" /><a href="http://www.tportal.hr/lifestyl…

    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 166, Column 19882: required attribute "src" not specified
    …iles/images/icons/d/djeca_28537.jpg" /><a href="http://dnevnik.hr/vijesti/svij…

    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 166, Column 20197: required attribute "src" not specified
    …s/icons/s/svisuludizamary_25497.jpg" /><a href="http://www.24sata.hr/ljubav-se…

    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 166, Column 20513: required attribute "src" not specified
    …/files/images/icons/f/film_3611.gif" /><a href="http://dnevnik.hr/showbuzz/cel…

    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 166, Column 20782: cannot generate system identifier for general entity "v"
    …ube.com/watch?feature=player_embedded&v=SEQ8jyvmYtw<nid>&amp;label= bodybuilde…

    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 166, Column 20782: general entity "v" not defined and no default entity
    …ube.com/watch?feature=player_embedded&v=SEQ8jyvmYtw<nid>&amp;label= bodybuilde…

    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 166, Column 20783: reference not terminated by REFC delimiter
    …be.com/watch?feature=player_embedded&v=SEQ8jyvmYtw<nid>&amp;label= bodybuilder…

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

  • Warning Line 166, Column 20783: reference to external entity in attribute value
    …be.com/watch?feature=player_embedded&v=SEQ8jyvmYtw<nid>&amp;label= bodybuilder…

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

  • Error Line 166, Column 20783: reference to entity "v" for which no system identifier could be generated
    …be.com/watch?feature=player_embedded&v=SEQ8jyvmYtw<nid>&amp;label= bodybuilder…

    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 166, Column 20781: entity was defined here
    …tube.com/watch?feature=player_embedded&v=SEQ8jyvmYtw<nid>&amp;label= bodybuild…
  • Warning Line 166, Column 20795: character "<" is the first character of a delimiter but occurred as data
    …?feature=player_embedded&v=SEQ8jyvmYtw<nid>&amp;label= bodybuildera" target="_…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 166, Column 20841: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …p;label= bodybuildera" target="_blank"> bodybuildera</a> jeo 10 obroka dnevno<…

    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 166, Column 20983: required attribute "src" not specified
    …/files/images/icons/s/seks_2795.gif" /><a href="http://www.jutarnji.hr/stizu-o…

    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 166, Column 21298: required attribute "src" not specified
    …files/images/icons/p/pas2_25246.jpg" /><a href="http://www.vecernji.hr/zagreb/…

    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 166, Column 21589: required attribute "src" not specified
    …/images/icons/d/dicaprio2_25181.jpg" /><a href="http://www.vecernji.hr/scena/l…

    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 166, Column 21919: required attribute "src" not specified
    …les/images/icons/b/bundy2_25508.jpg" /><a href="http://www.youtube.com/watch?f…

    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 166, Column 21983: reference not terminated by REFC delimiter
    …be.com/watch?feature=player_embedded&v=vumzl-lQ0gg" target="_blank" info="2261…

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

  • Warning Line 166, Column 21983: reference to external entity in attribute value
    …be.com/watch?feature=player_embedded&v=vumzl-lQ0gg" target="_blank" info="2261…

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

  • Error Line 166, Column 21983: reference to entity "v" for which no system identifier could be generated
    …be.com/watch?feature=player_embedded&v=vumzl-lQ0gg" target="_blank" info="2261…

    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 166, Column 20781: entity was defined here
    …tube.com/watch?feature=player_embedded&v=SEQ8jyvmYtw<nid>&amp;label= bodybuild…
  • Error Line 166, Column 22219: required attribute "src" not specified
    …/images/icons/a/anonimus2_25383.jpg" /><a href="http://www.tportal.hr/kultura/…

    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 166, Column 22526: required attribute "src" not specified
    …iles/images/icons/g/gitara_1071.gif" /><a href="http://www.soundset.hr/glazba/…

    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 166, Column 22787: required attribute "src" not specified
    …iles/images/icons/u/usne2_25339.jpg" /><a href="http://www.tportal.hr/portalpl…

    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 166, Column 23126: required attribute "src" not specified
    …ges/icons/k/kimkardashian_25218.jpg" /><a href="http://dnevnik.hr/showbuzz/cel…

    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 166, Column 23423: required attribute "src" not specified
    …es/images/icons/d/djevojka_3009.gif" /><a href="http://www.index.hr/clanak.asp…

    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 166, Column 23692: required attribute "src" not specified
    …iles/images/icons/b/baka2_25426.jpg" /><a href="http://www.index.hr/clanak.asp…

    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 166, Column 23953: required attribute "src" not specified
    …/images/icons/z/zuckerberg_4658.png" /><a href="http://www.vecernji.hr/vijesti…

    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 166, Column 24256: required attribute "src" not specified
    …les/images/icons/p/poljubac_362.gif" /><a href="http://www.vecernji.hr/scena/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>.

  • Error Line 166, Column 24559: required attribute "src" not specified
    …s/images/icons/r/radni-stol_720.gif" /><a href="http://www.24sata.hr/lifestyle…

    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 166, Column 24856: required attribute "src" not specified
    …files/images/icons/d/dolar_3766.gif" /><a href="http://www.24sata.hr/strane-zv…

    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 166, Column 25167: required attribute "src" not specified
    …r/files/images/icons/a/auto_548.gif" /><a href="http://www.tportal.hr/lifestyl…

    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 166, Column 25451: required attribute "src" not specified
    …ges/icons/e/edwardcullen2_25185.jpg" /><a href="http://www.tportal.hr/portalpl…

    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 166, Column 25779: required attribute "src" not specified
    …files/images/icons/s/san2_25325.jpg" /><a href="http://metro-portal.hr/za-bolj…

    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 166, Column 26053: required attribute "src" not specified
    …les/images/icons/b/bieber_25166.jpg" /><a href="http://www.vecernji.hr/scena/j…

    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 166, Column 26372: required attribute "src" not specified
    …iles/images/icons/b/bocica_1964.gif" /><a href="http://www.businessinsider.com…

    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 166, Column 26510: character "&" is the first character of a delimiter but occurred as data
    …k" info="226054" rel="nofollow">Dolce & Gabbana rade parfem za bebe</a></li><l…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 166, Column 26650: required attribute "src" not specified
    …mages/icons/c/charlie-brown_583.gif" /><a href="http://edition.cnn.com/2013/01…

    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 166, Column 26968: required attribute "src" not specified
    …s/images/icons/s/snjegovic_2943.gif" /><a href="http://mashable.com/2013/01/23…

    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 166, Column 27209: required attribute "src" not specified
    …files/images/icons/g/gmail_4860.png" /><a href="http://mashable.com/2013/01/23…

    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 166, Column 27480: required attribute "src" not specified
    …les/images/icons/p/pticice_4791.gif" /><a href="http://edition.cnn.com/2013/01…

    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 166, Column 27750: required attribute "src" not specified
    …/files/images/icons/p/ptica_322.gif" /><a href="http://biologija.com.hr/module…

    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 166, Column 28026: required attribute "src" not specified
    …les/images/icons/t/tableta_4817.gif" /><a href="http://biologija.com.hr/module…

    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 166, Column 28295: required attribute "src" not specified
    …s/images/icons/k/kazaliste_5163.gif" /><a href="http://www.jutarnji.hr/mucnoj-…

    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 166, Column 28657: required attribute "src" not specified
    …les/images/icons/p/poljubac_362.gif" /><a href="http://www.inquisitr.com/48901…

    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 166, Column 29025: required attribute "src" not specified
    …/images/icons/m/marihuana_27798.jpg" /><a href="http://www.dailybulletin.com/b…

    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 166, Column 29345: required attribute "src" not specified
    …files/images/icons/d/dijete_764.gif" /><a href="http://www.vecernji.hr/zagreb/…

    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 166, Column 29721: required attribute "src" not specified
    …iles/images/icons/l/ljubav_1785.gif" /><a href="http://www.vecernji.hr/zivot/v…

    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 166, Column 30024: required attribute "src" not specified
    …es/icons/s/speedy-gonzales_1125.gif" /><a href="http://www.vecernji.hr/vijesti…

    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 166, Column 30350: required attribute "src" not specified
    …es/images/icons/j/joystick_1044.gif" /><a href="http://www.complex.com/video-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>.

  • Error Line 166, Column 30692: required attribute "src" not specified
    …files/images/icons/m/meso_28592.gif" /><a href="http://www.ponudadana.hr/Mesna…

    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 166, Column 30865: reference not terminated by REFC delimiter
    …ana_Kruge-3987_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Warning Line 166, Column 30865: reference to external entity in attribute value
    …ana_Kruge-3987_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Error Line 166, Column 30865: reference to entity "a_bid" for which no system identifier could be generated
    …ana_Kruge-3987_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 166, Column 30885: reference not terminated by REFC delimiter
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Warning Line 166, Column 30885: reference to external entity in attribute value
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Error Line 166, Column 30885: reference to entity "utm_source" for which no system identifier could be generated
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 166, Column 30906: reference not terminated by REFC delimiter
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Warning Line 166, Column 30906: reference to external entity in attribute value
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Error Line 166, Column 30906: reference to entity "utm_medium" for which no system identifier could be generated
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 166, Column 30927: reference not terminated by REFC delimiter
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22596…

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

  • Warning Line 166, Column 30927: reference to external entity in attribute value
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22596…

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

  • Error Line 166, Column 30927: reference to entity "utm_campaign" for which no system identifier could be generated
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22596…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Error Line 166, Column 31157: required attribute "src" not specified
    …les/images/icons/u/upaljac_3307.gif" /><a href="http://www.poslovni.hr/hrvatsk…

    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 166, Column 31430: required attribute "src" not specified
    …files/images/icons/a/auto_25424.jpg" /><a href="http://www.automobili.hr/clana…

    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 166, Column 31706: required attribute "src" not specified
    …/files/images/icons/c/car6_4630.gif" /><a href="http://www.automobili.hr/clana…

    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 166, Column 31964: required attribute "src" not specified
    …/files/images/icons/s/seks_2795.gif" /><a href="http://www.vecernji.hr/zivot/v…

    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 166, Column 32247: required attribute "src" not specified
    …iles/images/icons/r/razvod_2662.gif" /><a href="http://www.24sata.hr/ljubav-se…

    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 166, Column 32576: required attribute "src" not specified
    …ages/icons/f/filmska-traka_3731.gif" /><a href="http://pogledaj.to/art/najbolj…

    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 166, Column 32824: required attribute "src" not specified
    …es/images/icons/p/pracovjek_557.gif" /><a href="http://www.bbc.co.uk/news/scie…

    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 166, Column 32917: reference not terminated by REFC delimiter
    …-21123717#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 32917: reference to external entity in attribute value
    …-21123717#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 32917: reference to entity "ns_source" for which no system identifier could be generated
    …-21123717#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 13635: entity was defined here
    …s/magazine-21201680#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blan…
  • Error Line 166, Column 33166: required attribute "src" not specified
    …r/files/images/icons/v/vino_812.gif" /><a href="http://boingboing.net/2013/01/…

    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 166, Column 33500: required attribute "src" not specified
    …les/images/icons/a/autobus_2869.gif" /><a href="http://www.huffingtonpost.com/…

    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 166, Column 33818: required attribute "src" not specified
    …es/images/icons/p/pustinja_3875.gif" /><a href="http://www.neatorama.com/2013/…

    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 166, Column 34077: required attribute "src" not specified
    …/icons/s/saka-udarac-mala_25324.jpg" /><a href="http://www.blog.blagus.eu/potr…

    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 166, Column 34396: required attribute "src" not specified
    …/files/images/icons/f/foto_4990.gif" /><a href="http://www.jutarnji.hr/foto---…

    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 166, Column 34683: required attribute "src" not specified
    …les/images/icons/t/tablete_1912.gif" /><a href="http://www.slobodnadalmacija.h…

    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 166, Column 35009: required attribute "src" not specified
    …es/images/icons/z/zdravlje_3621.gif" /><a href="http://www.bbc.co.uk/news/heal…

    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 166, Column 35089: reference not terminated by REFC delimiter
    …-21123204#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 35089: reference to external entity in attribute value
    …-21123204#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 35089: reference to entity "ns_source" for which no system identifier could be generated
    …-21123204#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 13635: entity was defined here
    …s/magazine-21201680#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blan…
  • Error Line 166, Column 35333: required attribute "src" not specified
    …files/images/icons/j/jesen_4675.gif" /><a href="http://www.tportal.hr/scitech/…

    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 166, Column 35631: required attribute "src" not specified
    …files/images/icons/m/muzej_4280.gif" /><a href="http://www.tportal.hr/kultura/…

    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 166, Column 35927: required attribute "src" not specified
    …/images/icons/m/marihuana_28456.jpg" /><a href="http://www.vecernji.hr/zivot/u…

    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 166, Column 36231: required attribute "src" not specified
    …r/files/images/icons/v/vino_812.gif" /><a href="http://www.vecernji.hr/regije/…

    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 166, Column 36511: required attribute "src" not specified
    …s/images/icons/k/krastavac_4685.gif" /><a href="http://www.vecernji.hr/zivot/j…

    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 166, Column 36796: required attribute "src" not specified
    …r/files/images/icons/a/auto_202.gif" /><a href="http://www.automobili.hr/clana…

    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 166, Column 37083: required attribute "src" not specified
    …les/images/icons/l/ljubav_25296.jpg" /><a href="http://www.cbsnews.com/8301-20…

    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 166, Column 37418: required attribute "src" not specified
    …iles/images/icons/a/auti7_26875.png" /><a href="http://www.automobili.hr/clana…

    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 166, Column 37694: required attribute "src" not specified
    …mages/icons/m/marsattacks_26750.jpg" /><a href="http://www.slobodnadalmacija.h…

    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 166, Column 38020: required attribute "src" not specified
    …/files/images/icons/s/suma_3050.gif" /><a href="http://www.huffingtonpost.com/…

    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 166, Column 38333: required attribute "src" not specified
    …iles/images/icons/g/glazba_1088.gif" /><a href="http://www.dailymail.co.uk/new…

    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 166, Column 38707: required attribute "src" not specified
    …/icons/v/vatrogasno-vozilo_4737.gif" /><a href="http://www.thescottishsun.co.u…

    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 166, Column 39076: required attribute "src" not specified
    …ges/icons/b/barack-obama-3_3790.gif" /><a href="http://i.imgur.com/G0j3JUy.gif…

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

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

  • Error Line 166, Column 39316: required attribute "src" not specified
    …r/files/images/icons/a/auto_203.gif" /><a href="http://well.blogs.nytimes.com/…

    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 166, Column 39577: required attribute "src" not specified
    …files/images/icons/p/puska_2589.gif" /><a href="http://www.bbc.co.uk/news/worl…

    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 166, Column 39851: required attribute "src" not specified
    …files/images/icons/o/obama_3705.png" /><a href="http://imgur.com/3PjLC7S" targ…

    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 166, Column 40095: required attribute "src" not specified
    …rihuana-testisa-slika-124_27797.jpg" /><a href="http://www.politika.hr/svijet/…

    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 166, Column 40388: required attribute "src" not specified
    …es/icons/n/nogometnalopta_25241.jpg" /><a href="http://www.klix.ba/sport/nogom…

    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 166, Column 40731: required attribute "src" not specified
    …les/images/icons/k/kosarka_1605.gif" /><a href="http://www.slobodnadalmacija.h…

    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 166, Column 41069: required attribute "src" not specified
    …les/images/icons/b/brkovi_25459.jpg" /><a href="http://www.24sata.hr/ljubav-se…

    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 166, Column 41398: required attribute "src" not specified
    …les/images/icons/k/kosarka_1605.gif" /><a href="http://sportski.net.hr/kosarka…

    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 166, Column 41740: required attribute "src" not specified
    …iles/images/icons/g/glazba_3612.gif" /><a href="http://www.klix.ba/magazin/muz…

    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 166, Column 42023: required attribute "src" not specified
    …s/images/icons/t/trudnoca_26485.jpg" /><a href="http://danas.net.hr/svijet/tru…

    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 166, Column 42365: required attribute "src" not specified
    …files/images/icons/z/zena_25455.jpg" /><a href="http://www.24sata.hr/psihologi…

    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 166, Column 42692: required attribute "src" not specified
    …les/images/icons/s/siromah_5127.gif" /><a href="http://feeds.net.hr/c/33283/f/…

    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 166, Column 43126: required attribute "src" not specified
    …mages/icons/d/depresivna2_25283.jpg" /><a href="http://www.plivazdravlje.hr/vi…

    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 166, Column 43443: required attribute "src" not specified
    …files/images/icons/z/zamak_4283.gif" /><a href="http://dnevnik.hr/vijesti/tech…

    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 166, Column 43766: required attribute "src" not specified
    …s/images/icons/s/snjegovic_3938.gif" /><a href="http://dnevnik.hr/showbuzz/cel…

    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 166, Column 44051: required attribute "src" not specified
    …/files/images/icons/c/crkva_662.gif" /><a href="http://www.jutarnji.hr/klauzur…

    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 166, Column 44354: required attribute "src" not specified
    …es/images/icons/m/migrena_28588.gif" /><a href="http://www.kolektiva.hr/zagreb…

    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 166, Column 44464: reference not terminated by REFC delimiter
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Warning Line 166, Column 44464: reference to external entity in attribute value
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

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

  • Error Line 166, Column 44464: reference to entity "a_bid" for which no system identifier could be generated
    …12013.html?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 166, Column 44484: reference not terminated by REFC delimiter
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Warning Line 166, Column 44484: reference to external entity in attribute value
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

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

  • Error Line 166, Column 44484: reference to entity "utm_source" for which no system identifier could be generated
    …itor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 166, Column 44505: reference not terminated by REFC delimiter
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Warning Line 166, Column 44505: reference to external entity in attribute value
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

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

  • Error Line 166, Column 44505: reference to entity "utm_medium" for which no system identifier could be generated
    …15b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals&utm_campai…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 166, Column 44523: reference not terminated by REFC delimiter
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Warning Line 166, Column 44523: reference to external entity in attribute value
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

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

  • Error Line 166, Column 44523: reference to entity "utm_content" for which no system identifier could be generated
    …affiliate&utm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" tar…

    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 106, Column 2398: entity was defined here
    …_2dgxwoZBLRMD9SAgYsYFLJ?utm_medium=rss&utm_content=%20%20%20%20%20%20Page%20Si…
  • Warning Line 166, Column 44547: reference not terminated by REFC delimiter
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" info="22562…

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

  • Warning Line 166, Column 44547: reference to external entity in attribute value
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" info="22562…

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

  • Error Line 166, Column 44547: reference to entity "utm_campaign" for which no system identifier could be generated
    …ks&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank" info="22562…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Error Line 166, Column 44791: required attribute "src" not specified
    …r/files/images/icons/a/auto_202.gif" /><a href="http://www.automobili.hr/clana…

    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 166, Column 45073: required attribute "src" not specified
    …files/images/icons/k/kokos_1566.gif" /><a href="http://dnevnik.hr/vijesti/zani…

    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 166, Column 45371: required attribute "src" not specified
    …images/icons/j/johnnydepp_28451.jpg" /><a href="http://www.jutarnji.hr/depp-zb…

    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 166, Column 45737: required attribute "src" not specified
    …es/images/icons/s/snijeg2_28566.jpg" /><a href="http://www.plivazdravlje.hr/vi…

    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 166, Column 46085: required attribute "src" not specified
    …/images/icons/m/marihuana_28456.jpg" /><a href="http://www.24sata.hr/crna-kron…

    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 166, Column 46417: required attribute "src" not specified
    …iles/images/icons/b/batman_3922.gif" /><a href="http://www.poslovni.hr/after5/…

    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 166, Column 46729: required attribute "src" not specified
    …les/images/icons/b/brak99_27759.jpg" /><a href="http://www.tportal.hr/lifestyl…

    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 166, Column 47036: required attribute "src" not specified
    …les/images/icons/a/akvarij_4505.gif" /><a href="http://www.tportal.hr/funbox/f…

    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 166, Column 47321: required attribute "src" not specified
    …/images/icons/p/pegbundy2_25546.jpg" /><a href="http://www.tportal.hr/funbox/f…

    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 166, Column 47618: required attribute "src" not specified
    …iles/images/icons/z/zebra_25480.jpg" /><a href="http://biologija.com.hr/module…

    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 166, Column 47892: required attribute "src" not specified
    …les/images/icons/b/bundy2_25508.jpg" /><a href="http://biologija.com.hr/module…

    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 166, Column 48160: required attribute "src" not specified
    …/icons/f/fotografija-lens_27485.jpg" /><a href="http://www.slobodnadalmacija.h…

    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 166, Column 48507: required attribute "src" not specified
    …es/images/icons/l/ljepota_28587.gif" /><a href="http://www.ponudadana.hr/10_IP…

    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 166, Column 48726: reference not terminated by REFC delimiter
    …i_dolazak-4010_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Warning Line 166, Column 48726: reference to external entity in attribute value
    …i_dolazak-4010_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

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

  • Error Line 166, Column 48726: reference to entity "a_bid" for which no system identifier could be generated
    …i_dolazak-4010_1?a_aid=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_mediu…

    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 61, Column 83: entity was defined here
    …ktiva.hr/zagreb/?a_aid=monitor_monitor&a_bid=528a7489" rel="">Kolektiva</a></l…
  • Warning Line 166, Column 48746: reference not terminated by REFC delimiter
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Warning Line 166, Column 48746: reference to external entity in attribute value
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

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

  • Error Line 166, Column 48746: reference to entity "utm_source" for which no system identifier could be generated
    …id=12mon3koX&a_bid=e6809470&utm_source=affiliate&utm_medium=txtlink&utm_campai…

    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 106, Column 3984: entity was defined here
    …l?a_aid=monitor_monitor&a_bid=b515b319&utm_source=affiliate&utm_medium=links&u…
  • Warning Line 166, Column 48767: reference not terminated by REFC delimiter
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Warning Line 166, Column 48767: reference to external entity in attribute value
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

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

  • Error Line 166, Column 48767: reference to entity "utm_medium" for which no system identifier could be generated
    …809470&utm_source=affiliate&utm_medium=txtlink&utm_campaign=monitor.hr" target…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 166, Column 48788: reference not terminated by REFC delimiter
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22544…

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

  • Warning Line 166, Column 48788: reference to external entity in attribute value
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22544…

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

  • Error Line 166, Column 48788: reference to entity "utm_campaign" for which no system identifier could be generated
    …iliate&utm_medium=txtlink&utm_campaign=monitor.hr" target="_blank" info="22544…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Error Line 166, Column 49013: required attribute "src" not specified
    …/files/images/icons/z/zena_5003.gif" /><a href="http://www.bbc.co.uk/news/worl…

    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 166, Column 49102: reference not terminated by REFC delimiter
    …-21088811#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 49102: reference to external entity in attribute value
    …-21088811#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 49102: reference to entity "ns_source" for which no system identifier could be generated
    …-21088811#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blank" info="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 166, Column 13635: entity was defined here
    …s/magazine-21201680#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa" target="_blan…
  • Error Line 166, Column 49331: required attribute "src" not specified
    …iles/images/icons/g/google_1131.jpg" /><a href="http://mashable.com/2013/01/18…

    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 166, Column 49421: reference not terminated by REFC delimiter
    …labs/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Mashable+%28M…

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

  • Warning Line 166, Column 49421: reference to external entity in attribute value
    …labs/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Mashable+%28M…

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

  • Error Line 166, Column 49421: reference to entity "utm_medium" for which no system identifier could be generated
    …labs/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Mashable+%28M…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 166, Column 49439: reference not terminated by REFC delimiter
    …eedburner&utm_medium=feed&utm_campaign=Feed%3A+Mashable+%28Mashable%29" target…

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

  • Warning Line 166, Column 49439: reference to external entity in attribute value
    …eedburner&utm_medium=feed&utm_campaign=Feed%3A+Mashable+%28Mashable%29" target…

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

  • Error Line 166, Column 49439: reference to entity "utm_campaign" for which no system identifier could be generated
    …eedburner&utm_medium=feed&utm_campaign=Feed%3A+Mashable+%28Mashable%29" target…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Error Line 166, Column 49672: required attribute "src" not specified
    …es/images/icons/f/facebook_4198.png" /><a href="http://www.businessinsider.com…

    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 166, Column 49798: reference not terminated by REFC delimiter
    …013-1?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+businessinsid…

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

  • Warning Line 166, Column 49798: reference to external entity in attribute value
    …013-1?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+businessinsid…

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

  • Error Line 166, Column 49798: reference to entity "utm_medium" for which no system identifier could be generated
    …013-1?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+businessinsid…

    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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 166, Column 49816: reference not terminated by REFC delimiter
    …eedburner&utm_medium=feed&utm_campaign=Feed%3A+businessinsider+%28Business+Ins…

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

  • Warning Line 166, Column 49816: reference to external entity in attribute value
    …eedburner&utm_medium=feed&utm_campaign=Feed%3A+businessinsider+%28Business+Ins…

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

  • Error Line 166, Column 49816: reference to entity "utm_campaign" for which no system identifier could be generated
    …eedburner&utm_medium=feed&utm_campaign=Feed%3A+businessinsider+%28Business+Ins…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Error Line 166, Column 50061: required attribute "src" not specified
    …files/images/icons/c/chrome_601.jpg" /><a href="http://techcrunch.com/2013/01/…

    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 166, Column 50190: reference not terminated by REFC delimiter
    …-one/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Techcrunch+%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 166, Column 50190: reference to external entity in attribute value
    …-one/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Techcrunch+%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 166, Column 50190: reference to entity "utm_medium" for which no system identifier could be generated
    …-one/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Techcrunch+%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 106, Column 4005: entity was defined here
    …or&a_bid=b515b319&utm_source=affiliate&utm_medium=links&utm_content=boostdeals…
  • Warning Line 166, Column 50208: reference not terminated by REFC delimiter
    …eedburner&utm_medium=feed&utm_campaign=Feed%3A+Techcrunch+%28TechCrunch%29" ta…

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

  • Warning Line 166, Column 50208: reference to external entity in attribute value
    …eedburner&utm_medium=feed&utm_campaign=Feed%3A+Techcrunch+%28TechCrunch%29" ta…

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

  • Error Line 166, Column 50208: reference to entity "utm_campaign" for which no system identifier could be generated
    …eedburner&utm_medium=feed&utm_campaign=Feed%3A+Techcrunch+%28TechCrunch%29" ta…

    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 106, Column 4045: entity was defined here
    …tm_medium=links&utm_content=boostdeals&utm_campaign=monitor.hr" target="_blank…
  • Error Line 166, Column 50442: required attribute "src" not specified
    …/files/images/icons/f/film_3611.gif" /><a href="http://www.24sata.hr/strane-zv…

    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 166, Column 50769: required attribute "src" not specified
    …s/images/icons/c/cornelius_4650.gif" /><a href="http://www.tportal.hr/funbox/f…

    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 166, Column 51074: required attribute "src" not specified
    …/files/images/icons/s/seks_2795.gif" /><a href="http://www.tportal.hr/lifestyl…

    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 166, Column 51370: required attribute "src" not specified
    …/files/images/icons/z/zena_1579.gif" /><a href="http://www.index.hr/clanak.asp…

    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 166, Column 51647: required attribute "src" not specified
    …es/icons/d/djevojka-vesela_3362.gif" /><a href="http://www.tportal.hr/lifestyl…

    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 166, Column 51937: required attribute "src" not specified
    …s/images/icons/m/medvescak_1923.jpg" /><a href="http://www.vedrantolic.com/p67…

    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 166, Column 52200: required attribute "src" not specified
    …s/images/icons/m/muskarac_27981.jpg" /><a href="http://www.index.hr/clanak.asp…

    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 166, Column 52456: required attribute "src" not specified
    …les/images/icons/k/kosarka_1608.gif" /><a href="http://www.index.hr/clanak.asp…

    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 166, Column 52741: required attribute "src" not specified
    …iles/images/icons/p/pozar_25409.jpg" /><a href="http://www.index.hr/clanak.asp…

    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 166, Column 53023: required attribute "src" not specified
    …s/images/icons/s/sevemala_25326.jpg" /><a href="http://www.tportal.hr/showtime…

    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 166, Column 53344: required attribute "src" not specified
    …/images/icons/m/mona-lisa2_4327.gif" /><a href="http://www.index.hr/clanak.asp…

    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 166, Column 53585: required attribute "src" not specified
    …files/images/icons/t/trazi_5102.png" /><a href="http://www.businessinsider.com…

    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 166, Column 53873: required attribute "src" not specified
    …iles/images/icons/g/galaxy_4839.gif" /><a href="http://mashable.com/2013/01/18…

    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 166, Column 54120: required attribute "src" not specified
    …iles/images/icons/s/svijet_3624.gif" /><a href="http://mashable.com/2013/01/18…

    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 166, Column 54414: required attribute "type" not specified
    …ti</dt><dd style="color: #000000;background: #ffffff;text-align: left"><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 173, Column 14: there is no attribute "class"
    <TABLE class="kalendar" cellspacing="1" width="100%">

    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 173, Column 37: there is no attribute "cellspacing"
    <TABLE class="kalendar" cellspacing="1" width="100%">

    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 173, Column 47: there is no attribute "width"
    <TABLE class="kalendar" cellspacing="1" width="100%">

    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 173, Column 53: element "TABLE" undefined
    <TABLE class="kalendar" cellspacing="1" width="100%">

    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 174, Column 13: there is no attribute "height"
    	<TR height="18">

    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 174, Column 17: element "TR" undefined
    	<TR height="18">

    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 175, Column 13: there is no attribute "class"
    		<TD class="kalendar-strelica-natrag">

    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 175, Column 39: element "TD" undefined
    		<TD class="kalendar-strelica-natrag">

    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 176, Column 112: required attribute "alt" not specified
    …one;"><img src="http://www.monitor.hr/adminmax/img/system/loading.gif" /></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 177, Column 60: there is no attribute "onClick"
    …a href="javascript: void(0);" onClick="get_month('1355569200', 'p');" rel="nof…

    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 177, Column 114: end tag for element "A" which is not open
    …void(0);" onClick="get_month('1355569200', 'p');" rel="nofollow">&lt;</A></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.

  • Error Line 177, Column 120: end tag for "a" omitted, but OMITTAG NO was specified
    …void(0);" onClick="get_month('1355569200', 'p');" rel="nofollow">&lt;</A></div>

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

  • Info Line 177, Column 21: start tag was here
    			<div id="link_p"><a href="javascript: void(0);" onClick="get_month('13555692…
  • Error Line 179, Column 15: there is no attribute "COLSPAN"
    		<TD COLSPAN="5" class="kalendar-mjesec-godina">Siječanj, 2013</TD>

    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 179, Column 49: element "TD" undefined
    		<TD COLSPAN="5" class="kalendar-mjesec-godina">Siječanj, 2013</TD>

    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 180, Column 41: element "TD" undefined
    		<TD class="kalendar-strelica-naprijed">

    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 181, Column 112: required attribute "alt" not specified
    …one;"><img src="http://www.monitor.hr/adminmax/img/system/loading.gif" /></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 185, Column 12: there is no attribute "class"
    	<TR class="kalendar-nazivi-dana">

    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 185, Column 34: element "TR" undefined
    	<TR class="kalendar-nazivi-dana">

    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 187, Column 5: element "TR" undefined
    	<TR>

    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 188, Column 35: element "TD" undefined
    		<TD class="kalendar-prazni-dani">&nbsp;</TD>

    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 189, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 189, Column 45: there is no attribute "HREF"
    …class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013/01/0…

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

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

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

  • Error Line 189, Column 147: end tag for element "A" which is not open
    …i/2013/01/01/" class="kalendar-aktivni-dani-linkovi" target="_blank">1</A></TD>

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

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

  • Error Line 189, Column 152: end tag for "a" omitted, but OMITTAG NO was specified
    …i/2013/01/01/" class="kalendar-aktivni-dani-linkovi" target="_blank">1</A></TD>

    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 189, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 190, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 190, Column 147: end tag for element "A" which is not open
    …i/2013/01/02/" class="kalendar-aktivni-dani-linkovi" target="_blank">2</A></TD>

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

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

  • Error Line 190, Column 152: end tag for "a" omitted, but OMITTAG NO was specified
    …i/2013/01/02/" class="kalendar-aktivni-dani-linkovi" target="_blank">2</A></TD>

    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 190, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 191, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 191, Column 147: end tag for element "A" which is not open
    …i/2013/01/03/" class="kalendar-aktivni-dani-linkovi" target="_blank">3</A></TD>

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

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

  • Error Line 191, Column 152: end tag for "a" omitted, but OMITTAG NO was specified
    …i/2013/01/03/" class="kalendar-aktivni-dani-linkovi" target="_blank">3</A></TD>

    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 191, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 192, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 192, Column 147: end tag for element "A" which is not open
    …i/2013/01/04/" class="kalendar-aktivni-dani-linkovi" target="_blank">4</A></TD>

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

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

  • Error Line 192, Column 152: end tag for "a" omitted, but OMITTAG NO was specified
    …i/2013/01/04/" class="kalendar-aktivni-dani-linkovi" target="_blank">4</A></TD>

    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 192, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 193, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 193, Column 147: end tag for element "A" which is not open
    …i/2013/01/05/" class="kalendar-aktivni-dani-linkovi" target="_blank">5</A></TD>

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

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

  • Error Line 193, Column 152: end tag for "a" omitted, but OMITTAG NO was specified
    …i/2013/01/05/" class="kalendar-aktivni-dani-linkovi" target="_blank">5</A></TD>

    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 193, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 194, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 194, Column 147: end tag for element "A" which is not open
    …i/2013/01/06/" class="kalendar-aktivni-dani-linkovi" target="_blank">6</A></TD>

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

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

  • Error Line 194, Column 152: end tag for "a" omitted, but OMITTAG NO was specified
    …i/2013/01/06/" class="kalendar-aktivni-dani-linkovi" target="_blank">6</A></TD>

    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 194, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 196, Column 5: element "TR" undefined
    	<TR>

    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 197, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 197, Column 147: end tag for element "A" which is not open
    …i/2013/01/07/" class="kalendar-aktivni-dani-linkovi" target="_blank">7</A></TD>

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

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

  • Error Line 197, Column 152: end tag for "a" omitted, but OMITTAG NO was specified
    …i/2013/01/07/" class="kalendar-aktivni-dani-linkovi" target="_blank">7</A></TD>

    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 197, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 198, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 198, Column 147: end tag for element "A" which is not open
    …i/2013/01/08/" class="kalendar-aktivni-dani-linkovi" target="_blank">8</A></TD>

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

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

  • Error Line 198, Column 152: end tag for "a" omitted, but OMITTAG NO was specified
    …i/2013/01/08/" class="kalendar-aktivni-dani-linkovi" target="_blank">8</A></TD>

    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 198, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 199, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 199, Column 147: end tag for element "A" which is not open
    …i/2013/01/09/" class="kalendar-aktivni-dani-linkovi" target="_blank">9</A></TD>

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

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

  • Error Line 199, Column 152: end tag for "a" omitted, but OMITTAG NO was specified
    …i/2013/01/09/" class="kalendar-aktivni-dani-linkovi" target="_blank">9</A></TD>

    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 199, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 200, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 200, Column 148: end tag for element "A" which is not open
    …/2013/01/10/" class="kalendar-aktivni-dani-linkovi" target="_blank">10</A></TD>

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

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

  • Error Line 200, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/10/" class="kalendar-aktivni-dani-linkovi" target="_blank">10</A></TD>

    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 200, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 201, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 201, Column 148: end tag for element "A" which is not open
    …/2013/01/11/" class="kalendar-aktivni-dani-linkovi" target="_blank">11</A></TD>

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

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

  • Error Line 201, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/11/" class="kalendar-aktivni-dani-linkovi" target="_blank">11</A></TD>

    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 201, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 202, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 202, Column 148: end tag for element "A" which is not open
    …/2013/01/12/" class="kalendar-aktivni-dani-linkovi" target="_blank">12</A></TD>

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

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

  • Error Line 202, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/12/" class="kalendar-aktivni-dani-linkovi" target="_blank">12</A></TD>

    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 202, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 203, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 203, Column 148: end tag for element "A" which is not open
    …/2013/01/13/" class="kalendar-aktivni-dani-linkovi" target="_blank">13</A></TD>

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

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

  • Error Line 203, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/13/" class="kalendar-aktivni-dani-linkovi" target="_blank">13</A></TD>

    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 203, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 205, Column 5: element "TR" undefined
    	<TR>

    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 206, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 206, Column 148: end tag for element "A" which is not open
    …/2013/01/14/" class="kalendar-aktivni-dani-linkovi" target="_blank">14</A></TD>

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

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

  • Error Line 206, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/14/" class="kalendar-aktivni-dani-linkovi" target="_blank">14</A></TD>

    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 206, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 207, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 207, Column 148: end tag for element "A" which is not open
    …/2013/01/15/" class="kalendar-aktivni-dani-linkovi" target="_blank">15</A></TD>

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

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

  • Error Line 207, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/15/" class="kalendar-aktivni-dani-linkovi" target="_blank">15</A></TD>

    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 207, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 208, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 208, Column 148: end tag for element "A" which is not open
    …/2013/01/16/" class="kalendar-aktivni-dani-linkovi" target="_blank">16</A></TD>

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

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

  • Error Line 208, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/16/" class="kalendar-aktivni-dani-linkovi" target="_blank">16</A></TD>

    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 208, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 209, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 209, Column 148: end tag for element "A" which is not open
    …/2013/01/17/" class="kalendar-aktivni-dani-linkovi" target="_blank">17</A></TD>

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

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

  • Error Line 209, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/17/" class="kalendar-aktivni-dani-linkovi" target="_blank">17</A></TD>

    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 209, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 210, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 210, Column 148: end tag for element "A" which is not open
    …/2013/01/18/" class="kalendar-aktivni-dani-linkovi" target="_blank">18</A></TD>

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

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

  • Error Line 210, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/18/" class="kalendar-aktivni-dani-linkovi" target="_blank">18</A></TD>

    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 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 211, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 211, Column 148: end tag for element "A" which is not open
    …/2013/01/19/" class="kalendar-aktivni-dani-linkovi" target="_blank">19</A></TD>

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

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

  • Error Line 211, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/19/" class="kalendar-aktivni-dani-linkovi" target="_blank">19</A></TD>

    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 211, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 212, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 212, Column 148: end tag for element "A" which is not open
    …/2013/01/20/" class="kalendar-aktivni-dani-linkovi" target="_blank">20</A></TD>

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

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

  • Error Line 212, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/20/" class="kalendar-aktivni-dani-linkovi" target="_blank">20</A></TD>

    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 212, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 214, Column 5: element "TR" undefined
    	<TR>

    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 215, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 215, Column 148: end tag for element "A" which is not open
    …/2013/01/21/" class="kalendar-aktivni-dani-linkovi" target="_blank">21</A></TD>

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

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

  • Error Line 215, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/21/" class="kalendar-aktivni-dani-linkovi" target="_blank">21</A></TD>

    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 215, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 216, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 216, Column 148: end tag for element "A" which is not open
    …/2013/01/22/" class="kalendar-aktivni-dani-linkovi" target="_blank">22</A></TD>

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

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

  • Error Line 216, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/22/" class="kalendar-aktivni-dani-linkovi" target="_blank">22</A></TD>

    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 216, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 217, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 217, Column 148: end tag for element "A" which is not open
    …/2013/01/23/" class="kalendar-aktivni-dani-linkovi" target="_blank">23</A></TD>

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

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

  • Error Line 217, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/23/" class="kalendar-aktivni-dani-linkovi" target="_blank">23</A></TD>

    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 217, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 218, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 218, Column 148: end tag for element "A" which is not open
    …/2013/01/24/" class="kalendar-aktivni-dani-linkovi" target="_blank">24</A></TD>

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

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

  • Error Line 218, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/24/" class="kalendar-aktivni-dani-linkovi" target="_blank">24</A></TD>

    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 218, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 219, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 219, Column 148: end tag for element "A" which is not open
    …/2013/01/25/" class="kalendar-aktivni-dani-linkovi" target="_blank">25</A></TD>

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

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

  • Error Line 219, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/25/" class="kalendar-aktivni-dani-linkovi" target="_blank">25</A></TD>

    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 219, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 220, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 220, Column 148: end tag for element "A" which is not open
    …/2013/01/26/" class="kalendar-aktivni-dani-linkovi" target="_blank">26</A></TD>

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

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

  • Error Line 220, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/26/" class="kalendar-aktivni-dani-linkovi" target="_blank">26</A></TD>

    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 220, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 221, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 221, Column 148: end tag for element "A" which is not open
    …/2013/01/27/" class="kalendar-aktivni-dani-linkovi" target="_blank">27</A></TD>

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

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

  • Error Line 221, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/27/" class="kalendar-aktivni-dani-linkovi" target="_blank">27</A></TD>

    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 221, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 223, Column 5: element "TR" undefined
    	<TR>

    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 224, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 224, Column 148: end tag for element "A" which is not open
    …/2013/01/28/" class="kalendar-aktivni-dani-linkovi" target="_blank">28</A></TD>

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

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

  • Error Line 224, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/28/" class="kalendar-aktivni-dani-linkovi" target="_blank">28</A></TD>

    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 224, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 225, Column 36: element "TD" undefined
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…

    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 225, Column 148: end tag for element "A" which is not open
    …/2013/01/29/" class="kalendar-aktivni-dani-linkovi" target="_blank">29</A></TD>

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

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

  • Error Line 225, Column 153: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/29/" class="kalendar-aktivni-dani-linkovi" target="_blank">29</A></TD>

    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 225, Column 37: start tag was here
    		<TD class="kalendar-aktivni-dani"><a HREF="http://www.monitor.hr/vijesti/2013…
  • Error Line 226, Column 40: element "TD" undefined
    …	<TD class="kalendar-trenutni-aktivni"><a HREF="http://www.monitor.hr/vijesti/…

    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 226, Column 152: end tag for element "A" which is not open
    …/2013/01/30/" class="kalendar-aktivni-dani-linkovi" target="_blank">30</A></TD>

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

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

  • Error Line 226, Column 157: end tag for "a" omitted, but OMITTAG NO was specified
    …/2013/01/30/" class="kalendar-aktivni-dani-linkovi" target="_blank">30</A></TD>

    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 226, Column 41: start tag was here
    …<TD class="kalendar-trenutni-aktivni"><a HREF="http://www.monitor.hr/vijesti/2…
  • Error Line 227, Column 38: element "TD" undefined
    		<TD class="kalendar-neaktivni-dani">31</TD>

    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 228, Column 35: element "TD" undefined
    		<TD class="kalendar-prazni-dani">&nbsp;</TD>

    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 229, Column 35: element "TD" undefined
    		<TD class="kalendar-prazni-dani">&nbsp;</TD>

    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 230, Column 35: element "TD" undefined
    		<TD class="kalendar-prazni-dani">&nbsp;</TD>

    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 235, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 329, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'+'ipt src="http://ad.hr.doubleclick.net/adj/hr.bk.monitor.…

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

  • Error Line 329, Column 21: element "scr" undefined
    document.write('<scr'+'ipt src="http://ad.hr.doubleclick.net/adj/hr.bk.monitor.…

    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 329, Column 184: delimiter "'" invalid: only S separators and TAGC allowed here
    …copt + ';tile=' + tile + ';sz=300x600;ord=' + cachebuster + '?"></scr'+'ipt>');
  • Error Line 331, Column 941: required attribute "type" not specified
    …ext-align: left"><script src="http://widgets.twimg.com/j/2/widget.js"></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 332, Column 8: required attribute "type" not specified
    <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 367, Column 112: "allowfullscreen" is not a member of a group specified for any attribute
    …://www.youtube.com/embed/JlSQAZEp3PA" frameborder="0" allowfullscreen></iframe>
  • Error Line 374, Column 27: end tag for "div" omitted, but OMITTAG NO was specified
    <!-- OVO NE DIRATI --></dd><dd style="text-align: left"><script type='text/java…

    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 365, Column 1: start tag was here
    <div style="font-size:12px">

Visitor Analysis

Daily Visitor
  • 4.433 visits
Daily Visitor