validation W3C

Bonjour

j’ai passé le site pour essayer de valider au mieux le squelette

SPIP 3.2.1 SVN [24058] + écran de sécurité 1.3.6

plus les trois plugins nécessaire
Agenda 3.20.1 - stable
Escal 4.1.23 - stable

Mini Calendrier 2.4.1 - stable

j’ai 4 errors qui me semble liés a SPIP (mais pas sur) , comment supprimé les 4 errors ?

ou du moins expliqué moi pour ma gouverne perso

merci

Validation Output: 4 Errors1. ErrorLine 340, Column 41: there is no attribute « data-ajax-env »

…  <div class='ajaxbloc' data-ajax-env=**'**ZO/cK2reL3BrY0fsnew6aONk5ohzK7cZycmI5n8…

:email:

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 element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1. ErrorLine 340, Column 260: there is no attribute « data-origin »

    …QbWUGh8b++sX2R5Tt0fSvOUIbzMvcXaasKfaF8/5RQK4kimGTX9oYTna9g==' data-origin=**"**./">
    

    :email:

    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 element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  2. ErrorLine 676, Column 158: there is no attribute « autocapitalize »

    …in' id='var_login' value="" size='40' autocapitalize=**"**off" autocorrect="off" />
    

    :email:

    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 element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  3. ErrorLine 676, Column 176: there is no attribute « autocorrect »

    …in' id='var_login' value="" size='40' autocapitalize="off" autocorrect=**"**off" />
    

    :email:

    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 element to incorporate flash media in a Web page, see the FAQ item on valid flash.

C est des spécifications HTML5. So… Passe ton site en HTML5.

Le dim. 28 oct. 2018 à 11:13, teamspipfactory@gmail.com <teamspipfactory@gmail.com> a écrit :

Bonjour

j’ai passé le site pour essayer de valider au mieux le squelette

SPIP 3.2.1 SVN [24058] + écran de sécurité 1.3.6

plus les trois plugins nécessaire
Agenda 3.20.1 - stable
Escal 4.1.23 - stable

Mini Calendrier 2.4.1 - stable

j’ai 4 errors qui me semble liés a SPIP (mais pas sur) , comment supprimé les 4 errors ?

ou du moins expliqué moi pour ma gouverne perso

merci

Validation Output: 4 Errors1. ErrorLine 340, Column 41: there is no attribute « data-ajax-env »

…  <div class='ajaxbloc' data-ajax-env=**'**ZO/cK2reL3BrY0fsnew6aONk5ohzK7cZycmI5n8…

:email:

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 element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1. ErrorLine 340, Column 260: there is no attribute « data-origin »

    …QbWUGh8b++sX2R5Tt0fSvOUIbzMvcXaasKfaF8/5RQK4kimGTX9oYTna9g==' data-origin=**"**./">
    

    :email:

    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 element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  2. ErrorLine 676, Column 158: there is no attribute « autocapitalize »

    …in' id='var_login' value="" size='40' autocapitalize=**"**off" autocorrect="off" />
    

    :email:

    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 element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  3. ErrorLine 676, Column 176: there is no attribute « autocorrect »

    …in' id='var_login' value="" size='40' autocapitalize="off" autocorrect=**"**off" />
    

    :email:

    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 element to incorporate flash media in a Web page, see the FAQ item on valid flash.

-- 
Courriel: [team@spipfactory.fr](mailto:team@spipfactory.fr)
Site: [https://spipfactory.fr/](https://spipfactory.fr/)
IRC: [https://webchat.freenode.net/?channels=%23%23spipfactory](https://webchat.freenode.net/?channels=%23%23spipfactory)

En répondant a ce courriel vous acceptez implicitement la diffusion, l'échange de la conversation, sauf avis contraire clairement exprimé.

liste spip
spip@rezo.net - désabonnement : envoyer un mail à spip-off@rezo.net

Archives : https://www.mail-archive.com/spip@rezo.net/maillist.html

Infos : https://listes.rezo.net/mailman/listinfo/spip

Documentation de SPIP : http://www.spip.net/

Irc : de l’aide à toute heure : http://spip.net/irc

ok on va regarder ça , vu le chantier ça sera pour plus tard …

Le 09/11/2018 à 21:26, teamspipfactory@gmail.com a écrit :

ok on va regarder ça , vu le chantier ça sera pour plus tard ....

C'est juste une configuration dans le back office, ça devrait pas prendre très longtemps :smiley:

--
nicod_

Le 10/11/2018 à 13:49, nicod_ a écrit :

Le 09/11/2018 à 21:26, teamspipfactory@gmail.com a écrit :

ok on va regarder ça , vu le chantier ça sera pour plus tard ....

C'est juste une configuration dans le back office, ça devrait pas prendre très longtemps :smiley:

alors je veu bien un coup de main ...... nicod_

--
Courriel: team@spipfactory.fr
Site: https://spipfactory.fr/
IRC: https://webchat.freenode.net/?channels=%23%23spipfactory

En répondant a ce courriel vous acceptez implicitement la diffusion, l'échange de la conversation, sauf avis contraire clairement exprimé.

Le 11/11/2018 à 13:39, teamspipfactory@gmail.com a écrit :

Le 10/11/2018 à 13:49, nicod_ a écrit :

Le 09/11/2018 à 21:26, teamspipfactory@gmail.com a écrit :

ok on va regarder ça , vu le chantier ça sera pour plus tard ....

C'est juste une configuration dans le back office, ça devrait pas prendre très longtemps :smiley:

alors je veu bien un coup de main ...... nicod_

Configuration -> Fonctions avancées -> Permettre le HTML5

Il faut juste vérifier que les squelettes commencent bien par <!DOCTYPE html>

C'est quoi ton squelette ?

Tu as une url pour jeter un oeil ?

--
nicod_

Le 11/11/2018 à 14:24, nicod_ a écrit :

Le 11/11/2018 à 13:39, teamspipfactory@gmail.com a écrit :

Le 10/11/2018 à 13:49, nicod_ a écrit :

Le 09/11/2018 à 21:26, teamspipfactory@gmail.com a écrit :

ok on va regarder ça , vu le chantier ça sera pour plus tard ....

C'est juste une configuration dans le back office, ça devrait pas prendre très longtemps :smiley:

alors je veu bien un coup de main ...... nicod_

Configuration -> Fonctions avancées -> Permettre le HTML5

Il faut juste vérifier que les squelettes commencent bien par <!DOCTYPE html>

En résumé, si tes squelettes commencent par :

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd&quot;&gt;

comme dans les squelettes dist, tu remplaces simplement par :

<!DOCTYPE html>

--
nicod_

Le 11/11/2018 à 14:24, nicod_ a écrit :

Le 11/11/2018 à 13:39, teamspipfactory@gmail.com a écrit :

Le 10/11/2018 à 13:49, nicod_ a écrit :

Le 09/11/2018 à 21:26, teamspipfactory@gmail.com a écrit :

ok on va regarder ça , vu le chantier ça sera pour plus tard ....

C'est juste une configuration dans le back office, ça devrait pas prendre très longtemps :smiley:

alors je veu bien un coup de main ...... nicod_

Configuration -> Fonctions avancées -> Permettre le HTML5

Il faut juste vérifier que les squelettes commencent bien par <!DOCTYPE html>

C'est quoi ton squelette ?

c'est ESCAL
https://zone.spip.net/trac/spip-zone/browser/spip-zone/_squelettes_/escal

Tu as une url pour jeter un oeil ?

URL de test
https://escal.spipfactory.fr/essaispip/escalreponsive/

--

Site: https://spipfactory.fr/
Plateforme d’hébergement autogéré en association de loi 1901, mutualisation sous habillage Escal en SPIP 3.2.1 SVN [24137] + écran de sécurité 1.3.8

Courriel: team@spipfactory.fr
IRC: https://webchat.freenode.net/?channels=%23%23spipfactory

En répondant a ce courriel vous acceptez implicitement la diffusion, l'échange de la conversation, sauf avis contraire clairement exprimé.