M2B Gonflable
-
16 janv. 2013 à 10:04
ThEBiShOp
Messages postés8378Date d'inscriptionjeudi 22 mars 2007StatutContributeurDernière intervention 8 février 2021
-
16 janv. 2013 à 14:14
Bonjour,
J'ai change le template de mon site.
l ancien etait en html et celui la en xhtml,
je me retrouve avec pas mal d erreurs.
Validation Output: 28 Errors
Error Line 4, Column 7: document type does not allow element "head" here; assuming missing "html" start-tag
<head >
?
Error Line 4, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
<head >
?
Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
<html xmlns="http://www.w3.org/1999/xhtml">
Error Line 125, Column 7: document type does not allow element "title" here
<title>M2B Gonflable - Tout est Realisable en structure gonflable</title>
?
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 126, Column 255: end tag for "meta" 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 ">".
Info Line 126, Column 1: start tag was here
Error Line 127, Column 184: end tag for "meta" omitted, but OMITTAG NO was specified
...de toutes formes et de toutes capacites.Chacune de nos structures est unique.">
?
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 127, Column 1: start tag was here
<meta name="description" content="Nous sommes fabricant de structures gonflable...
Error Line 128, Column 73: end tag for "meta" 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 ">".
Info Line 128, Column 1: start tag was here
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 177, Column 34: there is no attribute "leftmargin"
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 177, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
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 177, Column 46: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
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 177, Column 60: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
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 177, Column 75: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
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 185, Column 30: there is no attribute "background"
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 204, Column 70: required attribute "alt" not specified
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 299, Column 60: required attribute "alt" not specified
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 314, Column 70: required attribute "alt" not specified
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 355, Column 60: required attribute "alt" not specified
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 379, Column 85: cannot generate system identifier for general entity "media"
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 379, Column 85: general entity "media" not defined and no default entity
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 379, Column 90: reference not terminated by REFC delimiter
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 379, Column 90: reference to external entity in attribute value
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 379, Column 90: reference to entity "media" for which no system identifier could be generated
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 379, Column 84: entity was defined here
Warning Line 379, Column 160: cannot generate system identifier for general entity "description"
..._images/262762001349958809images1.jpg&description=fabricant de structures gonf...
?
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 379, Column 160: general entity "description" not defined and no default entity
..._images/262762001349958809images1.jpg&description=fabricant de structures gonf...
?
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 379, Column 171: reference not terminated by REFC delimiter
...762001349958809images1.jpg&description=fabricant de structures gonflables sur ...
?
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 379, Column 171: reference to external entity in attribute value
...762001349958809images1.jpg&description=fabricant de structures gonflables sur ...
?
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 379, Column 171: reference to entity "description" for which no system identifier could be generated
...762001349958809images1.jpg&description=fabricant de structures gonflables sur ...
?
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 379, Column 159: entity was defined here
...b_images/262762001349958809images1.jpg&description=fabricant de structures gon...
Error Line 380, Column 161: there is no attribute "count-layout"
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 380, Column 253: required attribute "alt" not specified
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 420, Column 23: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<p><ul class="sitemap"><li>Main Menu
?
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>").
Je ne sais pas comment les rectifier
le head n est pas a sa place
mais je ne sais pas ou le mettre......
M2B Gonflable
Messages postés2Date d'inscriptionmercredi 16 janvier 2013StatutMembreDernière intervention16 janvier 2013 16 janv. 2013 à 12:08
Bonjour je te remercie pour tes reponses.
En fait le head est deja en tete, mais l erreur persiste.
Il est vrai que l affichage du site est correcte mais ma plus grande crainte est par rapport au positionement, si j'etais sur que ca ne me penalisera pas dans le positionement google je laisserai tout comme ca, car le site actuelement est parfaitement positione par google pour les mots clefs relatifs aux recherchent de mes clients cibles, je ne voudrais pas perdre ca au prochain passage du bot.
ThEBiShOp
Messages postés8378Date d'inscriptionjeudi 22 mars 2007StatutContributeurDernière intervention 8 février 20211 565 16 janv. 2013 à 12:54
De toute façon, l'influence de la validation W3C par rapport au pagerank est quasi inexistante... regarde n'importe quel gros site, et essaye de faire une validation w3c, tu seras surpris.
Vous n’avez pas trouvé la réponse que vous recherchez ?
M2B Gonflable
Messages postés2Date d'inscriptionmercredi 16 janvier 2013StatutMembreDernière intervention16 janvier 2013 16 janv. 2013 à 13:30
Merci beaucoup,
Le lien du site: www.m2bgonflable.com
En gros je peux tout laisser comme ca, ca n'influencera pas le position google, c'est bien ca ?
Si j'ai bien comprise se serait parfait.
En vous remerciant mille fois
Les sites validés par le w3c ne sont pas légions sur internet, plus un site est conséquent, plus ça sera compliqué d'être valide à ce niveau et ça n'influe pas sur le référencement.
