Validazione HTML 10 errori

Salve,
mi sono comparsi 10 errori nella validazione del sito su https://validator.w3.org/check?uri=h...org%2Fservices

Come posso risolvere?

Validation Output: 10 Errors

Error Line 17, Column 48: there is no attribute "sizes"

…="apple-touch-icon-precomposed" sizes="144x144" href="http://cdn.iabasic1.alte…

✉

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 110, Column 99: there is no attribute "placeholder"

…="text" name="username" class="input-small" size="14" placeholder="Username" />

✉

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 170, Column 34: "itemscope" is not a member of a group specified for any attribute

<div class="item-page" itemscope itemtype="https://schema.org/Article">

✉
Error Line 170, Column 43: there is no attribute "itemtype"

<div class="item-page" itemscope itemtype="https://schema.org/Article">

✉

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 171, Column 16: there is no attribute "itemprop"

<meta itemprop="inLanguage" content="it-IT" />

✉

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 171, Column 46: document type does not allow element "meta" here

<meta itemprop="inLanguage" content="it-IT" />

✉

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 173, Column 14: there is no attribute "itemprop"

<h2 itemprop="name">

✉

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 176, Column 15: there is no attribute "itemprop"

<div itemprop="articleBody">

✉

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 271, Column 50: end tag for "img" omitted, but OMITTAG NO was specified

alt="Valid robots.txt" width="80" height="15"></a>

✉

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 270, Column 1: start tag was here

<img src="http://tool.motoricerca.info/pic/valid-robots-small.png" border="0"

Error Line 308, Column 8: required attribute "type" not specified

<script>(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||functi…

✉

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>.

Stessa cosa anche per il CSS qui: http://jigsaw.w3.org/css-validator/v...rning=&lang=it

?????

[darbula]

Ehm ti indica esattamente la posizione dove dovresti modificarlo per renderlo valido.. Ora gli errori sono 11.. primo errore ai due title, secondo errore cambia in size, terzo errore cambia in placefolder, quarto errore itemtype ma credo sia riferito all'attributo itemscope che non ha valore e neanche le virgolette(ma non conosco joomla e potrei anche sbagliarmi).. non ho trovato ulteriori indicazioni su joomla mi dispiace.. https://docs.joomla.org/Microdata per itemtype ed altro. Speriamo che non sia un'attacco e sei stato involontariamente a modificare ciò

Title l'ho proprio cancellato dal file index.php del tempalte .... E me lo mostra ancora in W3C....


Ma gli altri errori non so proprio dove siano per metterci mano....

[darbula]

Ma W3C a ragione poichè legge il sorgente.., puoi provare a svuotare la cache di cloudfare http://it.help.altervista.org/w/CloudFlare (dal pannello di controllo altervista).
ps. nemmeno io so dove siano gli errori visto che stiamo parlando di xhtml che diversamente da html a elementi e attributi documentati (cioé non se ne possono inserire nuovi a differenza di xhtml)

Su joomla come è possibile modificare il codice sorgente....

Se non so dove metter mano come risolvo? :D

CloudFlare non ce l'ho attivo

[darbula]

ehm posta nella sezione joomla qui o nel loro forum per maggiori info.. Comunque per modificare qualcosa ci sono due cose che dovresti conoscere, il primo il linguaggio php e secondo la struttura di joomla altrimenti i cambiamenti fatti alla cieca non darebbero i suoi frutti... Studia mi raccomando

Questi due errori sono di un modulo con codice HTML al proprio interno

Come posso risolverli?

Error Line 251, Column 47: end tag for "img" omitted, but OMITTAG NO was specified

alt="Valid robots.txt" width="80" height="15"> </a>

✉

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 250, Column 1: start tag was here

<img src="http://tool.motoricerca.info/pic/valid-robots-small.png" border="0"

[darbula]

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 250, Column 1: start tag was here come dice lui stesso basta inserire spaziobianco/>.. altrimenti per il html sarebbe stato solo > Hai messo un modulo html dentro un documento xhtml? lo sai che ci sono differenze sui tag di chiusura

Custom HTML advanced uso questa estensione per pubblicare codici, sennò altrimenti come potrei pubblicare la validazione del file robots.txt?

[darbula]

adeguando il sorgente html al xhtml.. in paticolare per gli elementi vuoti. http://www.w3c.it/traduzioni/xhtml1-it.html visualizza anche l'appendice C.2.
Ma ora potrebbe entrare in gioco un'altro fattore, poiché alcuni editor inseriscono in modo erroneo un carattere non stampabile dove inizialmente sembra un classico carattere di spazio ma invece non lo é..(per farsi un'idea mi riferisco ad esso come nome d'entità &nbsp;) in utf-8 occupa due byte.
Questo richiede una conoscenza piú ampia..ma se il validatore ti segnala errore é la sintassi sembra giusta.. allora il problema sarà &nbsp;