hataların devamı
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 251, Column 580: there is no attribute "height"
…x-shockwave-flash" width="300" height="235" allowFullScreen="true" AllowScript…
✉
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 251, Column 602: there is no attribute "allowFullScreen"
…th="300" height="235" allowFullScreen="true" AllowScriptAccess="always" bgcolo…
✉
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 251, Column 627: there is no attribute "AllowScriptAccess"
…owFullScreen="true" AllowScriptAccess="always" bgcolor="#000000" quality="high…
✉
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 251, Column 644: there is no attribute "bgcolor"
…e" AllowScriptAccess="always" bgcolor="#000000" quality="high" flashVars="id=3…
✉
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 251, Column 662: there is no attribute "quality"
…ss="always" bgcolor="#000000" quality="high" flashVars="id=3112441&vid=688319&…
✉
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 251, Column 679: there is no attribute "flashVars"
…or="#000000" quality="high" flashVars="id=3112441&vid=688319&lang=en-us&intl=u…
✉
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 251, Column 694: reference not terminated by REFC delimiter
…ality="high" flashVars="id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http…
✉
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 251, Column 694: reference to external entity in attribute value
…ality="high" flashVars="id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http…
✉
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 251, Column 694: reference to entity "vid" for which no system identifier could be generated
…ality="high" flashVars="id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Info Line 251, Column 329: entity was defined here
…ram name="flashVars" value="id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=…
# Warning Line 251, Column 706: reference not terminated by REFC delimiter
… flashVars="id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.…
✉
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 251, Column 717: reference not terminated by REFC delimiter
…"id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/…
✉
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 251, Column 717: reference to external entity in attribute value
…"id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/…
✉
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 251, Column 717: reference to entity "intl" for which no system identifier could be generated
…"id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Info Line 251, Column 351: entity was defined here
…alue="id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/…
# Warning Line 251, Column 729: reference not terminated by REFC delimiter
…vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/sch/cn/v/v1/…
✉
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 251, Column 729: reference to external entity in attribute value
…vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/sch/cn/v/v1/…
✉
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 251, Column 729: reference to entity "thumbUrl" for which no system identifier could be generated
…vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/sch/cn/v/v1/…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Info Line 251, Column 359: entity was defined here
…=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/sch…
# Warning Line 251, Column 799: reference not terminated by REFC delimiter
…m/a/i/us/sch/cn/v/v1/w994/688319_400_300.jpeg&embed=1" ></embed></object></div>
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Warning Line 251, Column 799: reference to external entity in attribute value
…m/a/i/us/sch/cn/v/v1/w994/688319_400_300.jpeg&embed=1" ></embed></object></div>
✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
# Error Line 251, Column 799: reference to entity "embed" for which no system identifier could be generated
…m/a/i/us/sch/cn/v/v1/w994/688319_400_300.jpeg&embed=1" ></embed></object></div>
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Info Line 251, Column 432: entity was defined here
…s/sch/cn/v/v1/w994/688319_400_300.jpeg&embed=1" /><embed src="http://d.yimg.co…
# Error Line 251, Column 803: element "embed" undefined
…m/a/i/us/sch/cn/v/v1/w994/688319_400_300.jpeg&embed=1" ></embed></object></div>
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
* incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
* by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
* by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).