[TYPO3-german] Fluid Typo3 9.5.3 nur bei ColPos= 0 dem <p>-Tag eine Klasse zuweisen

Heike Herzog-Kuhnke hhk at kuhnke-owl.de
Sat Jan 12 16:48:28 CET 2019


Also ich hatte es jetzt noch mal in meinem Typoskript für den 
MainContent drin und hier hat mir die Template Analyse freundlich 
mitgeteilt, dass ihr drei schließende Klammern fehlen, die ich eingefügt 
habe (leider ohne erfolg...)

--------------------

[globalVar = TSFE:tt_content|colPos = 0]
# alternativ
// [globalVar = TSFE:tt_content|colPos = 0, CType = text]

lib.parseFunc_RTE {
	externalBlocks := addToList(p)
	externalBlocks = p
	externalBlocks {
		p {
			stdWrap {
     				HTMLparser = 1
     				HTMLparser {
        				 tags.p.fixAttrib.class {
             			default = lead
             			always = 1
             			list = lead
                        }
        	 	        }
         	keepNonMatchedTags = 1
             }
         }
     }
}
[global]
-------------------

Auch der Text mit der Alternative der globalVar Condition hat leider 
nichts gebracht...

LG
Heike

Am 12.01.19 um 08:45 schrieb Heike Herzog-Kuhnke:
> Nachtrag:
> In den Ressourcen der Seite machts das auch nicht :(
> 
> LG
> Heike
> 
> Am 12.01.19 um 08:42 schrieb Heike Herzog-Kuhnke:
>> Hmhhh,
>>
>> also ich hab das jetzt an drei Stellen ausprobiert.
>> Im Objekt selbst:
>> -------------------------
>> lib.mainContent = COA
>>
>> [globalVar = TSFE:tt_content|colPos = 0]
>> # alternativ
>> // [globalVar = TSFE:tt_content|colPos = 0, CType = text]
>>
>> lib.parseFunc_RTE {
>>      externalBlocks := addToList(p)
>>      externalBlocks = p
>>      externalBlocks {
>>          p {
>>              stdWrap {
>>                      HTMLparser = 1
>>                      HTMLparser {
>>                          tags.p.fixAttrib.class {
>>                          default = lead
>>                          always = 1
>>                          list = lead
>>                  }
>>              keepNonMatchedTags = 1
>>      }
>> }
>>
>> [global]
>>
>> lib.mainContent {
>>              10 = COA
>>              10 < styles.content.get
>>              10.select.where = colPos=0
>>
>>
>>        }
>> }
>>
>> ---------------------
>>
>> ändert nix...
>>
>> Im Typoskript der Seite:
>> mal so:
>> -----------------------
>> config {
>>    doctype = xhtml_trans
>>    htmlTag_langKey = de
>>    xmlprologue = none
>>    language= de
>>    locale_all = de_DE
>>    contentObjectExceptionHandler = 0
>>    }
>>
>>
>> page = PAGE
>> page.shortcutIcon = fileadmin/templates/images/favicon.ico
>> page.meta.viewport  = width=device-width, initial-scale=1.0
>>
>>
>> [globalVar = TSFE:tt_content|colPos = 0]
>> # alternativ
>> // [globalVar = TSFE:tt_content|colPos = 0, CType = text]
>>
>> lib.parseFunc_RTE {
>>      externalBlocks := addToList(p)
>>      externalBlocks = p
>>      externalBlocks {
>>          p {
>>              stdWrap {
>>                      HTMLparser = 1
>>                      HTMLparser {
>>                          tags.p.fixAttrib.class {
>>                          default = lead
>>                          always = 1
>>                          list = lead
>>                  }
>>              keepNonMatchedTags = 1
>>      }
>> }
>>
>> [global]
>>
>> page {
>>      1 = FLUIDTEMPLATE
>>      1 {
>>          file = fileadmin/templates/BootstrapOWL/templates/template.html
>>          partialRootPath = fileadmin/templates/BootstrapOWL/partials
>>          layoutRootPath = fileadmin/templates/BootstrapOWL/layouts
>>
>>      }
>>
>>      includeCSS.bootCSS = 
>> fileadmin/templates/BootstrapOWL/css/bootstrap.css
>>      includeCSS.carousel = 
>> fileadmin/templates/BootstrapOWL/css/caroussel.css
>>      includeJSFooter.jquery = 
>> https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js
>>      includeJSFooter.bootstrap = 
>> fileadmin/templates/BootstrapOWL/js/bootstrap.min.js
>>      includeJSFooter.iewa = 
>> fileadmin/templates/BootstrapOWL/ja/ie10-viewport-bug-workaround.js
>>
>>      variables {
>>        hauptText < styles.content.get
>>        hauptText.select.where = colPos=0
>>
>>      }
>> }
>> --------------------------
>>
>> und mal so:
>>
>> --------------------------
>>
>> config {
>>    doctype = xhtml_trans
>>    htmlTag_langKey = de
>>    xmlprologue = none
>>    language= de
>>    locale_all = de_DE
>>    contentObjectExceptionHandler = 0
>>    }
>> [globalVar = TSFE:tt_content|colPos = 0]
>> # alternativ
>> // [globalVar = TSFE:tt_content|colPos = 0, CType = text]
>>
>> lib.parseFunc_RTE {
>>      externalBlocks := addToList(p)
>>      externalBlocks = p
>>      externalBlocks {
>>          p {
>>              stdWrap {
>>                      HTMLparser = 1
>>                      HTMLparser {
>>                          tags.p.fixAttrib.class {
>>                          default = lead
>>                          always = 1
>>                          list = lead
>>                  }
>>              keepNonMatchedTags = 1
>>      }
>> }
>>
>> [global]
>>
>>
>> page = PAGE
>> page.shortcutIcon = fileadmin/templates/images/favicon.ico
>> page.meta.viewport  = width=device-width, initial-scale=1.0
>>
>>
>>
>> page {
>>      1 = FLUIDTEMPLATE
>>      1 {
>>          file = fileadmin/templates/BootstrapOWL/templates/template.html
>>          partialRootPath = fileadmin/templates/BootstrapOWL/partials
>>          layoutRootPath = fileadmin/templates/BootstrapOWL/layouts
>>
>>      }
>>
>>      includeCSS.bootCSS = 
>> fileadmin/templates/BootstrapOWL/css/bootstrap.css
>>      includeCSS.carousel = 
>> fileadmin/templates/BootstrapOWL/css/caroussel.css
>>      includeJSFooter.jquery = 
>> https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js
>>      includeJSFooter.bootstrap = 
>> fileadmin/templates/BootstrapOWL/js/bootstrap.min.js
>>      includeJSFooter.iewa = 
>> fileadmin/templates/BootstrapOWL/ja/ie10-viewport-bug-workaround.js
>>
>>      variables {
>>        hauptText < styles.content.get
>>        hauptText.select.where = colPos=0
>>
>>      }
>> }
>>
>> ----------------------
>>
>> Eigentlich war ich sicher, dass die Stelle innerhalb von PAGE richtig 
>> ist. Muss ich das gegebenenfalls in den Ressourcen der Seite mitgeben 
>> und nicht in den Skripts?
>>
>> <p> ist aktuell noch ohne Klasse...
>>
>>
>> Danke Dir nochmal.
>>
>> LG
>> Heike
> 



More information about the TYPO3-german mailing list