Ma poate ajuta cineva cu un sfat in ceea ce priveste erorile de pe un site?
Am verificat cu w3validator si am cateva erori care nu am putut sa scap de ele in dreamweaver, ceva sfaturi va rog frumos, se pricepe cineva sa ma ajute ?
Nu se pricepe nimeni sa rezolve erori inchipuite.
W3C Validator are prostul obicei sa iti spuna si ce problema ai la cod, dar se pare ca nu vrei sa ne dezvalui un asa secret
W3C Validator are prostul obicei sa iti spuna si ce problema ai la cod, dar se pare ca nu vrei sa ne dezvalui un asa secret
# Error Line 111, Column 9: there is no attribute "align".
<p align="center" class="fdfdsfdffff"><strong>Garantat</strong> <span class="d">
✉
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 140, Column 28: there is no attribute "bgcolor".
<td bgcolor="#FFFFFF"><p>
✉
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 140, Column 37: document type does not allow element "td" here; assuming missing "tr" start-tag.
<td bgcolor="#FFFFFF"><p>
✉
# Error Line 150, Column 20: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag.
<p><img src="images/100sati.jpg" alt="" width="150" height="11
✉
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 150, Column 93: end tag for "p" omitted, but OMITTAG NO was specified.
…" width="150" height="111" /></p></td>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 144, Column 18: start tag was here.
<p class="hygugy">Indiferent pentru care motiv constatati ca
# Error Line 152, Column 19: end tag for "tr" omitted, but OMITTAG NO was specified.
</table>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 140, Column 16: start tag was here.
<td bgcolor="#FFFFFF"><p>
# Error Line 170, Column 23: there is no attribute "align".
<div align="center"><!-- CursBnr.ro Code start v.2.1-->
✉
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 171, Column 209: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag.
…cript><a href="http://www.cursbnr.ro"><strong>curs bnr</strong></a></noscri…
✉
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 200, Column 35: there is no attribute "language".
<script language="Javascript" src="http://www.freeusersonline.
✉
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 200, Column 98: cannot generate system identifier for general entity "siteurl".
…ww.freeusersonline.com/?action=track&siteurl=http://www.audio-engleza.com"></
✉
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 "&" (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 æ 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 200, Column 98: general entity "siteurl" not defined and no default entity.
…ww.freeusersonline.com/?action=track&siteurl=http://www.audio-engleza.com"></
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Warning Line 200, Column 105: reference not terminated by REFC delimiter.
…usersonline.com/?action=track&siteurl=http://www.audio-engleza.com"></script>
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Warning Line 200, Column 105: reference to external entity in attribute value.
…usersonline.com/?action=track&siteurl=http://www.audio-engleza.com"></script>
✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
# Error Line 200, Column 105: reference to entity "siteurl" for which no system identifier could be generated.
…usersonline.com/?action=track&siteurl=http://www.audio-engleza.com"></script>
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Info Line 200, Column 97: entity was defined here.
…www.freeusersonline.com/?action=track&siteurl=http://www.audio-engleza.com"><
# Error Line 200, Column 135: required attribute "type" not specified.
…siteurl=http://www.audio-engleza.com"></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 206, Column 2: document type does not allow element "p" here; assuming missing "li" start-tag.
<p><a href="http://www.oculture.com/2006/10/audio_book_podc.html">Pentru a-ti fo
✉
# Error Line 214, Column 6: end tag for "li" omitted, but OMITTAG NO was specified.
</div>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 206, Column 0: start tag was here.
<p><a href="http://www.oculture.com/2006/10/audio_book_podc.html">Pentru a-ti fo
# Error Line 214, Column 6: end tag for "ul" omitted, but OMITTAG NO was specified.
</div>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 197, Column 12: start tag was here.
<ul>
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 224, Column 0: start tag was here.
<div id="footer"><div align="center">
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 82, Column 0: start tag was here.
<div id="back1">
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 80, Column 0: start tag was here.
<div id="page">
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 66, Column 1: start tag was here.
<div id="main">
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 43, Column 0: start tag was here.
<div id="back">
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 42, Column 0: start tag was here.
<div id="content">
# Error Line 227, Column 7: end tag for "html" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 2, Column 0: start tag was here.
<html xmlns="http://www.w3.org/1999/xhtml">
# Error Line 150, Column > 80: XML Parsing Error: Opening and ending tag mismatch: p line 144 and td.
…ti.jpg" alt="" width="150" height="111" /></p></td>…
✉
# Error Line 152, Column 20: XML Parsing Error: Opening and ending tag mismatch: td line 140 and table.
</table>
✉
# Error Line 157, Column 7: XML Parsing Error: Opening and ending tag mismatch: table line 138 and div.
</div>
✉
# Error Line 200, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…ipt" src="http://www.freeusersonline.com/?action=track&siteurl=http://www.aud…
✉
# Error Line 214, Column 7: XML Parsing Error: Opening and ending tag mismatch: ul line 197 and div.
</div>
✉
# Error Line 227, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 224 and body.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 158.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 84.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 82.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 80.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 66.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 43.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 42.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag body line 40.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag html line 2.
</body>
<p align="center" class="fdfdsfdffff"><strong>Garantat</strong> <span class="d">
✉
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 140, Column 28: there is no attribute "bgcolor".
<td bgcolor="#FFFFFF"><p>
✉
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 140, Column 37: document type does not allow element "td" here; assuming missing "tr" start-tag.
<td bgcolor="#FFFFFF"><p>
✉
# Error Line 150, Column 20: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag.
<p><img src="images/100sati.jpg" alt="" width="150" height="11
✉
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 150, Column 93: end tag for "p" omitted, but OMITTAG NO was specified.
…" width="150" height="111" /></p></td>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 144, Column 18: start tag was here.
<p class="hygugy">Indiferent pentru care motiv constatati ca
# Error Line 152, Column 19: end tag for "tr" omitted, but OMITTAG NO was specified.
</table>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 140, Column 16: start tag was here.
<td bgcolor="#FFFFFF"><p>
# Error Line 170, Column 23: there is no attribute "align".
<div align="center"><!-- CursBnr.ro Code start v.2.1-->
✉
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 171, Column 209: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag.
…cript><a href="http://www.cursbnr.ro"><strong>curs bnr</strong></a></noscri…
✉
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 200, Column 35: there is no attribute "language".
<script language="Javascript" src="http://www.freeusersonline.
✉
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 200, Column 98: cannot generate system identifier for general entity "siteurl".
…ww.freeusersonline.com/?action=track&siteurl=http://www.audio-engleza.com"></
✉
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 "&" (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 æ 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 200, Column 98: general entity "siteurl" not defined and no default entity.
…ww.freeusersonline.com/?action=track&siteurl=http://www.audio-engleza.com"></
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Warning Line 200, Column 105: reference not terminated by REFC delimiter.
…usersonline.com/?action=track&siteurl=http://www.audio-engleza.com"></script>
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Warning Line 200, Column 105: reference to external entity in attribute value.
…usersonline.com/?action=track&siteurl=http://www.audio-engleza.com"></script>
✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
# Error Line 200, Column 105: reference to entity "siteurl" for which no system identifier could be generated.
…usersonline.com/?action=track&siteurl=http://www.audio-engleza.com"></script>
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Info Line 200, Column 97: entity was defined here.
…www.freeusersonline.com/?action=track&siteurl=http://www.audio-engleza.com"><
# Error Line 200, Column 135: required attribute "type" not specified.
…siteurl=http://www.audio-engleza.com"></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 206, Column 2: document type does not allow element "p" here; assuming missing "li" start-tag.
<p><a href="http://www.oculture.com/2006/10/audio_book_podc.html">Pentru a-ti fo
✉
# Error Line 214, Column 6: end tag for "li" omitted, but OMITTAG NO was specified.
</div>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 206, Column 0: start tag was here.
<p><a href="http://www.oculture.com/2006/10/audio_book_podc.html">Pentru a-ti fo
# Error Line 214, Column 6: end tag for "ul" omitted, but OMITTAG NO was specified.
</div>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 197, Column 12: start tag was here.
<ul>
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 224, Column 0: start tag was here.
<div id="footer"><div align="center">
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 82, Column 0: start tag was here.
<div id="back1">
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 80, Column 0: start tag was here.
<div id="page">
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 66, Column 1: start tag was here.
<div id="main">
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 43, Column 0: start tag was here.
<div id="back">
# Error Line 227, Column 6: end tag for "div" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 42, Column 0: start tag was here.
<div id="content">
# Error Line 227, Column 7: end tag for "html" omitted, but OMITTAG NO was specified.
</body>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 2, Column 0: start tag was here.
<html xmlns="http://www.w3.org/1999/xhtml">
# Error Line 150, Column > 80: XML Parsing Error: Opening and ending tag mismatch: p line 144 and td.
…ti.jpg" alt="" width="150" height="111" /></p></td>…
✉
# Error Line 152, Column 20: XML Parsing Error: Opening and ending tag mismatch: td line 140 and table.
</table>
✉
# Error Line 157, Column 7: XML Parsing Error: Opening and ending tag mismatch: table line 138 and div.
</div>
✉
# Error Line 200, Column > 80: XML Parsing Error: EntityRef: expecting ';'.
…ipt" src="http://www.freeusersonline.com/?action=track&siteurl=http://www.aud…
✉
# Error Line 214, Column 7: XML Parsing Error: Opening and ending tag mismatch: ul line 197 and div.
</div>
✉
# Error Line 227, Column 7: XML Parsing Error: Opening and ending tag mismatch: div line 224 and body.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 158.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 84.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 82.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 80.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 66.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 43.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag div line 42.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag body line 40.
</body>
✉
# Error Line 227, Column 7: XML Parsing Error: Premature end of data in tag html line 2.
</body>
QUOTE (RaZ_C @ Feb 16 2009, 10:24) 
# Error Line 111, Column 9: there is no attribute "align".
[...]
[...]
Pai in marea majoritate a cazurilor, validatorul ti-a spus despre ce este vorba.
Ai folosit atribute depreciate sau neadmise in doctype-ul utilizat (align, bgcolor, target="_blank" nu sint admise in xhtml 1.0 strict, iar bgcolor si align mai sint si depreciate), ai uitat sa inchizi tag-uri, ai gresit la formatarea tabelelor, iar partea cu & (ampersand) este foarte clar explicata de catre validator. Si tot asa, nu o sa stau sa iti explic fiecare eroare de acolo. E posibil ca erorile de fapt sa fie mai putine, insa se poate intimpla ca de la o eroare de formatare - un p care nu a fost inchis, de exemplu, sa porneasca o intreaga cascada de alte "erori".
Ca sa te inveti sa lucrezi curat, fara erori, ar trebui sa renunti la Dreamweaver si sa te apuci sa scrii codul de mina, cu un editor de text - Notepad++ este excelent. Altfel niciodata nu vei stii de ce faci greseli, pentru ca in wysiwyg tu nu faci altceva decit sa tragi pe ecran niste "patrate", insa codul care se afla la originea patratelor nu il vezi niciodata.
@Raz: sfatul meu este să renunți la a coda html. Nu ai nici măcar voința să citești erorile validatorului. Dacă chiar vroiai să rezolvi, o simplă căutare pe google te-ar fi ajutat mai repede decât crezi.
Dar cum forumul e mult mai la îndemână...
Dar cum forumul e mult mai la îndemână...
Aceasta este o versiune simplificată a paginii originale. Pentru a vizita versiunea originala click aici.