CRM Integration Survey Software Sectiunea principala English| [Română] eNewsletter   Personal Business Centrul de presă Companie Cariere Asistenţa Serviciul Plăţi Webcare    Personal Abonamente COSMOTE Comunică mai mult! COSMOTE Pentru Tine ... ...

cosmote.ro
  • Domain Name
    cosmote.ro
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #73084
  • Page Size
    38.2 KB
  • Ip Address
    85.121.35.71
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    28 GIF, 15 JPG, 0 PNG

Website Meta Analysis

  • Title
    COSMOTE Personal
  • Meta Keyword
  • Meta Description
    CRM Integration Survey Software Sectiunea principala English| [Română] eNewsletter   Personal Business Centrul de presă Companie Cariere Asistenţa Serviciul Plăţi Webcare    Personal Abonamente COSMOTE Comunică mai mult! COSMOTE Pentru Tine ...

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    85.121.35.71
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 12 Aug 2013 12:06:41 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • x-aspnet-version: 1.1.4322
  • cache-control: private
  • content-type: text/html; charset=iso-8859-2
  • content-length: 33482
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for cosmote.ro

DNS Analysis


DNS servers
ns-a.cosmote.ro [85.121.35.118]
ns.cosmote.ro [194.153.238.132]
ns-b.cosmote.ro [194.153.238.28]


DNS Records

Answer records
cosmote.ro A 85.121.35.71 3600s
cosmote.ro NS  ns.cosmote.ro 3600s
cosmote.ro NS  ns-b.cosmote.ro 3600s
cosmote.ro NS  ns-a.cosmote.ro 3600s
cosmote.ro SOA
server: ns-b.cosmote.ro
email: hostmaster@cosmote.ro
serial: 2006101447
refresh: 1800
retry: 600
expire: 1209600
minimum ttl: 3600
3600s
cosmote.ro MX
preference: 10
exchange: mail1.cosmote.ro
3600s
cosmote.ro MX
preference: 20
exchange: mail.cosmote.ro
3600s
cosmote.ro TXT v=spf1 mx include:return8.com -all 3600s

Authority records

Additional records
ns.cosmote.ro A 194.153.238.132 3600s
ns-b.cosmote.ro A 194.153.238.28 3600s
ns-a.cosmote.ro A 85.121.35.118 3600s
mail1.cosmote.ro A 85.121.35.5 3600s
mail.cosmote.ro A 194.153.238.6 3600s

IP 85.121.35.71 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 85.121.35.71

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 207 Errors
  • 46 Warnings
Ratio Text/Html
  • 0.7383624325775199
Message Error
  • Error Line 5, Column 13: there is no attribute "ID"
    		<title id="pageTitle">COSMOTE Personal</title>

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

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

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

  • Warning Line 25, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …rm-integration">CRM Integration</a><br/><a target="_blank" href="http://www.qu…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 25, Column 191: NET-enabling start-tag requires SHORTTAG YES
    …="http://www.qualtrics.com/survey-software">Survey Software</a><br/></noscript>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 47, Column 8: end tag for element "HEAD" which is not open
    	</HEAD>

    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 48, Column 19: there is no attribute "LEFTMARGIN"
    	<BODY leftMargin="0" topMargin="0" bgColor="#cbd7d1">

    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 48, Column 33: there is no attribute "TOPMARGIN"
    	<BODY leftMargin="0" topMargin="0" bgColor="#cbd7d1">

    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 48, Column 54: document type does not allow element "BODY" here
    	<BODY leftMargin="0" topMargin="0" bgColor="#cbd7d1">

    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 51, Column 60: required attribute "TYPE" not specified
    <script language="Javascript" src="/script/formValidate.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 54, Column 65: end tag for "TR" which is not finished
    		<!--<TD bgColor="#97c137" height="19" colspan="3"></TD>--></TR>

    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 90, Column 65: end tag for "TR" which is not finished
    		<!--<TD bgColor="#97c137" height="19" colspan="3"></TD>--></TR>

    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 98, Column 6: end tag for element "A" which is not open
    		</A></B></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 98, Column 10: end tag for element "B" which is not open
    		</A></B></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 98, Column 15: end tag for element "TD" which is not open
    		</A></B></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.

  • Warning Line 114, Column 91: cannot generate system identifier for general entity "ns"
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span…

    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 114, Column 91: general entity "ns" not defined and no default entity
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span…

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

  • Error Line 114, Column 93: reference to entity "ns" for which no system identifier could be generated
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Warning Line 114, Column 101: cannot generate system identifier for general entity "cid"
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>

    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 114, Column 101: general entity "cid" not defined and no default entity
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>

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

  • Error Line 114, Column 104: reference to entity "cid" for which no system identifier could be generated
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Error Line 124, Column 11: there is no attribute "HEIGHT"
    			height="550">

    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 128, Column 98: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 177: reference to entity "ns" for which no system identifier could be generated
    …ef='contractplans.aspx?style=styles&ns=-10000&cid=17072'> <IMG height=64 src=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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 188: reference to entity "cid" for which no system identifier could be generated
    …tplans.aspx?style=styles&ns=-10000&cid=17072'> <IMG height=64 src=http://www.c…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 221: NET-enabling start-tag requires SHORTTAG YES
    …0&cid=17072'> <IMG height=64 src=http://www.cosmote.ro/ro/images/connection_pr…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 221: required attribute "ALT" not specified
    …0&cid=17072'> <IMG height=64 src=http://www.cosmote.ro/ro/images/connection_pr…

    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 128, Column 389: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 389: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 489: reference to entity "ns" for which no system identifier could be generated
    …ef='contractplans.aspx?style=styles&ns=-10000&cid=17072'>Abonamente COSMOTE</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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 500: reference to entity "cid" for which no system identifier could be generated
    …tplans.aspx?style=styles&ns=-10000&cid=17072'>Abonamente COSMOTE</a></span><br…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 541: NET-enabling start-tag requires SHORTTAG YES
    …072'>Abonamente COSMOTE</a></span><br />Comunică mai mult!</td></tr></table><t…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 640: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 713: reference to entity "ns" for which no system identifier could be generated
    …><a href='loyalty.aspx?style=styles&ns=-10000&cid=19362'> <IMG height=64 src=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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 724: reference to entity "cid" for which no system identifier could be generated
    …oyalty.aspx?style=styles&ns=-10000&cid=19362'> <IMG height=64 src=http://www.c…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 757: NET-enabling start-tag requires SHORTTAG YES
    …0&cid=19362'> <IMG height=64 src=http://www.cosmote.ro/ro/images/c_care_ypires…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 757: required attribute "ALT" not specified
    …0&cid=19362'> <IMG height=64 src=http://www.cosmote.ro/ro/images/c_care_ypires…

    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 128, Column 920: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 920: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 1014: reference to entity "ns" for which no system identifier could be generated
    …><a href='loyalty.aspx?style=styles&ns=-10000&cid=19362'>COSMOTE Pentru Tine</…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 1025: reference to entity "cid" for which no system identifier could be generated
    …oyalty.aspx?style=styles&ns=-10000&cid=19362'>COSMOTE Pentru Tine</a></span><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.

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 1067: NET-enabling start-tag requires SHORTTAG YES
    …62'>COSMOTE Pentru Tine</a></span><br />Tot ce ai nevoie şi chiar mai mult!</t…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 1183: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 1264: reference to entity "ns" for which no system identifier could be generated
    …='PrepaidPlanHome.aspx?style=styles&ns=-10000&cid=17226'> <IMG height=64 src=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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 1275: reference to entity "cid" for which no system identifier could be generated
    …anHome.aspx?style=styles&ns=-10000&cid=17226'> <IMG height=64 src=http://www.c…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 1308: NET-enabling start-tag requires SHORTTAG YES
    …0&cid=17226'> <IMG height=64 src=http://www.cosmote.ro/ro/images/left_cosmokar…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 1308: required attribute "ALT" not specified
    …0&cid=17226'> <IMG height=64 src=http://www.cosmote.ro/ro/images/left_cosmokar…

    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 128, Column 1470: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 1470: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 1572: reference to entity "ns" for which no system identifier could be generated
    …='PrepaidPlanHome.aspx?style=styles&ns=-10000&cid=17226'>Cartela COSMOTE</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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 1583: reference to entity "cid" for which no system identifier could be generated
    …anHome.aspx?style=styles&ns=-10000&cid=17226'>Cartela COSMOTE</a></span><br />…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 1621: NET-enabling start-tag requires SHORTTAG YES
    …=17226'>Cartela COSMOTE</a></span><br />Adună-i pe toţi!</td></tr></table><tab…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 1718: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 1790: reference to entity "ns" for which no system identifier could be generated
    …'><a href='iPhone.aspx?style=styles&ns=-10000&cid=20250'> <IMG border=0 src=ht…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 1801: reference to entity "cid" for which no system identifier could be generated
    …iPhone.aspx?style=styles&ns=-10000&cid=20250'> <IMG border=0 src=http://www.co…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 1833: NET-enabling start-tag requires SHORTTAG YES
    …00&cid=20250'> <IMG border=0 src=http://www.cosmote.ro/ro/images/iPhone_menu.j…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 1833: required attribute "ALT" not specified
    …00&cid=20250'> <IMG border=0 src=http://www.cosmote.ro/ro/images/iPhone_menu.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>.

  • Warning Line 128, Column 1992: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 1992: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 2085: reference to entity "ns" for which no system identifier could be generated
    …'><a href='iPhone.aspx?style=styles&ns=-10000&cid=20250'>iPhone</a></span><br …

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 2096: reference to entity "cid" for which no system identifier could be generated
    …iPhone.aspx?style=styles&ns=-10000&cid=20250'>iPhone</a></span><br />Noul iPho…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 2125: NET-enabling start-tag requires SHORTTAG YES
    …10000&cid=20250'>iPhone</a></span><br />Noul iPhone 5 este acum disponibil. Af…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 2257: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 2330: reference to entity "ns" for which no system identifier could be generated
    …><a href='display.aspx?style=styles&ns=-10000&cid=17082'> <IMG height=64 src=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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 2341: reference to entity "cid" for which no system identifier could be generated
    …isplay.aspx?style=styles&ns=-10000&cid=17082'> <IMG height=64 src=http://www.c…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 2374: NET-enabling start-tag requires SHORTTAG YES
    …0&cid=17082'> <IMG height=64 src=http://www.cosmote.ro/ro/images/handsets.jpg …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 2374: required attribute "ALT" not specified
    …0&cid=17082'> <IMG height=64 src=http://www.cosmote.ro/ro/images/handsets.jpg …

    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 128, Column 2529: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 2529: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 2623: reference to entity "ns" for which no system identifier could be generated
    …><a href='display.aspx?style=styles&ns=-10000&cid=17082'>Telefoane</a></span><…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 2634: reference to entity "cid" for which no system identifier could be generated
    …isplay.aspx?style=styles&ns=-10000&cid=17082'>Telefoane</a></span><br />COSMOT…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 2666: NET-enabling start-tag requires SHORTTAG YES
    …00&cid=17082'>Telefoane</a></span><br />COSMOTE vă propune telefonul...</td></…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 2778: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 2861: reference to entity "ns" for which no system identifier could be generated
    …connectMobileHome.aspx?style=styles&ns=-10000&cid=20368'> <IMG height=64 src=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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 2872: reference to entity "cid" for which no system identifier could be generated
    …leHome.aspx?style=styles&ns=-10000&cid=20368'> <IMG height=64 src=http://www.c…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 2905: NET-enabling start-tag requires SHORTTAG YES
    …0&cid=20368'> <IMG height=64 src=http://www.cosmote.ro/ro/images/icon_Connect_…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 2905: required attribute "ALT" not specified
    …0&cid=20368'> <IMG height=64 src=http://www.cosmote.ro/ro/images/icon_Connect_…

    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 128, Column 3071: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 3071: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 3175: reference to entity "ns" for which no system identifier could be generated
    …connectMobileHome.aspx?style=styles&ns=-10000&cid=20368'>Internet pe mobil</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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 3186: reference to entity "cid" for which no system identifier could be generated
    …leHome.aspx?style=styles&ns=-10000&cid=20368'>Internet pe mobil</a></span><br …

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 3226: NET-enabling start-tag requires SHORTTAG YES
    …0368'>Internet pe mobil</a></span><br />Ia internetul cu tine oriunde ai merge…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 3346: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 3424: reference to entity "ns" for which no system identifier could be generated
    …ref='connectHome1.aspx?style=styles&ns=-10000&cid=20088'> <P class=maintext><I…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 3435: reference to entity "cid" for which no system identifier could be generated
    …tHome1.aspx?style=styles&ns=-10000&cid=20088'> <P class=maintext><IMG border=0…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Error Line 128, Column 3461: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …s=-10000&cid=20088'> <P class=maintext><IMG border=0 src=http://www.cosmote.ro…

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

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

  • Warning Line 128, Column 3485: NET-enabling start-tag requires SHORTTAG YES
    …class=maintext><IMG border=0 src=http://www.cosmote.ro/ro/images/connect_icon.…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 3485: required attribute "ALT" not specified
    …class=maintext><IMG border=0 src=http://www.cosmote.ro/ro/images/connect_icon.…

    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 128, Column 3650: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 3650: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 3749: reference to entity "ns" for which no system identifier could be generated
    …ref='connectHome1.aspx?style=styles&ns=-10000&cid=20088'>Internet pe laptop şi…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 3760: reference to entity "cid" for which no system identifier could be generated
    …tHome1.aspx?style=styles&ns=-10000&cid=20088'>Internet pe laptop şi tabletă</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 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 3812: NET-enabling start-tag requires SHORTTAG YES
    …et pe laptop şi tabletă</a></span><br />Internet mobil cu viteza de până la 43…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 3969: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 4042: reference to entity "ns" for which no system identifier could be generated
    …><a href='muziton.aspx?style=styles&ns=-10000&cid=19630'> <IMG height=64 src=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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 4053: reference to entity "cid" for which no system identifier could be generated
    …uziton.aspx?style=styles&ns=-10000&cid=19630'> <IMG height=64 src=http://www.c…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 4086: NET-enabling start-tag requires SHORTTAG YES
    …0&cid=19630'> <IMG height=64 src=http://www.cosmote.ro/ro/images/muziton.gif w…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 4086: required attribute "ALT" not specified
    …0&cid=19630'> <IMG height=64 src=http://www.cosmote.ro/ro/images/muziton.gif w…

    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 128, Column 4240: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 4240: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 4334: reference to entity "ns" for which no system identifier could be generated
    …><a href='muziton.aspx?style=styles&ns=-10000&cid=19630'>Muziton</a></span><br…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 4345: reference to entity "cid" for which no system identifier could be generated
    …uziton.aspx?style=styles&ns=-10000&cid=19630'>Muziton</a></span><br />Înlocuie…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 4375: NET-enabling start-tag requires SHORTTAG YES
    …0000&cid=19630'>Muziton</a></span><br />Înlocuieşte monoton cu muziton!</td></…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 4487: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 4564: reference to entity "ns" for which no system identifier could be generated
    …href='portability.aspx?style=styles&ns=-10000&cid=19685'> <P class=maintext><I…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 4575: reference to entity "cid" for which no system identifier could be generated
    …bility.aspx?style=styles&ns=-10000&cid=19685'> <P class=maintext><IMG height=6…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Error Line 128, Column 4601: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …s=-10000&cid=19685'> <P class=maintext><IMG height=62 src=http://www.cosmote.r…

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

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

  • Warning Line 128, Column 4626: NET-enabling start-tag requires SHORTTAG YES
    …lass=maintext><IMG height=62 src=http://www.cosmote.ro/ro/images/buton_portabi…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 4626: required attribute "ALT" not specified
    …lass=maintext><IMG height=62 src=http://www.cosmote.ro/ro/images/buton_portabi…

    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 128, Column 4796: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 4796: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 4894: reference to entity "ns" for which no system identifier could be generated
    …href='portability.aspx?style=styles&ns=-10000&cid=19685'>Portabilitate</a></sp…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 4905: reference to entity "cid" for which no system identifier could be generated
    …bility.aspx?style=styles&ns=-10000&cid=19685'>Portabilitate</a></span><br />Ia…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 4941: NET-enabling start-tag requires SHORTTAG YES
    …id=19685'>Portabilitate</a></span><br />Ia numărul de telefon cu tine oriunde …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 5069: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 5145: reference to entity "ns" for which no system identifier could be generated
    … href='blackberry.aspx?style=styles&ns=-10000&cid=20001'> <P class=maintext><I…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 5156: reference to entity "cid" for which no system identifier could be generated
    …kberry.aspx?style=styles&ns=-10000&cid=20001'> <P class=maintext><IMG height=6…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Error Line 128, Column 5182: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …s=-10000&cid=20001'> <P class=maintext><IMG height=64 src=http://www.cosmote.r…

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

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

  • Warning Line 128, Column 5207: NET-enabling start-tag requires SHORTTAG YES
    …lass=maintext><IMG height=64 src=http://www.cosmote.ro/ro/images/BB_b_final.gi…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 5207: required attribute "ALT" not specified
    …lass=maintext><IMG height=64 src=http://www.cosmote.ro/ro/images/BB_b_final.gi…

    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 128, Column 5368: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 5368: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 5465: reference to entity "ns" for which no system identifier could be generated
    … href='blackberry.aspx?style=styles&ns=-10000&cid=20001'>BlackBerry</a></span>…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 5476: reference to entity "cid" for which no system identifier could be generated
    …kberry.aspx?style=styles&ns=-10000&cid=20001'>BlackBerry</a></span><br />Cu so…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 5509: NET-enabling start-tag requires SHORTTAG YES
    …0&cid=20001'>BlackBerry</a></span><br />Cu soluţia BlackBerry de la Cosmote ai…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 5664: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …er='0' cellpadding='0' cellspacing='0'><tr valign='middle'><td width='65'><a h…

    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 128, Column 5748: reference to entity "ns" for which no system identifier could be generated
    …obileApplications.aspx?style=styles&ns=-10000&cid=20995'> <IMG border=0 src=ht…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 5759: reference to entity "cid" for which no system identifier could be generated
    …ations.aspx?style=styles&ns=-10000&cid=20995'> <IMG border=0 src=http://www.co…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 5791: NET-enabling start-tag requires SHORTTAG YES
    …00&cid=20995'> <IMG border=0 src=http://www.cosmote.ro/ro/images/resources/ico…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 5791: required attribute "ALT" not specified
    …00&cid=20995'> <IMG border=0 src=http://www.cosmote.ro/ro/images/resources/ico…

    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 128, Column 5963: NET-enabling start-tag requires SHORTTAG YES
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 5963: required attribute "ALT" not specified
    …ges/spacer.gif' width='15' height='1' /></td><td width='160'><span class='sub-…

    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 128, Column 6068: reference to entity "ns" for which no system identifier could be generated
    …obileApplications.aspx?style=styles&ns=-10000&cid=20995'>Aplicatii</a></span><…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 128, Column 6079: reference to entity "cid" for which no system identifier could be generated
    …ations.aspx?style=styles&ns=-10000&cid=20995'>Aplicatii</a></span><br /><FONT …

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 128, Column 6111: NET-enabling start-tag requires SHORTTAG YES
    …00&cid=20995'>Aplicatii</a></span><br /><FONT color=#000000>Divertisment oriun…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 128, Column 6125: an attribute value must be a literal unless it contains only name characters
    …Aplicatii</a></span><br /><FONT color=#000000>Divertisment oriunde!</FONT></td…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 134, Column 66: required attribute "ALT" not specified
    		<td><img src="images/resources/spacer.gif" width="1" height="1"></td>

    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 140, Column 86: required attribute "ALT" not specified
    …"mycosmos-bg"><img src="images/resources/spacer.gif" width="1" height="7"></td>

    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 143, Column 66: required attribute "ALT" not specified
    		<td><img src='images/resources/spacer.gif' width='1' height='5'></td>

    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 149, Column 187: "VIEWASTEXT" is not a member of a group specified for any attribute
    …540000 width=240 height=290 VIEWASTEXT><PARAM NAME="_cx" VALUE="12700"><PARAM …
  • Error Line 150, Column 61: there is no attribute "SRC"
    …                           <embed src="http://www.cosmote.ro/ro/flash/Catalog_…

    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 150, Column 140: there is no attribute "QUALITY"
    …osmote_Februarie_240x290.swf" quality="high" pluginspage="http://www.macromedi…

    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 150, Column 159: there is no attribute "PLUGINSPAGE"
    …0x290.swf" quality="high" 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 150, Column 210: there is no attribute "TYPE"
    …acromedia.com/go/getflashplayer" type="application/x-shockwave-flash" width="2…

    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 150, Column 248: there is no attribute "WIDTH"
    …"application/x-shockwave-flash" width="240" height="290" menu="true" wmode="tr…

    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 150, Column 261: there is no attribute "HEIGHT"
    …x-shockwave-flash" width="240" height="290" menu="true" wmode="transparent"></…

    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 150, Column 272: there is no attribute "MENU"
    …-flash" width="240" height="290" menu="true" wmode="transparent"></embed></OBJ…

    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 150, Column 285: there is no attribute "WMODE"
    …ash" width="240" height="290" menu="true" wmode="transparent"></embed></OBJECT>

    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 150, Column 298: element "EMBED" undefined
    …ash" width="240" height="290" menu="true" wmode="transparent"></embed></OBJECT>

    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 152, Column 98: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …LeftPlaceholder_content"><TABLE cellSpacing=0 cellPadding=0 width=242 border=0>

    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 156, Column 57: there is no attribute "BACKGROUND"
    …=0 cellPadding=0 width=242 background=http://www.cosmote.ro/en/images/resource…

    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 156, Column 62: NET-enabling start-tag requires SHORTTAG YES
    …llPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/tea…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 156, Column 62: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …llPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/tea…

    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 156, Column 63: end tag for "TABLE" which is not finished
    …lPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/teas…

    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 156, Column 63: end tag for "TABLE" which is not finished
    …lPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/teas…

    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 157, Column 22: document type does not allow element "TBODY" here
    <TBODY class=maintext>

    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 161, Column 11: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
    <TD align=middle width=80 height=81><IMG height=65 src="http://www.cosmote.ro/r…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 161, Column 127: required attribute "ALT" not specified
    …c="http://www.cosmote.ro/ro/images/resources/Icon-Folder_3D.jpg" width=65></TD>

    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 162, Column 52: an attribute value must be a literal unless it contains only name characters
    …ck width=154 height=68><B><FONT color=#8cc63e>Descarca</FONT></B><BR><A href="…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 165, Column 60: end tag for "SPAN" omitted, but its declaration does not permit this
    <TD width=242 colSpan=3 height=10></TD></TR></TBODY></TABLE>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 152, Column 6: start tag was here
    					<span id="MainLeftPlaceholder_content"><TABLE cellSpacing=0 cellPadding=0 …
  • Warning Line 170, Column 62: NET-enabling start-tag requires SHORTTAG YES
    …llPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/tea…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 170, Column 63: end tag for "TABLE" which is not finished
    …lPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/teas…

    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 170, Column 63: end tag for "TABLE" which is not finished
    …lPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/teas…

    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 171, Column 22: document type does not allow element "TBODY" here; assuming missing "TABLE" start-tag
    <TBODY class=maintext>
  • Error Line 175, Column 11: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
    <TD align=middle width=80 height=68><IMG height=65 src="http://www.cosmote.ro/e…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 175, Column 120: required attribute "ALT" not specified
    …t=65 src="http://www.cosmote.ro/en/images/resources/network.jpg" width=65></TD>

    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 176, Column 52: an attribute value must be a literal unless it contains only name characters
    …ck width=154 height=68><B><FONT color=#8cc63e>Reţeaua noastră</FONT></B><BR><A…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 180, Column 7: end tag for element "SPAN" which is not open
    </span>

    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 9: end tag for element "TD" which is not open
    				</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 51: document type does not allow element "TD" here
    				<TD vAlign="top" width="538" id="content_main">

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

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

  • Warning Line 205, Column 168: NET-enabling start-tag requires SHORTTAG YES
    …ner Availability Iphone 5" width="500" height="251" border="0" usemap="#Map" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 207, Column 101: reference to entity "cid" for which no system identifier could be generated
    …osmote.ro/ro/iPhone.aspx?ns=-10000&cid=20250&p=3" target="_blank" alt="view of…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Warning Line 207, Column 108: cannot generate system identifier for general entity "p"
    ….ro/ro/iPhone.aspx?ns=-10000&cid=20250&p=3" target="_blank" alt="view offer" />

    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 207, Column 108: general entity "p" not defined and no default entity
    ….ro/ro/iPhone.aspx?ns=-10000&cid=20250&p=3" target="_blank" alt="view offer" />

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

  • Error Line 207, Column 109: reference to entity "p" for which no system identifier could be generated
    ….ro/ro/iPhone.aspx?ns=-10000&cid=20250&p=3" target="_blank" alt="view offer" />

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

  • Info Line 207, Column 107: entity was defined here
    ….ro/ro/iPhone.aspx?ns=-10000&cid=20250&p=3" target="_blank" alt="view offer" /…
  • Warning Line 207, Column 146: NET-enabling start-tag requires SHORTTAG YES
    ….ro/ro/iPhone.aspx?ns=-10000&cid=20250&p=3" target="_blank" alt="view offer" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 207, Column 147: character data is not allowed here
    ….ro/ro/iPhone.aspx?ns=-10000&cid=20250&p=3" target="_blank" alt="view offer" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 208, Column 165: NET-enabling start-tag requires SHORTTAG YES
    …x?style=styles&amp;ns=-10000&amp;cid=20250" target="_blank" alt="Learn More" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 209, Column 10: NET-enabling start-tag requires SHORTTAG YES
    </map><br/><br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 209, Column 15: NET-enabling start-tag requires SHORTTAG YES
    </map><br/><br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 209, Column 20: NET-enabling start-tag requires SHORTTAG YES
    </map><br/><br/><br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 236, Column 13: invalid comment declaration: found name start character outside comment but inside comment declaration
    								<!--banner-->
  • Info Line 215, Column 9: comment declaration started here
    								<!--banner	
  • Error Line 238, Column 98: "VIEWASTEXT" is not a member of a group specified for any attribute
    …lsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="500" height="240" VIEWASTEXT>
  • Error Line 265, Column 72: element "EMBED" undefined
    …								type="application/x-shockwave-flash" width="500" height="240"> </embed>

    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 314, Column 31: there is no attribute "ONMOUSEOVER"
    									<marquee onmouseover="this.stop();" onmouseout="this.start();" scrollA…

    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 314, Column 57: there is no attribute "ONMOUSEOUT"
    …onmouseover="this.stop();" onmouseout="this.start();" scrollAmount="2" scrollD…

    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 314, Column 86: there is no attribute "SCROLLAMOUNT"
    …er="this.stop();" onmouseout="this.start();" scrollAmount="2" scrollDelay="110"

    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 314, Column 102: there is no attribute "SCROLLDELAY"
    …er="this.stop();" onmouseout="this.start();" scrollAmount="2" scrollDelay="110"

    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 315, Column 21: there is no attribute "DIRECTION"
    										direction="up" behavior="scroll" loop="0" width="231" height="70"><sp…

    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 315, Column 35: there is no attribute "BEHAVIOR"
    										direction="up" behavior="scroll" loop="0" width="231" height="70"><sp…

    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 315, Column 49: there is no attribute "LOOP"
    …direction="up" behavior="scroll" loop="0" width="231" height="70"><span id="Ne…

    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 315, Column 59: there is no attribute "WIDTH"
    …"up" behavior="scroll" loop="0" width="231" height="70"><span id="Newstickerfo…

    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 315, Column 72: there is no attribute "HEIGHT"
    …="scroll" loop="0" width="231" height="70"><span id="Newstickerforyou1_marqbod…

    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 315, Column 76: element "MARQUEE" undefined
    …roll" loop="0" width="231" height="70"><span id="Newstickerforyou1_marqbody"><…

    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 315, Column 209: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …o; borderWidth: 1; borderColor: white"><a  href="/ro/content.aspx?style=styles…

    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 315, Column 252: reference to entity "ns" for which no system identifier could be generated
    …href="/ro/content.aspx?style=styles&ns=-10000&amp;cid=20826" >ATENTIE! Pagina …

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 315, Column 457: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …o; borderWidth: 1; borderColor: white"><a  href="/ro/content.aspx?style=styles…

    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 315, Column 500: reference to entity "ns" for which no system identifier could be generated
    …href="/ro/content.aspx?style=styles&ns=-10000&amp;cid=20358" >Mesajele tale de…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 315, Column 796: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …o; borderWidth: 1; borderColor: white"><a  href="/ro/content.aspx?style=styles…

    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 315, Column 839: reference to entity "ns" for which no system identifier could be generated
    …href="/ro/content.aspx?style=styles&ns=-10000&amp;cid=20143" >Ghid de informat…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 315, Column 1089: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …o; borderWidth: 1; borderColor: white"><a  href="/ro/content.aspx?style=styles…

    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 315, Column 1132: reference to entity "ns" for which no system identifier could be generated
    …href="/ro/content.aspx?style=styles&ns=-10000&amp;cid=20071" >Campanie promoti…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 315, Column 1314: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …o; borderWidth: 1; borderColor: white"><a  href="/ro/content.aspx?style=styles…

    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 315, Column 1357: reference to entity "ns" for which no system identifier could be generated
    …href="/ro/content.aspx?style=styles&ns=-10000&noparent=19829&amp;cid=19909" >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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Warning Line 315, Column 1365: cannot generate system identifier for general entity "noparent"
    …o/content.aspx?style=styles&ns=-10000&noparent=19829&amp;cid=19909" >Tari ale …

    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 315, Column 1365: general entity "noparent" not defined and no default entity
    …o/content.aspx?style=styles&ns=-10000&noparent=19829&amp;cid=19909" >Tari ale …

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

  • Error Line 315, Column 1373: reference to entity "noparent" for which no system identifier could be generated
    …t.aspx?style=styles&ns=-10000&noparent=19829&amp;cid=19909" >Tari ale UE pentr…

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

  • Info Line 315, Column 1364: entity was defined here
    …ro/content.aspx?style=styles&ns=-10000&noparent=19829&amp;cid=19909" >Tari ale…
  • Error Line 315, Column 1613: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …o; borderWidth: 1; borderColor: white"><a  href="/ro/content.aspx?style=styles…

    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 315, Column 1656: reference to entity "ns" for which no system identifier could be generated
    …href="/ro/content.aspx?style=styles&ns=-10000&amp;cid=18792" >În urma semnală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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 315, Column 1891: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …o; borderWidth: 1; borderColor: white"><a  href="/ro/content.aspx?style=styles…

    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 315, Column 1934: reference to entity "ns" for which no system identifier could be generated
    …href="/ro/content.aspx?style=styles&ns=-10000&amp;cid=19786" >Interconectare</…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 315, Column 2084: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …o; borderWidth: 1; borderColor: white"><a  href="/ro/content.aspx?style=styles…

    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 315, Column 2127: reference to entity "ns" for which no system identifier could be generated
    …href="/ro/content.aspx?style=styles&ns=-10000&noparent=19782&amp;cid=19794" >o…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 315, Column 2143: reference to entity "noparent" for which no system identifier could be generated
    …t.aspx?style=styles&ns=-10000&noparent=19782&amp;cid=19794" >oferta comerciala…

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

  • Info Line 315, Column 1364: entity was defined here
    …ro/content.aspx?style=styles&ns=-10000&noparent=19829&amp;cid=19909" >Tari ale…
  • Error Line 328, Column 128: required attribute "ALT" not specified
    …7" src="/ro/images/resources/blue_line_bottom_right_cornet.gif" width="7"></td>

    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 341, Column 109: NET-enabling start-tag requires SHORTTAG YES
    …llPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/tea…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 341, Column 109: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …llPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/tea…

    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 341, Column 110: end tag for "TABLE" which is not finished
    …lPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/teas…

    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 341, Column 110: end tag for "TABLE" which is not finished
    …lPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/teas…

    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 342, Column 22: document type does not allow element "TBODY" here
    <TBODY class=maintext>

    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 346, Column 30: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
    <TD height=68 width=80 align=middle><IMG src="http://www.cosmote.ro/ro/images/r…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 346, Column 130: required attribute "ALT" not specified
    ….cosmote.ro/ro/images/resources/buton_webcare_mod.jpg" width=65 height=62></TD>

    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 347, Column 52: an attribute value must be a literal unless it contains only name characters
    …ck height=68 width=154><B><FONT color=#8cc63e>Cosmote WebCare</FONT></B><BR><A…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 350, Column 60: end tag for "SPAN" omitted, but its declaration does not permit this
    <TD height=10 width=242 colSpan=3></TD></TR></TBODY></TABLE>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 341, Column 9: start tag was here
    								<span id="BoxWebcare_content"><TABLE border=0 cellSpacing=0 cellPadding…
  • Error Line 351, Column 7: end tag for element "SPAN" which is not open
    </span>

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

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

  • Warning Line 354, Column 119: NET-enabling start-tag requires SHORTTAG YES
    …llPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/tea…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 354, Column 119: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …llPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/tea…

    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 354, Column 120: end tag for "TABLE" which is not finished
    …lPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/teas…

    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 354, Column 120: end tag for "TABLE" which is not finished
    …lPadding=0 width=242 background=http://www.cosmote.ro/en/images/resources/teas…

    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 355, Column 22: document type does not allow element "TBODY" here
    <TBODY class=maintext>

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

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

  • Error Line 359, Column 30: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
    <TD height=81 width=80 align=middle><IMG src="http://www.cosmote.ro/en/images/r…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 359, Column 126: required attribute "ALT" not specified
    …/www.cosmote.ro/en/images/resources/sales_network.jpg" width=65 height=65></TD>

    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 360, Column 52: an attribute value must be a literal unless it contains only name characters
    …ck height=68 width=154><B><FONT color=#8cc63e>Reţea de Vânzare</FONT></B><BR><…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 363, Column 60: end tag for element "TABLE" which is not open
    <TD height=10 width=242 colSpan=3></TD></TR></TBODY></TABLE>

    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 367, Column 61: document type does not allow element "TD" here
    							<td style="TEXT-ALIGN: left" vAlign="top" width="50%">

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

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

  • Warning Line 372, Column 239: NET-enabling start-tag requires SHORTTAG YES
    …value="Reincarca_cartela_webcare.swf" />     <param name="quality" value="high…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 281: NET-enabling start-tag requires SHORTTAG YES
    …   <param name="quality" value="high" />     <param name="bgcolor" value="#fff…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 326: NET-enabling start-tag requires SHORTTAG YES
    …<param name="bgcolor" value="#ffffff" />     <param name="play" value="true" /…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 365: NET-enabling start-tag requires SHORTTAG YES
    …>     <param name="play" value="true" />     <param name="loop" value="true" /…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 404: NET-enabling start-tag requires SHORTTAG YES
    …>     <param name="loop" value="true" />     <param name="wmode" value="transp…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 451: NET-enabling start-tag requires SHORTTAG YES
    …aram name="wmode" value="transparent" />     <param name="scale" value="showal…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 494: NET-enabling start-tag requires SHORTTAG YES
    …  <param name="scale" value="showall" />     <param name="menu" value="true" /…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 533: NET-enabling start-tag requires SHORTTAG YES
    …>     <param name="menu" value="true" />     <param name="devicefont" value="f…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 579: NET-enabling start-tag requires SHORTTAG YES
    …param name="devicefont" value="false" />     <param name="salign" value="" /> …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 616: NET-enabling start-tag requires SHORTTAG YES
    … />     <param name="salign" value="" />     <param name="allowScriptAccess" v…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 674: NET-enabling start-tag requires SHORTTAG YES
    …allowScriptAccess" value="sameDomain" />    <!--<![endif]-->     <a href="http…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 372, Column 863: NET-enabling start-tag requires SHORTTAG YES
    …yer.gif" alt="Get Adobe Flash player" />     </a>    <!--[if !IE]>-->    </obj…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 374, Column 11: end tag for element "TR" which is not open
    						</tr>

    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 375, Column 10: document type does not allow element "TR" here
    						<tr>

    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 383, Column 10: document type does not allow element "TR" here
    						<tr><td colSpan="2" height="240"><BR>

    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 385, Column 275: element "EMBED" undefined
    …tion/x-shockwave-flash" width="500" height="240" menu="true" ></embed></OBJECT>

    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 389, Column 10: document type does not allow element "TR" here
    						<tr><td colSpan="2" height="240"><br>

    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 390, Column 69: reference to entity "ns" for which no system identifier could be generated
    …ote.ro/ro/content.aspx?style=styles&ns=-10000&cid=18792"><img src="http://www.…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 390, Column 80: reference to entity "cid" for which no system identifier could be generated
    …ontent.aspx?style=styles&ns=-10000&cid=18792"><img src="http://www.cosmote.ro/…

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

  • Info Line 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Error Line 390, Column 159: required attribute "ALT" not specified
    …2"><img src="http://www.cosmote.ro/ro/images/phishing_2012.jpg" border="0"></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 395, Column 13: end tag for element "TABLE" which is not open
    					</table>

    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 396, Column 9: end tag for element "TD" which is not open
    				</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 397, Column 8: end tag for element "TR" which is not open
    			</TR>

    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 398, Column 10: end tag for element "TABLE" which is not open
    		</TABLE>

    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 410, Column 8: invalid comment declaration: found character "<" outside comment but inside comment declaration
    			<!--<span id="footer_control_txtfooter"></span>-->

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

  • Info Line 406, Column 3: comment declaration started here
    		<!--<TD WIDTH="28" HEIGHT="27" align="center" valign="top"><IMG SRC="images/r…
  • Error Line 410, Column 9: character data is not allowed here
    			<!--<span id="footer_control_txtfooter"></span>-->

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 410, Column 50: end tag for element "SPAN" which is not open
    			<!--<span id="footer_control_txtfooter"></span>-->

    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 425, Column 123: reference to entity "ns" for which no system identifier could be generated
    … <a href="content.aspx?style=styles&ns=-10000&cid=18792" id="footer_control_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 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…
  • Error Line 425, Column 134: reference to entity "cid" for which no system identifier could be generated
    …ontent.aspx?style=styles&ns=-10000&cid=18792" id="footer_control_href_fraud" 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 114, Column 100: entity was defined here
    …1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></span>
  • Error Line 426, Column 122: reference to entity "ns" for which no system identifier could be generated
    …a href="wholesale.aspx?style=styles&ns=-10000" id="footer_control_href_interco…

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

  • Info Line 114, Column 90: entity was defined here
    …l1"><a href='default.aspx?style=styles&ns=-10000&cid=-10000'>Personal</a></spa…

Visitor Analysis

Daily Visitor
  • 1.867 visits