Errori per la sitemap

di il
11 risposte

Errori per la sitemap

Come richiesto, vi posto gli errori che mi da il validator quando vado a creare una sitemap.
C'è da dire che l'errore del "b&b" l'ho risolto, o meglio credevo di averlo fatto, sostituendo & con &amp, e invece pare stia ancora qui.
Che devo fare? Vi prego aiutatemi.

Validation Output: 9 Errors

1. Warning Line 6, Column 64: cannot generate system identifier for general entity "b"

…nt="trova locali, locali, hotel, b&b, discoteca, pub, notte, albergo, agritu

?

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.
2. Error Line 6, Column 64: general entity "b" not defined and no default entity

…nt="trova locali, locali, hotel, b&b, discoteca, pub, notte, albergo, agritu

?

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.
3. Warning Line 6, Column 65: reference not terminated by REFC delimiter

…t="trova locali, locali, hotel, b&b, discoteca, pub, notte, albergo, agritur

?

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.
4. Warning Line 6, Column 65: reference to external entity in attribute value

…t="trova locali, locali, hotel, b&b, discoteca, pub, notte, albergo, agritur

?

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 '&'.
5. Error Line 6, Column 65: reference to entity "b" for which no system identifier could be generated

…t="trova locali, locali, hotel, b&b, discoteca, pub, notte, albergo, agritur

?

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.
6. Info Line 6, Column 62: entity was defined here

…tent="trova locali, locali, hotel, b&b, discoteca, pub, notte, albergo, agri

7. Error Line 11, Column 45: Attribute "frameborder" exists, but can not be used for this element.

<frameset rows="*" cols="240,*" frameborder="no" border="0" framespacing="0">

?

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.
8. Error Line 11, Column 57: Attribute "border" exists, but can not be used for this element.

<frameset rows="*" cols="240,*" frameborder="no" border="0" framespacing="0">

?

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.
9. Error Line 11, Column 74: Attribute "framespacing" is not a valid attribute

… frameborder="no" border="0" framespacing="0">

?

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.
10. Error Line 13, Column 61: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"

…html" name="topFrame1" scrolling="No" noresize="noresize" id="topFrame1" titl

?

The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
11. Error Line 17, Column 67: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"

….html" name="topFrame" scrolling="No" noresize="noresize" id="topFrame" title

?

The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
12. Error Line 21, Column 10: document type does not allow element "noframes" here

<noframes><body>

?

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).
13. Error Line 6, Column 64: XML Parsing Error: EntityRef: expecting ';'

…nt="trova locali, locali, hotel, b&b, discoteca, pub, notte, albergo, agritu

11 Risposte

  • Re: Errori per la sitemap

    Ciao Tabbo,
    prova a sostituire:
    &
    con
    &

    non ti scordare il punto e virgola.
    Fammi sapere, ciao
  • Re: Errori per la sitemap

    Ho risolto sostituendo B&B con Bed and Breakfast

    Ora i problemi restanti sono quelli qui sotto

    Validation Output: 6 Errors

    1. Error Line 11, Column 45: Attribute "frameborder" exists, but can not be used for this element.

    <frameset rows="*" cols="240,*" frameborder="no" border="0" framespacing="0">

    ?

    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.
    2. Error Line 11, Column 57: Attribute "border" exists, but can not be used for this element.

    <frameset rows="*" cols="240,*" frameborder="no" border="0" framespacing="0">

    ?

    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.
    3. Error Line 11, Column 74: Attribute "framespacing" is not a valid attribute

    … frameborder="no" border="0" framespacing="0">

    ?

    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.
    4. Error Line 13, Column 61: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"

    …html" name="topFrame1" scrolling="No" noresize="noresize" id="topFrame1" titl

    ?

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
    5. Error Line 17, Column 67: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"

    ….html" name="topFrame" scrolling="No" noresize="noresize" id="topFrame" title

    ?

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
    6. Error Line 21, Column 10: document type does not allow element "noframes" here

    <noframes><body>

    ?

    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).
  • Re: Errori per la sitemap

    Ciao il problema é semplice.

    Hai dichiarato nel prologo del documento XHTML che é di tipo strict (non vuole attributi di formattazione sul codice, vanno messi nel CSS), altrimenti scegli il tipo Transitional che é di bocca buona e accetta ancora molti attributi in line.

    Ciao
  • Re: Errori per la sitemap

    Problema: dove lo devo modificare?
  • Re: Errori per la sitemap

    Ciao

    é la prima riga del codice HTML delle tue pagine.
  • Re: Errori per la sitemap

    Problemi risolti.... a modo mio (un po' drastico).
    Ho tolto quello che non andava. Potresti gentilmente verificare che il sito lo vedi bene?
    Grazie mister
    PS Stavo pensando: se l'inserimento della sitemap non da i suoi frutti, potrei fare una "zozzata", ovvero fare l'home page senza frame, simile (anzi quasi emulata) quella che c'è ora, e collegare il menù a dei frameset che riproducono esattamente l'effetto frame che si vede ora il home page.
    così facendo pensi che Google l'home page me la indicizzerebbe meglio?
    Grazie mio mèntore
    (Hai visto sull'home page di www.ore18.i che cocktail ho messo?)
  • Re: Errori per la sitemap

    Ciao ho visto il cocktail, grande.

    Io ti consiglio ti consiglio di togliere i frame, sia per l'indicizzazione nei motori di ricerca sia per il fatto che fanno tecnologicamente vecchio.
    Ciao
  • Re: Errori per la sitemap

    Sto elaborando....
    Guarda qui e dammi un tuo giudizio
    http://www.trovalocali.it/Prove/Index.htm
  • Re: Errori per la sitemap

    Oh addio frames

    va già meglio, in te rivedrei anche il bordo delle tabelle
  • Re: Errori per la sitemap

    Cosa suggerisci per i bordi delle tabelle?
    Di farne sparire qualcuno?
  • Re: Errori per la sitemap

    Alla fine sono tornato all'html. Ora però ho un problema (anzi 10).
    Fatta la nuova pagina ho proceduto con la validazione, per poi fare la sitemap. Inizialmente gli errori erano 51, ora li ho ridotti a 10, però come potete vedere nell'home page (www.trovalocali.i) non riesco a "far tornare su" quello che sta giù. Vi prego aiutatemi che non so più dove mettermi le mani.
    Vi posto qui sotto gli errori, se volete e senza alcun problema, vi posso postare anche il codice nella mia pagina. Aiutooooooooooooooooooooooooooooooooo
    Validation Output: 10 Errors

    1. Error Line 156, Column 21: document type does not allow element "div" here; assuming missing "object" start-tag

    <div id="masterdiv"/>

    ?
    2. Error Line 158, Column 23: document type does not allow element "style" here

    <style type="text/css">

    ?

    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).
    3. Error Line 209, Column 6: document type does not allow element "body" here

    <body>

    ?

    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).
    4. Error Line 453, Column 254: required attribute "alt" not specified

    …idth="259" height="179" border="0" /></p>

    ?

    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>.
    5. Error Line 525, Column 9: end tag for "object" omitted, but OMITTAG NO was specified

    </html>

    ?

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
    6. Info Line 156: start tag was here

    ><div id="masterdiv"/>

    7. Error Line 525, Column 9: end tag for "head" omitted, but OMITTAG NO was specified

    </html>

    ?

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
    8. Info Line 3: start tag was here

    ><head>

    9. Error Line 525, Column 9: end tag for "html" which is not finished

    </html>

    ?

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
    10. Error Line 526, Column 9: end tag for element "head" which is not open

    </head>

    ?

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.
    11. Error Line 525, Column 9: XML Parsing Error: Opening and ending tag mismatch: head line 3 and html

    </html>

    ?
    12. Error Line 526, Column 9: XML Parsing Error: Opening and ending tag mismatch: html line 2 and head

    </head>

Devi accedere o registrarti per scrivere nel forum
11 risposte