Project

General

Profile

Bug #100872

Updated by Alexander Stehlik 10 months ago

 
 When using the @EXTBASEPLUGIN@ content element outside the @lib.contentElement@ context the request attribute @currentContentObject@ is not filled correctly. 

 The problem only occurs when the content is rendered with the f:cObject view helper in a FLUIDTEMPLATE content object. This is a minimal page setup with fluid_styled_content TypoScript included: 

 <pre> 
 lib.content.main < styles.content.get 

 page = PAGE 
 page.100 = FLUIDTEMPLATE 
 page.100.template = TEXT 
 page.100.template.value = <p>The form</p><f:cObject typoscriptObjectPath="lib.content.main"/></p> 
 </pre> 

 It can be tested by changing the config of the @form_formframework@ content element: 

 This works (the default config): 

 <pre> 
 tt_content.form_formframework =< lib.contentElement 
 tt_content.form_formframework { 
     20 = EXTBASEPLUGIN 
     20 { 
         extensionName = Form 
         pluginName = Formframework         
     } 
     templateName = Generic  
 } 
 </pre> 

 When rendering the plugin directly, the @currentContentObject@ is @null@ : 

 <pre> 
 tt_content.form_formframework > 
 tt_content.form_formframework = EXTBASEPLUGIN 
 tt_content.form_formframework { 
     extensionName = Form 
     pluginName = Formframework 
 } 
 </pre> 

 And maybe this is related: I just realized that the settings-Array is also empty in the second example.

Back