youtube videoları için w3c hatalarına çözüm bulunmuş fakat yahoo için çözüm bulamadım malum youtube yasaklı yahoo video kullanıyorum fakat 30`a yakın hatası var bir çözümü varmıdır
<object width="300" height="235"><param name="movie" value="http://d.yimg.com/static.video.yahoo.com/yep/YV_YEP.swf?ver=2.2.46" /><param name="allowFullScreen" value="true" /><param name="AllowScriptAccess" VALUE="always" /><param name="bgcolor" value="#000000" /><param name="flashVars" value="id=19256633&vid=7364432&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/p/i/bcst/videosearch/14349/106148471.jpeg&embed=1" /><embed src="http://d.yimg.com/static.video.yahoo.com/yep/YV_YEP.swf?ver=2.2.46" type="application/x-shockwave-flash" width="300" height="235" allowFullScreen="true" AllowScriptAccess="always" bgcolor="#000000" quality="high" flashVars="id=19256633&vid=7364432&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/p/i/bcst/videosearch/14349/106148471.jpeg&embed=1" ></embed></object>
# Error Line 251, Column 237: there is no attribute "VALUE"
…<param name="AllowScriptAccess" VALUE="always" /><param name="bgcolor" value="…
✉
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 330: cannot generate system identifier for general entity "vid"
…am name="flashVars" value="id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=h…
✉
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 251, Column 330: general entity "vid" not defined and no default entity
…am name="flashVars" value="id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=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.
# Warning Line 251, Column 333: reference not terminated by REFC delimiter
…name="flashVars" value="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 333: reference to external entity in attribute value
…name="flashVars" value="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 333: reference to entity "vid" for which no system identifier could be generated
…name="flashVars" value="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 345: reference not terminated by REFC delimiter
…ars" value="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 352: cannot generate system identifier for general entity "intl"
…lue="id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i…
✉
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 251, Column 352: general entity "intl" not defined and no default entity
…lue="id=3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/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.
# Warning Line 251, Column 356: 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 356: 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 356: 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 360: cannot generate system identifier for general entity "thumbUrl"
…3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/sch/…
✉
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 251, Column 360: general entity "thumbUrl" not defined and no default entity
…3112441&vid=688319&lang=en-us&intl=us&thumbUrl=http%3A//l.yimg.com/a/i/us/sch/…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Warning Line 251, Column 368: 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 368: 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 368: 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 433: cannot generate system identifier for general entity "embed"
…/sch/cn/v/v1/w994/688319_400_300.jpeg&embed=1" /><embed src="http://d.yimg.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 251, Column 433: general entity "embed" not defined and no default entity
…/sch/cn/v/v1/w994/688319_400_300.jpeg&embed=1" /><embed src="http://d.yimg.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 251, Column 438: reference not terminated by REFC delimiter
…cn/v/v1/w994/688319_400_300.jpeg&embed=1" /><embed src="http://d.yimg.com/stat…
✉
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 438: reference to external entity in attribute value
…cn/v/v1/w994/688319_400_300.jpeg&embed=1" /><embed src="http://d.yimg.com/stat…
✉
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 438: reference to entity "embed" for which no system identifier could be generated
…cn/v/v1/w994/688319_400_300.jpeg&embed=1" /><embed src="http://d.yimg.com/stat…
✉
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 455: there is no attribute "src"
…19_400_300.jpeg&embed=1" /><embed src="http://d.yimg.com/static.video.yahoo.co…
✉
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 529: there is no attribute "type"
…o.com/yep/YV_YEP.swf?ver=2.2.46" type="application/x-shockwave-flash" width="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 567: there is no attribute "width"
…"application/x-shockwave-flash" width="300" height="235" allowFullScreen="true…
✉
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).