james
Membre récent
 Hors-Ligne
Messages: 3
Je suis un lama!
|
bonjour j'ai un probleme pour métre ma page sur mon site mais je narrive pas a savoir comment les corriger.
si quelqu'un pourrais m'aider.
voila ce qu'il me dise, j'ai mis en rouge se qui pour eu ne va pas.
je connais rien a tous ca je les fait a partir de web dreator pro 4 mais comme il me disait qu'il y avait des probléme j'ai regardé ce que c'était mais je ne sais pas les réctifiées.
merci
<body onresize=PosPage(2,5,1.000000,1.000000); bgcolor="#000000" >✉
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 17, Column 22: an attribute value must be a literal unless it contains only name characters.
<body onresize=PosPage(2,5,1.000000,1.000000); bgcolor="#000000" >✉
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.
Line 17, Column 65: document type does not allow element "BODY" here.
…e=PosPage(2,5,1.000000,1.000000); bgcolor="#000000" >✉
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 36, Column 64: cannot generate system identifier for general entity "rci".
…ulte.xooit.com/login.php?logout=true&rci=4c746dc69e83cbaf64efe38193eae6c2'>ht✉
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.
Line 36, Column 64: general entity "rci" not defined and no default entity.
…ulte.xooit.com/login.php?logout=true&rci=4c746dc69e83cbaf64efe38193eae6c2'>ht✉
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.
Line 36, Column 67: reference to entity "rci" for which no system identifier could be generated.
…e.xooit.com/login.php?logout=true&rci=4c746dc69e83cbaf64efe38193eae6c2'>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.
Line 36, Column 63: entity was defined here.
…culte.xooit.com/login.php?logout=true&rci=4c746dc69e83cbaf64efe38193eae6c2'>h Line 36, Column 159: reference to entity "rci" for which no system identifier could be generated.
…e.xooit.com/login.php?logout=true&rci=4c746dc69e83cbaf64efe38193eae6c2</a>]<…✉
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.
Line 36, Column 63: entity was defined here.
…culte.xooit.com/login.php?logout=true&rci=4c746dc69e83cbaf64efe38193eae6c2'>h |
Auteur 
