Error Markup Validation W3C

Overzicht Reageren

Sponsored by: Vacatures door Monsterboard

Tim

Tim

30/10/2006 17:00:00
Quote Anchor link
Hey Allemaal,

Ik krijg een eror op mijn site, als ik een Markup Validation doe op de website van W3C.



Error Line 17: an attribute value must be a literal unless it contains only name characters.
<a href=index.php?go=view_news&newsid=12975>Amsterdamse wethou 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.

Schijnbaar is dit niet goed <a href=index.php?go=
Het vraagteken kleurt dan ook rood.

Wat kan ik het beste doen om dit te verhelpen.

Groetjes,
Tim
 
PHP hulp

PHP hulp

13/03/2025 19:09:34
 
M Ypma

M Ypma

30/10/2006 17:08:00
Quote Anchor link
<a href=index.php?go= is zeker niet goed omdat je de waarde die je geeft aan href wel moet quoten!

dus:
<a href=index.php?go=gamaar>
word:
<a href="index.php?go=gamaar">
 
Mebus  Hackintosh

Mebus Hackintosh

30/10/2006 17:12:00
Quote Anchor link
en & moet &amp; zijn;)

GR. mebus
 
Tim

Tim

30/10/2006 17:17:00
Quote Anchor link
Het werkt! Er staat nu nog maar een error.
Maar wat er bedoeld wordt is me niet helemaal duidelijk.

Het gaat denk ik om de teller van pphlogger.

Warning Line 322 column 80: cannot generate system identifier for general entity "st".
....nl/pphlogger/pphlogger.php?id=nieuws&st=img"></noscript>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 "&amp;" (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 &aelig; 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.

Groetjes,
Tim
 
K i p

K i p

30/10/2006 17:20:00
Quote Anchor link
Dat is dus wat Mebus zegt.

verander
pagina.php?a=hoi&b=hallo
in
pagina.php?a=hoi&amp;b=hallo
 
Tim

Tim

30/10/2006 17:37:00
Quote Anchor link
Super! bedankt nu is de test zonder een error geslaagd.

Groetjes,
Tim
 



Overzicht Reageren

 
 

Om de gebruiksvriendelijkheid van onze website en diensten te optimaliseren maken wij gebruik van cookies. Deze cookies gebruiken wij voor functionaliteiten, analytische gegevens en marketing doeleinden. U vindt meer informatie in onze privacy statement.