CODEWITHSUNDEEP
htmltypo3typoscripttypo3-8.xfluid-styled-content
Daniel Wagner
Daniel Wagner

Reputation: 95

Typo3-Fluid doesnt render my Content Elements | Error : "Content Element with uid "189" and type "text" has no rendering definition!"

i am trying to setup a Typo3 (v.8.7.27) Homepage using Fluid and Backendlayouts. First i created a Backendlayout (uid = 4) and also a new Template-Html (...\Resources\Private\Templates\Page\Test1). I edited my setup.typoscript for the extension and added the following Code (actuelly just the part with the 4 / 4.) 

   10 = FLUIDTEMPLATE
   10 {
      templateName = TEXT
      templateName.stdWrap.cObject = CASE
      templateName.stdWrap.cObject {
         key.data = pagelayout

         pagets__site_theme_default = TEXT
         pagets__site_theme_default.value = Default

         4 = TEXT
         4.value = Test1

         default = TEXT
         default.value = Default
      }

My Test1.html looked like this:

<f:layout name="Default" />
<f:section name="Main">
   <main role="main">
        <f:cObject typoscriptObjectPath="lib.dynamicContent" data="{pageUid: '{data.uid}', colPos: '11', wrap: '<div class=\"hero\">|</div>'}" />
   </main>
</f:section>

Here is the Problem: Everything worked but it didnt render the Content - instead it "wrapped" the Error Msg: " Content Element with uid "189" and type "text" has no rendering definition!"

<div class="hero">
   <p style="background-color: yellow; padding: 0.5em 1em;">
      <strong>ERROR:</strong> Content Element with uid "189" and type "text" has no rendering definition!
   </p>
</div>

In the Backend i added this Backendlayout to the Rootpage and created the Content Element for colPos 11 - its just a simple Text. I have problems understand what could be wrong as it correctly shows the uid of the Contentelement in the Error msg... Any idears?

Thank you for your help! And please write if you need more information Daniel

Upvotes: 1

Views: 2723

Answers (1)

Daniel Wagner
Daniel Wagner

Reputation: 95

The Import of Fluid had a syntax mistake. The Problem is fixed - thanks to @bandanh. If you have a problem like this check your TypoScript Objekt Browser and look for unexpected stuff / missing Objects.

Thank you, Daniel

Upvotes: 1

Related Questions