Erreurs W3C

Nouveau WRInaute
Bonjour a tous.

J'ai reussi a corrige les erreurs les plus simples, mais il me reste encore 31 erreur et 42 warning.
Le probleme est que je ne sais pas d'une part comment corriger ces erreurs et d autre part je ne trouve pas ces intitules dans le HTML de mon site.
Si quelqu un aurait la bonte de m'eclairer je vous remercie.
Voila un exemple d'erreurs:
ine 131, Column 129: cannot generate system identifier for general entity "langpair"

…'+encodeURIComponent(location.href)+'&langpair=fr|en&hl=fr&ie=UTF8'); return f…



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 131, Column 129: general entity "langpair" not defined and no default entity

…'+encodeURIComponent(location.href)+'&langpair=fr|en&hl=fr&ie=UTF8'); return f…



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 131, Column 137: reference not terminated by REFC delimiter

…URIComponent(location.href)+'&langpair=fr|en&hl=fr&ie=UTF8'); return false;" t…



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 131, Column 137: reference to external entity in attribute value

…URIComponent(location.href)+'&langpair=fr|en&hl=fr&ie=UTF8'); return false;" t…



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 131, Column 137: reference to entity "langpair" for which no system identifier could be generated

…URIComponent(location.href)+'&langpair=fr|en&hl=fr&ie=UTF8'); return false;" t…



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.
 
S
StefouFR
Guest
Bonjour,

est-ce que tu peux afficher le lien de ton site ici ?

Je veux bien regarder les erreurs ensuite pour voir si je peux t'aider.
 
WRInaute accro
Je viens de regarder, c'est à cause de scripts sur un onclick. Si tu remplaces les & par & ça devrais corriger le problème.

Mais ce serait plus propre de mettre la fonction de traduction à part, au lieu d'avoir un pâté pareil à chaque drapeau:
Code:
<a target="_blank" rel="nofollow" onclick="window.open('https://www.google.com/translate?u='+encodeURIComponent(location.href)+'&langpair=fr|en&hl=fr&ie=UTF8'); return false;" title="Google-Traduction-Français-en-anglais "><img border="0" style="cursor:pointer; cursor:hand;" width="24" alt="Google-Translate-English to French " src="http://i321.photobucket.com/albums/nn397/rodney2006_2008/flag_usa.gif" height="18" title="Google-Traduction-Français-en-anglais "/></a>
 
Nouveau WRInaute
spout a dit:
Je viens de regarder, c'est à cause de scripts sur un onclick. Si tu remplaces les & par &amp; ça devrais corriger le problème.

Mais ce serait plus propre de mettre la fonction de traduction à part, au lieu d'avoir un pâté pareil à chaque drapeau:
Code:
<a target="_blank" rel="nofollow" onclick="window.open('https://www.google.com/translate?u='+encodeURIComponent(location.href)+'&langpair=fr|en&hl=fr&ie=UTF8'); return false;" title="Google-Traduction-Français-en-anglais "><img border="0" style="cursor:pointer; cursor:hand;" width="24" alt="Google-Translate-English to French " src="http://i321.photobucket.com/albums/nn397/rodney2006_2008/flag_usa.gif" height="18" title="Google-Traduction-Français-en-anglais "/></a>

Je te remercie beaucoup,
En fait toutes ces erreurs c est a cause des drapeaux
Sais tu si il y a une autre solution avec un systeme de drapeaux pour la traduction sans avoir tous ces problemes, ou comment mettre la fonction de traduction a part ?

Merci en tout cas
 
Nouveau WRInaute
J'ai reussit a corriger la grande partie des erreurs,
mais il en reste 2 et je ne sais pas quelle est la source de ces problemes

Validation Output: 2 Errors

Error Line 161, Column 70: there is no attribute "height"

<table border="0" cellspacing="0" cellpadding="5" width="567" height="134">



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 186, 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>").
 
WRInaute accro
Bonjour,
Je vous conseillerai de changer de design pour quelque chose de plus coloré. Je trouve votre design vraiment triste ! On trouve de bien plus belle template maintenant !
Par contre, vous avez des balises META en doublon et dans le code, on trouve un peu de tout !
Des balises H1 vides, etc...
 
Nouveau WRInaute
passion a dit:
Bonjour,
Je vous conseillerai de changer de design pour quelque chose de plus coloré. Je trouve votre design vraiment triste ! On trouve de bien plus belle template maintenant !
Par contre, vous avez des balises META en doublon et dans le code, on trouve un peu de tout !
Des balises H1 vides, etc...


Bonjour je vous remercie,
Malheureusement le design avec LWS est assez limite. je vais sortir tout ce qui est en double et remplir les balises vides.

En vous remerciant,
Cordialement
 
Discussions similaires
Haut