[TYPO3-UG Italy] metatag e xhtml_cleaning

Tue Dec 7 10:13:03 CET 2010

Niente da fare, nonostante la modifica in:

page.stdWrap.HTMLparser.xhtml_cleaning = all

l'effetto resta invariato.

Ho il sospetto che questa issue (applicata al trunk 4.4), vedi  
intervento di Buelter al termine:

http://bugs.typo3.org/view.php?id=236

c'entri in qualche modo... tu che pensi?

Quoting Roberto Torresani <erreti at siel.it>:

> Ciao Alessandro!
> prova ad aggiungere
>
> page.config.xhtml_cleaning      = all
> (
> http://typo3.org/documentation/document-library/references/doc_core_tsref/4.3.2/view/1/6/#id2511889
> )
>
> Ciao
> Roberto
>
>
> Il giorno 07 dicembre 2010 09:29, Alessandro Tuveri <at at uniud.it> ha
> scritto:
>
>> Grazie, eccol il TS:
>>
>> //setup XHTML Transitional 1.0
>> page.config.doctype = <?xml version="1.0" encoding="utf-8"?><!DOCTYPE html
>> PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "
>> http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
>> page.config.htmlTag_setParams = lang="it" xml:lang="it" xmlns="
>> http://www.w3.org/1999/xhtml"
>>
>> e poi:
>>
>> page.meta.author= {$mysite.metaAuthor}
>> page.meta.revisit-after = {$mysite.revisitAfter}
>> page.meta.verify-v1 = {$mysite.googleVerify}
>>
>> per xhtml cleaning:
>>
>> page.stdWrap.HTMLparser = 0
>> page.stdWrap.HTMLparser.allowTags =
>> style,form,input,b,i,u,a,img,br,div,center,pre,font,hr,sub,sup,p,strong,em,li,ul,ol,blockquote,strike,span,h1,h2,h3,h4,h5,h6,dt,dl,dd,th,table,tr,td,tbody,noscript,iframe,script
>> page.stdWrap.HTMLparser.tags.img.allowedAttribs =
>> src,width,height,title,alt,style,name
>> page.stdWrap.HTMLparser.xhtml_cleaning = 0
>>
>> --- se lascio cosi' i tag non vengono corretti e chiusi con " />" in
>> pratica restano ">".
>>
>> come soluzione (workaround) ho scritto questo:
>> (nota: situato alla fine del documento TS)
>>
>> page.meta >
>>
>> page.headerData.26 = TEXT
>> page.headerData.26.stdWrap.cObject < temp.siteDescription
>> page.headerData.26.wrap = <meta name="description" content="|" />
>> page.headerData.27 = TEXT
>> page.headerData.27.stdWrap.cObject < temp.siteKeywords1
>> page.headerData.27.wrap = <meta name="keywords" content="|" />
>> page.headerData.28 = TEXT
>> page.headerData.28.value (
>> <meta name="author" content="{$mysite.metaAuthor}" />
>> <meta name="revisit-after" content="{$mysite.revisitAfter}" />
>> <meta name="verify-v1" content="{$mysite.googleVerify}" />
>> <meta name="X-UA-Compatible" content="IE=EmulateIE7" />
>> <meta http-equiv="Content-Type" content="text/html;
>> charset={$mysite.charSet}
>> " />
>> )
>> page.headerData.28.insertData = 1
>>
>> (nota: dove temp.siteDescription e temp.siteKeywords sono due oggetti
>> creati per generare le parole chiave).
>>
>> qui accade questo: i metatag sono generati correttamente (e' ovvio) ma
>> vengono aggiunti da TYPO3 altri metatag per la versione e il charset, che io
>> NON ho aggiunto (li mette TYPO3):
>>
>>
>> <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
>> <meta name="generator" content="TYPO3 4.4 CMS">
>>
>> e si vede chiaramente che nonostante l'uso di xhtml_cleaning non sono stati
>> "aggiustati".
>>
>> spero basti, grazie e a presto
>>
>>
>>
>> Quoting Roberto Torresani <erreti at siel.it>:
>>
>>  Ciao Alessandro!
>>> quali sono le configurazioni di  typoscript che utilizzi per
>>> personalizzare
>>> l'header della pagina? Potrebbe essere qualcosa da integrare in questa
>>> parte
>>> per risolvere il tuo problema.
>>>
>>> Ciao
>>> Roberto
>>>
>>>
>>> Il giorno 06 dicembre 2010 16:01, Alessandro Tuveri <at at uniud.it> ha
>>> scritto:
>>>
>>>  Salve a tutti
>>>> da qualche giorno e dopo aver aggiornato correttamente vari siti dalla
>>>> v.4.2.15 alla v. 4.4.4 ho notato che, pur attivando la pulizia xhtml per
>>>> il
>>>> rendering compatibile con xhtml Transitional 1.0
>>>> i tag generati automaticamente da TYPO3, ovvero:
>>>>
>>>> tutti i META TAG
>>>> (io li genero con: page.meta.NOME_DEL_TAG = <valore>)
>>>>
>>>> e altri tag situati nella header, come:
>>>> <link rel="stylesheet" type="text/css"
>>>> href="typo3temp/stylesheet_fa0cd332a5.css?1291300775" media="all">
>>>>
>>>> non vegono sottoposti alla pulizia, in pratica il test di compatibilita'
>>>> non e' superato il quanto il tag non e' chiuso correttamente con " /> "
>>>>
>>>> ora: mentre il problema puo' essere superato per i meta tag (e'
>>>> sufficiente
>>>> aggirare TYPO3 usando piu' proprieta' del tipo:
>>>>
>>>> page.headerData.10 = TEXT
>>>> page.headerData.10.data (... eccetera...)
>>>>
>>>> TYPO3 aggiunge comunque il tag meta per la versione e il charset:
>>>> <meta name="generator" content="TYPO3 4.4 CMS">
>>>> <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
>>>>
>>>> come si vede sopra NON nel formato corretto per XHTML.
>>>>
>>>> quindi: alla fine del giro comunque 5-6 errori di compatibilita' accadono
>>>> comunque a causa di queste "trovate" di TYPO3; nelle precedenti versioni
>>>> non
>>>> avevo alcun problema.
>>>>
>>>> qualcuno sa qualcosa o ha idee?
>>>>
>>>> grazie in anticipo
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Quoting Maurizio Morini <morini at gammsystem.com>:
>>>>
>>>>  Tieni conto che nella seconda skin devi azzerare le configurazioni TS
>>>>
>>>>> preCodeHeader >
>>>>> header >
>>>>> postCodeHeader >
>>>>>
>>>>> in modo che non si sovrappongano
>>>>>
>>>>> ciao M
>>>>>
>>>>> Il 03/12/2010 16.39, Nicola Cerchiari ha scritto:
>>>>>
>>>>>  Grandissimo aiuto davvero.
>>>>>> La necessità di due skin su due sotto alberi nasce dal fatto che ad
>>>>>> esempio
>>>>>> un sito contiene due versioni (anno dopo anno) che vengono
>>>>>> completamente
>>>>>> riviste dal punto di vista grafico ed editoriale e devono comunque
>>>>>> coesistere.
>>>>>> Comunque farò delle prove con il tuo prezioso suggerimento e ti farò
>>>>>> sapere.
>>>>>>
>>>>>> Grazie,
>>>>>> Nicola
>>>>>>
>>>>>> Il giorno 03 dicembre 2010 16:33, Maurizio Morini<
>>>>>> morini at gammsystem.com>
>>>>>>  ha
>>>>>> scritto:
>>>>>>
>>>>>>  Ciao Nicola,
>>>>>>
>>>>>>> ti riporto la risposta di Ron Hall di TemplavoilaFrameWork alla tua
>>>>>>> domanda.
>>>>>>>
>>>>>>> *******************
>>>>>>> The Framework skin selector has to be on a root level of the site so
>>>>>>> does
>>>>>>> not really fit the situation you describe.However, a couple of
>>>>>>> thoughts
>>>>>>> on
>>>>>>> that.
>>>>>>>
>>>>>>> 1) I question whether that would be needed. After all you would
>>>>>>> normally
>>>>>>> either use different templates in the same skin for that section of
>>>>>>> the
>>>>>>> site
>>>>>>> or else rewrite your TS objects thus overriding the original objects
>>>>>>> for
>>>>>>> that section of the site
>>>>>>>
>>>>>>> 2) If you really did have to do a new skin then you could probably
>>>>>>> manually
>>>>>>> unset and then reset paths for things like the CSS, JS, TS etc.
>>>>>>>
>>>>>>> At some point we may have it so that skins could be changed with TS
>>>>>>> for
>>>>>>> things like a mobile site but it would still be on the root template.
>>>>>>> *******************
>>>>>>>
>>>>>>>
>>>>>>> Ho fatto una prova veloce che consiste:
>>>>>>> 1) settare una skin nello skin selector (ad esepio wireframe)
>>>>>>> 2) definire un ext template per una pagina interna specificando nelle
>>>>>>> costants
>>>>>>>
>>>>>>> <INCLUDE_TYPOSCRIPT: source="FILE:
>>>>>>> typo3conf/ext/skin_regal/typoscript/skin_constants.ts">
>>>>>>> bnTemplates.skinPath = typo3conf/ext/skin_regal/
>>>>>>> templavoila_framework.skinPath = typo3conf/ext/skin_regal/
>>>>>>>
>>>>>>> nel setup:
>>>>>>> <INCLUDE_TYPOSCRIPT: source="FILE:
>>>>>>> typo3conf/ext/skin_regal/typoscript/skin_typoscript.ts">
>>>>>>>
>>>>>>>
>>>>>>> Come vedi ho ridefinito la skin wireframe con la skin regal
>>>>>>> e la cosa sembra funzionare...
>>>>>>>
>>>>>>> Spero di essere stato d'aiuto.
>>>>>>> ciao M
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Morini Maurizio
>>>>>>> Gamm System Srl
>>>>>>> www.gammsystem.com
>>>>>>> morini at gammsystem.com
>>>>>>>
>>>>>>>
>>>>>>> Il 01/12/2010 14.04, Nicola Cerchiari ha scritto:
>>>>>>>
>>>>>>>  Salve a tutti,
>>>>>>>
>>>>>>>>
>>>>>>>> vorrei porre domanda che mi è venuta in mente testando l'estensione
>>>>>>>> "templavoila framework" presentata al T3Camp Italia (tanto per citare
>>>>>>>> le
>>>>>>>> fonti ;) ).
>>>>>>>> E' effettivamente molto comoda ed intuitiva, come aveva già ben
>>>>>>>> dimostrato
>>>>>>>> Maurizio (perdonami se per caso sbaglio nome), ma per poterla
>>>>>>>> introdurre
>>>>>>>> nel
>>>>>>>> nostro flusso di lavoro viste le nostre esigenze, mi chiedevo se
>>>>>>>> fosse
>>>>>>>> possibile poter specificare skin diverse a livello di sotto-alberi di
>>>>>>>> un
>>>>>>>> sito.
>>>>>>>> Ho notato che se creo un template ext+ in un sotto-albero il tab
>>>>>>>> "skin
>>>>>>>> selector" non compare, quindi temo non si possa fare, però qualcuno
>>>>>>>> sa
>>>>>>>> se
>>>>>>>> è
>>>>>>>> per caso è possibile in qualche altro modo?
>>>>>>>>
>>>>>>>> Grazie ancora a tutti,
>>>>>>>> Nicola
>>>>>>>>
>>>>>>>>  _______________________________________________
>>>>>>>>
>>>>>>> TYPO3-UG-Italy mailing list
>>>>>>> TYPO3-UG-Italy at lists.typo3.org
>>>>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-ug-italy
>>>>>>>
>>>>>>>  _______________________________________________
>>>>>>>
>>>>>> TYPO3-UG-Italy mailing list
>>>>> TYPO3-UG-Italy at lists.typo3.org
>>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-ug-italy
>>>>>
>>>>>
>>>>
>>>>
>>>> ALESSANDRO TUVERI
>>>>
>>>> --------------------------------------
>>>> SERVIZI WEB D'ATENEO
>>>> CSIT, Centro Servizi Informatici e Telematici
>>>> Università degli Studi di Udine
>>>> tel. ufficio 0432-558904
>>>> --------------------------------------
>>>> Homo sine pecunia est imago mortis
>>>> --------------------------------------
>>>>
>>>> ----------------------------------------------------------------------
>>>> SEMEL (SErvizio di Messaging ELettronico) - CSIT -Universita' di Udine
>>>>
>>>> _______________________________________________
>>>> TYPO3-UG-Italy mailing list
>>>> TYPO3-UG-Italy at lists.typo3.org
>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-ug-italy
>>>>
>>>
>>>
>>>
>>>
>>> --
>>> 27 novembre 2010, Bologna, T3Camp Italia: Typoscript, questo
>>> sconosciuto<
>>> http://www.t3campitalia.it/programma-talk-conferenza-typo3/typoscript-questo-sconosiuto.html
>>> >
>>> _______________________________________________
>>> TYPO3-UG-Italy mailing list
>>> TYPO3-UG-Italy at lists.typo3.org
>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-ug-italy
>>>
>>>
>>
>>
>> ALESSANDRO TUVERI
>>
>> --------------------------------------
>> SERVIZI WEB D'ATENEO
>> CSIT, Centro Servizi Informatici e Telematici
>> Università degli Studi di Udine
>> tel. ufficio 0432-558904
>> --------------------------------------
>> Homo sine pecunia est imago mortis
>> --------------------------------------
>>
>> ----------------------------------------------------------------------
>> SEMEL (SErvizio di Messaging ELettronico) - CSIT -Universita' di Udine
>>
>> _______________________________________________
>> TYPO3-UG-Italy mailing list
>> TYPO3-UG-Italy at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-ug-italy
>>
>
>
>
> --
> 27 novembre 2010, Bologna, T3Camp Italia: Typoscript, questo
> sconosciuto<http://www.t3campitalia.it/programma-talk-conferenza-typo3/typoscript-questo-sconosiuto.html>
> _______________________________________________
> TYPO3-UG-Italy mailing list
> TYPO3-UG-Italy at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-ug-italy
>

ALESSANDRO TUVERI

--------------------------------------
SERVIZI WEB D'ATENEO
CSIT, Centro Servizi Informatici e Telematici
Università degli Studi di Udine
tel. ufficio 0432-558904
--------------------------------------
Homo sine pecunia est imago mortis
--------------------------------------

----------------------------------------------------------------------
SEMEL (SErvizio di Messaging ELettronico) - CSIT -Universita' di Udine