Editia online a ziarului Jurnalul National ...

jurnalul.ro
  • Domain Name
    jurnalul.ro
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #8999
  • Page Size
    222.1 KB
  • Ip Address
    83.246.1.122
  • Heading
    H1: 0, H2: 91, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 156 JPG, 27 PNG

Website Meta Analysis

  • Title
    Jurnalul National
  • Meta Keyword
  • Meta Description
    Editia online a ziarului Jurnalul National

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    83.246.1.122
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from jurnalul.ro.

HTML Analysis

  • server: nginx
  • date: Wed, 27 Feb 2013 08:29:43 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for jurnalul.ro

DNS Analysis


DNS servers
nsa.jurnalul.ro [194.152.42.160]
nsb.jurnalul.ro [194.152.42.161]

DNS Records

Answer records
jurnalul.ro SOA
server: nsa.jurnalul.ro
email: postmaster@jurnalul.ro
serial: 2012093002
refresh: 10800
retry: 3600
expire: 86400
minimum ttl: 10800
3600s
jurnalul.ro NS  nsb.jurnalul.ro 3600s
jurnalul.ro NS  nsa.jurnalul.ro 3600s
jurnalul.ro A 83.246.1.122 3600s
jurnalul.ro MX
preference: 10
exchange: mail.jurnalul.ro
3600s

Authority records

Additional records
nsa.jurnalul.ro A 194.152.42.160 3600s
nsb.jurnalul.ro A 194.152.42.161 3600s
mail.jurnalul.ro A 194.152.42.226 3600s

IP 83.246.1.122 Analysis

  • Country Code
    RO
  • Country Code3
    ROU
  • Country Name
    Romania
  • City
    Bucharest
  • Continent Code
    EU
  • Latitude
    44.4333
  • Longitude
    26.1.
  • No whois ip data for 83.246.1.122

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 83 Errors
  • 48 Warnings
Ratio Text/Html
  • 0.6998830501916922
Message Error
  • Error Line 29, Column 93: required attribute "type" not specified
    …cript" src="http://jurnalul.ro/static/js/jquery/jquery.mousewheel.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 30, Column 98: required attribute "type" not specified
    …" src="http://jurnalul.ro/static/js/jquery/jquery.jscrollpane.min.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 31, Column 83: required attribute "type" not specified
    …age="javascript" src="http://jurnalul.ro/static/js/jquery/ui.core.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 32, Column 83: required attribute "type" not specified
    …age="javascript" src="http://jurnalul.ro/static/js/jquery/ui.tabs.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 53, Column 16: there is no attribute "property"
    <meta property="fb:admins" content="100000017484825,100000775249415"/>

    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 124, Column 56: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="text" name="q" id="q" value="caută"></form>

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

  • Info Line 124, Column 1: start tag was here
    <input type="text" name="q" id="q" value="caută"></form>
  • Error Line 142, Column 356: end tag for "img" omitted, but OMITTAG NO was specified
    …Marius Tucă: De ziua tatălui meu" title="Marius Tucă: De ziua tatălui meu"></a>

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

  • Info Line 142, Column 193: start tag was here
    …le="Marius Tucă: De ziua tatălui meu"><img src="/thumbs/home/2012/12/21/marius…
  • Error Line 145, Column 780: end tag for "img" omitted, but OMITTAG NO was specified
    …apte, la ora 2:00. Vezi aici zonele vizate de atenţionarea meteorologilor"></a>

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

  • Info Line 145, Column 336: start tag was here
    …izate de atenţionarea meteorologilor"><img src="/thumbs/home/2013/02/25/cod-ga…
  • Error Line 222, Column 45: end tag for "ul" which is not finished
                                            </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Warning Line 246, Column 49: cannot generate system identifier for general entity "Afaceri"
                    	<a href="/bani-afaceri/" >Bani&Afaceri</a>

    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 246, Column 49: general entity "Afaceri" not defined and no default entity
                    	<a href="/bani-afaceri/" >Bani&Afaceri</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.

  • Warning Line 246, Column 56: reference not terminated by REFC delimiter
                    	<a href="/bani-afaceri/" >Bani&Afaceri</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.

  • Error Line 246, Column 56: reference to entity "Afaceri" for which no system identifier could be generated
                    	<a href="/bani-afaceri/" >Bani&Afaceri</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 246, Column 48: entity was defined here
                    	<a href="/bani-afaceri/" >Bani&Afaceri</a>
  • Warning Line 251, Column 106: cannot generate system identifier for general entity "Proprietati"
    … href="/bani-afaceri/constructii-proprietati/">Constructii&Proprietati</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 251, Column 106: general entity "Proprietati" not defined and no default entity
    … href="/bani-afaceri/constructii-proprietati/">Constructii&Proprietati</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 251, Column 117: reference not terminated by REFC delimiter
    … href="/bani-afaceri/constructii-proprietati/">Constructii&Proprietati</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.

  • Error Line 251, Column 117: reference to entity "Proprietati" for which no system identifier could be generated
    … href="/bani-afaceri/constructii-proprietati/">Constructii&Proprietati</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 251, Column 105: entity was defined here
    … href="/bani-afaceri/constructii-proprietati/">Constructii&Proprietati</a></li>
  • Error Line 319, Column 45: end tag for "ul" which is not finished
                                            </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Warning Line 331, Column 78: cannot generate system identifier for general entity "Moto"
    …                             <li><a href="/sport/auto-moto/">Auto&Moto</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 331, Column 78: general entity "Moto" not defined and no default entity
    …                             <li><a href="/sport/auto-moto/">Auto&Moto</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 331, Column 82: reference not terminated by REFC delimiter
    …                             <li><a href="/sport/auto-moto/">Auto&Moto</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.

  • Error Line 331, Column 82: reference to entity "Moto" for which no system identifier could be generated
    …                             <li><a href="/sport/auto-moto/">Auto&Moto</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 331, Column 77: entity was defined here
    …                             <li><a href="/sport/auto-moto/">Auto&Moto</a></li>
  • Error Line 362, Column 45: end tag for "ul" which is not finished
                                            </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 789, Column 29: value of attribute "id" invalid: "1" cannot start a name
                       <div id="1"><a href="/special-jurnalul/reportaje/intalnire-d…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 790, Column 28: value of attribute "id" invalid: "2" cannot start a name
                      <div id="2"><a href="/stiri/observator/cristian-danilet-revoc…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 791, Column 28: value of attribute "id" invalid: "3" cannot start a name
                      <div id="3"><a href="/stiri/observator/greva-judecatrii-revoc…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 792, Column 28: value of attribute "id" invalid: "4" cannot start a name
                      <div id="4"><a href="/stiri/externe/prostie-si-lipsa-de-prega…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 793, Column 28: value of attribute "id" invalid: "5" cannot start a name
                      <div id="5"><a href="/fun/jurnalul-unui-roman-sarac-la-cantin…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 1519, Column 166: reference not terminated by REFC delimiter
    …ss">rss</a><a href="/bani-afaceri/" title="Bani&Afaceri">Bani&Afaceri</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it 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 1519, Column 166: reference to external entity in attribute value
    …ss">rss</a><a href="/bani-afaceri/" title="Bani&Afaceri">Bani&Afaceri</a></div>

    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 1519, Column 166: reference to entity "Afaceri" for which no system identifier could be generated
    …ss">rss</a><a href="/bani-afaceri/" title="Bani&Afaceri">Bani&Afaceri</a></div>

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

  • Info Line 246, Column 48: entity was defined here
                    	<a href="/bani-afaceri/" >Bani&Afaceri</a>
  • Warning Line 1519, Column 180: reference not terminated by REFC delimiter
    …ss">rss</a><a href="/bani-afaceri/" title="Bani&Afaceri">Bani&Afaceri</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it 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 1519, Column 180: reference to entity "Afaceri" for which no system identifier could be generated
    …ss">rss</a><a href="/bani-afaceri/" title="Bani&Afaceri">Bani&Afaceri</a></div>

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

  • Info Line 246, Column 48: entity was defined here
                    	<a href="/bani-afaceri/" >Bani&Afaceri</a>
  • Error Line 1714, Column 148: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4E6F9D0/show.aspx" name="RegistForm" onsubmit="return Validator()" method=post>
  • Error Line 1731, Column 61: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …  <table style="direction:ltr;text-align:left" border=0 class="marginbottom15">
  • Error Line 1733, Column 19: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <td align=left><input type=text id="email" name="email" size=28 value="…
  • Error Line 1733, Column 36: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <td align=left><input type=text id="email" name="email" size=28 value="…
  • Error Line 1733, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …nput type=text id="email" name="email" size=28 value="Adresa ta de email"></td>
  • Error Line 1733, Column 104: end tag for "input" omitted, but OMITTAG NO was specified
    …nput type=text id="email" name="email" size=28 value="Adresa ta de email"></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 1733, Column 24: start tag was here
            <td align=left><input type=text id="email" name="email" size=28 value="…
  • Error Line 1743, Column 124: required attribute "alt" not specified
    …_blank" class="facebook"><img src="/static/images/jn_facebook.png">facebook</a>

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

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

  • Error Line 1743, Column 125: end tag for "img" omitted, but OMITTAG NO was specified
    …_blank" class="facebook"><img src="/static/images/jn_facebook.png">facebook</a>

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

  • Info Line 1743, Column 83: start tag was here
    …lro" target="_blank" class="facebook"><img src="/static/images/jn_facebook.png…
  • Error Line 1744, Column 120: required attribute "alt" not specified
    …t="_blank" class="twitter"><img src="/static/images/jn_twitter.png">twitter</a>

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

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

  • Error Line 1744, Column 121: end tag for "img" omitted, but OMITTAG NO was specified
    …t="_blank" class="twitter"><img src="/static/images/jn_twitter.png">twitter</a>

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

  • Info Line 1744, Column 80: start tag was here
    …ul_n" target="_blank" class="twitter"><img src="/static/images/jn_twitter.png"…
  • Error Line 1745, Column 97: required attribute "alt" not specified
    …arget="_blank" class="rss_sidebar"><img src="/static/images/jn_rss.png">rss</a>

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

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

  • Error Line 1745, Column 98: end tag for "img" omitted, but OMITTAG NO was specified
    …arget="_blank" class="rss_sidebar"><img src="/static/images/jn_rss.png">rss</a>

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

  • Info Line 1745, Column 61: start tag was here
    …" target="_blank" class="rss_sidebar"><img src="/static/images/jn_rss.png">rss…
  • Error Line 1758, Column 40: there is no attribute "data-href"
    …   <div class="fb-like-box" data-href="http://www.facebook.com/jurnalulro" dat…

    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 1758, Column 88: there is no attribute "data-width"
    …w.facebook.com/jurnalulro" data-width="300" data-show-faces="true" data-stream…

    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 1758, Column 110: there is no attribute "data-show-faces"
    …lro" data-width="300" data-show-faces="true" data-stream="false" data-header="…

    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 1758, Column 129: there is no attribute "data-stream"
    …idth="300" data-show-faces="true" data-stream="false" data-header="true"></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 1758, Column 149: there is no attribute "data-header"
    …idth="300" data-show-faces="true" data-stream="false" data-header="true"></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 1765, Column 20: there is no attribute "width"
    &#160;<embed width="300" height="250" menu="true" loop="true" play="true" src="…

    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 1765, Column 33: there is no attribute "height"
    &#160;<embed width="300" height="250" menu="true" loop="true" play="true" src="…

    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 1765, Column 44: there is no attribute "menu"
    …;<embed width="300" height="250" menu="true" loop="true" play="true" src="/med…

    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 1765, Column 56: there is no attribute "loop"
    …h="300" height="250" menu="true" loop="true" play="true" src="/media/flash/ban…

    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 1765, Column 68: there is no attribute "play"
    …ht="250" menu="true" loop="true" play="true" src="/media/flash/banner_BDT.swf"…

    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 1765, Column 79: there is no attribute "src"
    …nu="true" loop="true" play="true" src="/media/flash/banner_BDT.swf" pluginspag…

    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 1765, Column 121: there is no attribute "pluginspage"
    …dia/flash/banner_BDT.swf" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 1765, Column 172: there is no attribute "type"
    …acromedia.com/go/getflashplayer" type="application/x-shockwave-flash"></embed>…

    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 1765, Column 203: element "embed" undefined
    …tflashplayer" type="application/x-shockwave-flash"></embed><!--end div--></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1938, Column 30: required attribute "type" not specified
    <script language="javascript">

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

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

  • Warning Line 1964, Column 178: cannot generate system identifier for general entity "utm_medium"
    …angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+…

    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 1964, Column 178: general entity "utm_medium" not defined and no default entity
    …angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+…

    This is usually a cascading error caused by 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 1964, Column 188: reference not terminated by REFC delimiter
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    If you meant to include an entity that starts with "&", then you should terminate it 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 1964, Column 188: reference to external entity in attribute value
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    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 1964, Column 188: reference to entity "utm_medium" for which no system identifier could be generated
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

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

  • Info Line 1964, Column 177: entity was defined here
    …-angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul…
  • Warning Line 1964, Column 196: cannot generate system identifier for general entity "utm_campaign"
    …_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="R…

    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 1964, Column 196: general entity "utm_campaign" not defined and no default entity
    …_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="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.

  • Warning Line 1964, Column 208: reference not terminated by REFC delimiter
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Razboi intre …

    If you meant to include an entity that starts with "&", then you should terminate it 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 1964, Column 208: reference to external entity in attribute value
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Razboi intre …

    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 1964, Column 208: reference to entity "utm_campaign" for which no system identifier could be generated
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Razboi intre …

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

  • Info Line 1964, Column 195: entity was defined here
    …m_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="…
  • Warning Line 1965, Column 188: reference not terminated by REFC delimiter
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    If you meant to include an entity that starts with "&", then you should terminate it 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 1965, Column 188: reference to external entity in attribute value
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    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 1965, Column 188: reference to entity "utm_medium" for which no system identifier could be generated
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

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

  • Info Line 1964, Column 177: entity was defined here
    …-angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul…
  • Warning Line 1965, Column 208: reference not terminated by REFC delimiter
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National"  onclick="myTrackEve…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1965, Column 208: reference to external entity in attribute value
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National"  onclick="myTrackEve…

    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 1965, Column 208: reference to entity "utm_campaign" for which no system identifier could be generated
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National"  onclick="myTrackEve…

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

  • Info Line 1964, Column 195: entity was defined here
    …m_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="…
  • Warning Line 1965, Column 923: reference not terminated by REFC delimiter
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    If you meant to include an entity that starts with "&", then you should terminate it 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 1965, Column 923: reference to external entity in attribute value
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    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 1965, Column 923: reference to entity "utm_medium" for which no system identifier could be generated
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

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

  • Info Line 1964, Column 177: entity was defined here
    …-angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul…
  • Warning Line 1965, Column 943: reference not terminated by REFC delimiter
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Citește artic…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1965, Column 943: reference to external entity in attribute value
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Citește artic…

    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 1965, Column 943: reference to entity "utm_campaign" for which no system identifier could be generated
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Citește artic…

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

  • Info Line 1964, Column 195: entity was defined here
    …m_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="…
  • Warning Line 1968, Column 174: reference not terminated by REFC delimiter
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    If you meant to include an entity that starts with "&", then you should terminate it 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 1968, Column 174: reference to external entity in attribute value
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    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 1968, Column 174: reference to entity "utm_medium" for which no system identifier could be generated
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

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

  • Info Line 1964, Column 177: entity was defined here
    …-angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul…
  • Warning Line 1968, Column 194: reference not terminated by REFC delimiter
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Livrari la do…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1968, Column 194: reference to external entity in attribute value
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Livrari la do…

    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 1968, Column 194: reference to entity "utm_campaign" for which no system identifier could be generated
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Livrari la do…

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

  • Info Line 1964, Column 195: entity was defined here
    …m_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="…
  • Warning Line 1969, Column 174: reference not terminated by REFC delimiter
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    If you meant to include an entity that starts with "&", then you should terminate it 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 1969, Column 174: reference to external entity in attribute value
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    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 1969, Column 174: reference to entity "utm_medium" for which no system identifier could be generated
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

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

  • Info Line 1964, Column 177: entity was defined here
    …-angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul…
  • Warning Line 1969, Column 194: reference not terminated by REFC delimiter
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National"  onclick="myTrackEve…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1969, Column 194: reference to external entity in attribute value
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National"  onclick="myTrackEve…

    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 1969, Column 194: reference to entity "utm_campaign" for which no system identifier could be generated
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National"  onclick="myTrackEve…

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

  • Info Line 1964, Column 195: entity was defined here
    …m_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="…
  • Warning Line 1969, Column 931: reference not terminated by REFC delimiter
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    If you meant to include an entity that starts with "&", then you should terminate it 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 1969, Column 931: reference to external entity in attribute value
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    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 1969, Column 931: reference to entity "utm_medium" for which no system identifier could be generated
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

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

  • Info Line 1964, Column 177: entity was defined here
    …-angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul…
  • Warning Line 1969, Column 951: reference not terminated by REFC delimiter
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Citește artic…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1969, Column 951: reference to external entity in attribute value
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Citește artic…

    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 1969, Column 951: reference to entity "utm_campaign" for which no system identifier could be generated
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Citește artic…

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

  • Info Line 1964, Column 195: entity was defined here
    …m_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="…
  • Warning Line 1972, Column 187: reference not terminated by REFC delimiter
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    If you meant to include an entity that starts with "&", then you should terminate it 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 1972, Column 187: reference to external entity in attribute value
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    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 1972, Column 187: reference to entity "utm_medium" for which no system identifier could be generated
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

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

  • Info Line 1964, Column 177: entity was defined here
    …-angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul…
  • Warning Line 1972, Column 207: reference not terminated by REFC delimiter
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Rusii de la M…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1972, Column 207: reference to external entity in attribute value
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Rusii de la M…

    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 1972, Column 207: reference to entity "utm_campaign" for which no system identifier could be generated
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Rusii de la M…

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

  • Info Line 1964, Column 195: entity was defined here
    …m_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="…
  • Warning Line 1973, Column 187: reference not terminated by REFC delimiter
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    If you meant to include an entity that starts with "&", then you should terminate it 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 1973, Column 187: reference to external entity in attribute value
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    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 1973, Column 187: reference to entity "utm_medium" for which no system identifier could be generated
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

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

  • Info Line 1964, Column 177: entity was defined here
    …-angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul…
  • Warning Line 1973, Column 207: reference not terminated by REFC delimiter
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National"  onclick="myTrackEve…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1973, Column 207: reference to external entity in attribute value
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National"  onclick="myTrackEve…

    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 1973, Column 207: reference to entity "utm_campaign" for which no system identifier could be generated
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National"  onclick="myTrackEve…

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

  • Info Line 1964, Column 195: entity was defined here
    …m_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="…
  • Warning Line 1973, Column 955: reference not terminated by REFC delimiter
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    If you meant to include an entity that starts with "&", then you should terminate it 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 1973, Column 955: reference to external entity in attribute value
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

    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 1973, Column 955: reference to entity "utm_medium" for which no system identifier could be generated
    …html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" …

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

  • Info Line 1964, Column 177: entity was defined here
    …-angajatii.html?utm_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul…
  • Warning Line 1973, Column 975: reference not terminated by REFC delimiter
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Citește artic…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1973, Column 975: reference to external entity in attribute value
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Citește artic…

    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 1973, Column 975: reference to entity "utm_campaign" for which no system identifier could be generated
    …eneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="Citește artic…

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

  • Info Line 1964, Column 195: entity was defined here
    …m_source=parteneriat&utm_medium=widget&utm_campaign=Jurnalul+National" title="…
  • Warning Line 2123, Column 67: reference not terminated by REFC delimiter
    …                   <a href="/bani-afaceri/" >Bani&Afaceri</a>&nbsp;&nbsp;&nbsp;

    If you meant to include an entity that starts with "&", then you should terminate it 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 2123, Column 67: reference to entity "Afaceri" for which no system identifier could be generated
    …                   <a href="/bani-afaceri/" >Bani&Afaceri</a>&nbsp;&nbsp;&nbsp;

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

  • Info Line 246, Column 48: entity was defined here
                    	<a href="/bani-afaceri/" >Bani&Afaceri</a>
  • Error Line 2137, Column 69: end tag for "input" omitted, but OMITTAG NO was specified
                    <input type="hidden" value="cautare" name="section">

    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 2137, Column 17: start tag was here
                    <input type="hidden" value="cautare" name="section">
  • Error Line 2138, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
                    <input type="hidden" value="index" name="screen">

    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 2138, Column 17: start tag was here
                    <input type="hidden" value="index" name="screen">
  • Error Line 2139, Column 222: end tag for "input" omitted, but OMITTAG NO was specified
    …l.ro') this.value=''" name="q" value="Căutare în jurnalul.ro" class="inp_text">

    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 2139, Column 17: start tag was here
                    <input type="text" onblur="if(this.value=='') this.value='Căuta…
  • Error Line 2140, Column 63: end tag for "input" omitted, but OMITTAG NO was specified
                    <input type="submit" value="" class="trimite">

    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 2140, Column 17: start tag was here
                    <input type="submit" value="" class="trimite">
  • Error Line 2174, 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 2347, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    …mg src="/static/images/netvibes.jpg" alt="Netvibes" title="Netvibes"></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 2347, Column 98: start tag was here
    ….ro" target="_blank" title="Netvibes"><img src="/static/images/netvibes.jpg" a…
  • Error Line 2348, Column 161: end tag for element "center" which is not open
    …blank">INTACT MEDIA GROUP</a></div><div></center><div class="desp_s"></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 2354, Column 198: required attribute "alt" not specified
    …g src="/static/images/inwise_logo.png" style="vertical-align:middle"></a></div>

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

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

  • Error Line 2354, Column 202: end tag for "img" omitted, but OMITTAG NO was specified
    …g src="/static/images/inwise_logo.png" style="vertical-align:middle"></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 2354, Column 127: start tag was here
    …f="http://inwise.ro/" target="_blank"><img src="/static/images/inwise_logo.png…
  • Error Line 2366, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 2238, Column 1: start tag was here
    <div class="footer_facelift"><div class="footer_links_container">
  • Error Line 2366, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 2237, Column 1: start tag was here
    <div style="background-color:#FFF">

Visitor Analysis

Daily Visitor
  • 18.667 visits
Daily Visitor