|
2 / 2 / 1
Регистрация: 15.08.2011
Сообщений: 31
|
|
| 1 | |
Ошибки валидации - как исправить?17.03.2012, 10:24. Показов 27158. Ответов 17
Метки нет (Все метки)
выдает непонятные ошибки вот например что-то вроде этого Как исправить?? Validation Output: 4 Errors Line 4, Column 9: document type does not allow element "HEAD" here <head> ✉ 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). Line 8, Column 11: document type does not allow element "BODY" here <body> ✉ 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). Line 24, Column 7: "HEAD" not finished but containing element ended </html> ✉ Line 24, Column 7: end tag for "HTML" which is not finished </html> ✉ 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.
0
|
|
(| 17.03.2012, 10:24 | |
|
Ответы с готовыми решениями:
17
Ошибки валидации
При валидации ошибки, хотя все правильно |
|
Vovan-VE
|
|
17.03.2012, 16:08
#4
|
|
Не по теме:
Сообщение от tema_92
0
|
|
2 / 2 / 1
Регистрация: 15.08.2011
Сообщений: 31
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 18.03.2012, 12:38 [ТС] | 5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Validation Output: 17 Errors
Line 4, Column 9: document type does not allow element "HEAD" here <head> ✉ 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). Line 8, Column 11: document type does not allow element "BODY" here <body> ✉ 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). Line 10, Column 9: NET-enabling start-tag requires SHORTTAG YES <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. Line 12, Column 9: NET-enabling start-tag requires SHORTTAG YES <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. Line 16, Column 17: NET-enabling start-tag requires SHORTTAG YES <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. Line 19, Column 7: NET-enabling start-tag requires SHORTTAG YES <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. Line 21, Column 116: duplicate specification of attribute "TITLE" …age" alt="картинка отсутствует" title="image" height="200" width="300" border… ✉ You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag. Line 23, Column 63: there is no attribute "HEIGHT" …enter" border="4" width="1356" height="768" bordercolor="blue" cellpadding="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. Line 23, Column 82: there is no attribute "BORDERCOLOR" …width="1356" height="768" bordercolor="blue" cellpadding="10" cellspacing="0"> ✉ You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash. Line 31, Column 58: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag … <h3><p><strong>КиберФорум</strong> - компьютер… ✉ 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>"). Line 38, Column 19: end tag for element "P" which is not open </p> ✉ 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. Line 43, Column 76: there is no attribute "BODERCOLOR" … <table align="left" border="2" bodercolor="green" width="455" height="1000"> ✉ 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. Line 76, Column 75: required attribute "ALT" not specified <img src="https://www.cyberforum.ru/file base/navbits_start.gif" width="20" height="20"> ✉ The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element. Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>. Line 77, Column 28: document type does not allow element "H3" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag <p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p> ✉ The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>"). Line 77, Column 71: end tag for "H3" omitted, but its declaration does not permit this <p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p> ✉ 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. Line 77, Column 25: start tag was here <p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p> Line 77, Column 71: end tag for "STRONG" omitted, but its declaration does not permit this <p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p> ✉ 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. Line 77, Column 17: start tag was here <p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p> Line 79, Column 81: end tag for element "STRONG" which is not open … Техподдержка — DevArt.Pro<h3></strong> ✉ 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. Line 80, Column 139: end tag for element "P" which is not open …t" alt="image not found" width="90" height="50" title="Рейтинг на mail.ru"></p> ✉ 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. Line 83, Column 15: end tag for "H3" omitted, but its declaration does not permit this </td> ✉ 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. Line 79, Column 69: start tag was here … Техподдержка — DevArt.Pro<h3></strong> Line 107, Column 7: "HEAD" not finished but containing element ended </html> ✉ Line 107, Column 7: end tag for "HTML" which is not finished </html> ✉ 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.
Добавлено через 1 минуту вот такие ошибки не знаю как исправить) Добавлено через 15 минут да знаете пробовал уже,но не помогает!
0
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
conformist
|
|
18.03.2012, 12:43
#6
|
|
Не по теме: сколько тут текста...ошибок....может лучше просто сделать заново?
0
|
|
2 / 2 / 1
Регистрация: 15.08.2011
Сообщений: 31
|
||||||
| 18.03.2012, 16:17 [ТС] | 8 | |||||
0
|
||||||
|
O tempora, o mores!
238 / 172 / 13
Регистрация: 15.01.2012
Сообщений: 681
|
|
| 18.03.2012, 17:33 | 9 |
|
только мне кажется, что это исходный код одной из страниц этого форума?
0
|
|
|
Фрилансер
   1846 / 1342 / 599
Регистрация: 12.01.2011
Сообщений: 5,432
|
||||||
| 18.03.2012, 17:35 | 10 | |||||
|
tema_92, зачем же вы нас так мучаете? вставляйте код через
Добавлено через 57 секунд <html> </html> Вот так вот :
0
|
||||||
|
209 / 209 / 6
Регистрация: 23.10.2011
Сообщений: 971
|
||||||
| 18.03.2012, 18:00 | 11 | |||||
|
1. meta должен быть внутри head
2. одиночные теги в html должны быть открыты, в отличии от XHTML (пишем просто <br>) 3. атрибут height для table не входит в спецификацию, как и bordercolor (для этого юзай CSS) 4. в одной из строчек дважды повторяется атрибут title 5. тег p внутри h3. блочный элемент не должен стоять внутри строчного. 6. какой-то bodercolor... 7. h3 внутри p. теги не должны пересекаться 8. h3 внутри strong ну и прочие мелкие ошибки.... откуда эта верстка??? исправленая версия:
1
|
||||||
|
0 / 0 / 0
Регистрация: 13.05.2012
Сообщений: 4
|
|
| 13.05.2012, 21:31 | 15 |
|
Здравствуйте!подскажите пожалуйста!при запуске компьютера постоянно стало всплывать окно solution center, как его убрать????? прям раздражает,чтоб убрать это окно нужно по 10 раз на отмену нажимать((((
0
|
|
|
1 / 1 / 0
Регистрация: 29.05.2015
Сообщений: 103
|
|
| 21.09.2015, 16:17 | 18 |
|
Heleg,
Здравствуйте, помогите и мне, верстка чужая, поэтому все сложнее, причем, указывая DOCTYPE XHTML 1.0 Transitional валидатор ругается - перепробовал все, целый день потратил. Из 33 ошибок осталось 14. Ткните пожайлуйста вот ошибки Notes and Potential Issues The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document. Warning DOCTYPE Override in effect! The detected DOCTYPE Declaration "<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"/>" has been suppressed and the DOCTYPE for "XHTML 1.0 Transitional" inserted instead, but even if no errors are shown below the document will not be Valid until you update it to reflect this new DOCTYPE. ↑ TOP Validation Output: 14 Errors Error end tag for X omitted, but OMITTAG NO was specified ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". Line 741, column 7: end tag for "div" omitted, but OMITTAG NO was specified </body> Line 741, column 7: end tag for "div" omitted, but OMITTAG NO was specified </body> Error document type does not allow element X here ✉ 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). Line 1, column 152: document type does not allow element "script" here …TR/xhtml1/DTD/xhtml1-transitional.dtd"><script type='text/javascript'>/*@cc_on Line 51, column 37: document type does not allow element "base" here <base href="http://thermis.ru/" /> Error there is no attribute X ✉ 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. Line 8, column 14: there is no attribute "prefix" <html prefix="og: http://ogp.me/ns#" xmlns="http://www.w3.org/1999/xhtml"> Line 299, column 23: there is no attribute "type" <jdoc:include type="message"/> Line 634, column 112: there is no attribute "height" …ft:10px; padding-top:5px; padding-bottom:5px;"> <table width="25%" height="50"> Error end tag for element X which is not open ✉ 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. Line 33, column 78: end tag for element "script" which is not open <script type="text/javascript" src="/templates/beez_20/jquery.js"/></script> Line 619, column 195: end tag for element "a" which is not open …title="Написать нам"/> <div class="blok transition">Написать нам</div></a></td> Error duplicate specification of attribute X ✉ You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag. Line 639, column 56: duplicate specification of attribute "type" …t/javascript" id="top100Counter" type="text/javascript" src="http://counter.ra… Error ID X already defined ✉ An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element). Line 209, column 22: ID "cssmenu" already defined <ul class="menu" id="cssmenu"> Error element X undefined ✉ 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). Line 299, column 33: element "jdoc:include" undefined <jdoc:include type="message"/> Line 301, column 35: element "jdoc:include" undefined <jdoc:include type="component"/> Warning character X is the first character of a delimiter but occurred as data ✉ This message may appear in several cases: You tried to include the "<" character in your page: you should escape it as "<" You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe. Another possibility is that you forgot to close quotes in a previous tag. Line 4, column 63: character "&" is the first character of a delimiter but occurred as data …l(function(){if(document.body != null && typeof document.body != 'undefined'){… Line 4, column 64: character "&" is the first character of a delimiter but occurred as data …(function(){if(document.body != null && typeof document.body != 'undefined'){c… Line 197, column 25: character "<" is the first character of a delimiter but occurred as data if (top+h_mrg < h_hght) { Error X declaration not allowed in instance ✉ Line 5, column 12: "DOCTYPE" declaration not allowed in instance </script><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http:/…
0
|
|
| 21.09.2015, 16:17 | |
| 21.09.2015, 16:17 | |
|
Помогаю со студенческими работами здесь
18
Первая верстка как исправить ошибки Как получить ошибки валидации Не выводятся ошибки валидации формы YII Передача клиенту ошибки при валидации данных Искать еще темы с ответами Или воспользуйтесь поиском по форуму: |
Наверх