TYPO3 Core

@Timo Pfeffer - Can you provide info on how to reproduce the error?

Steps to reproduce:

1) Configure $GLOBALS['TYPO3_CONF_VARS']['SYS']['errorHandlerErrors'] to handle warnings too
2) use f:cObject inside Fluid template without defining the described attributes
3) call "the template" in browser and look into the log module

expected behaviour:
two new entries inside log module for each of the missing attributes.

Hi - tried with

page = PAGE
page.10 = FLUIDTEMPLATE
page.10 {
    template = TEXT
    template.value = <f:cObject typoscriptObjectPath="lib.test" data="foo"/>
}
lib.test = TEXT
lib.test.current = 1

[SYS][errorHandlerErrors] = 30466

Hmm the page of us is full of these warnings.
Is it ensured that optional arguments are filled in $arguments too, although these are not defined in fluid?

Hi @Timo Pfeffer

My output looks like:

/typo3/sysext/fluid/Classes/ViewHelpers/CObjectViewHelper.php:139:
array (size=4)
  'data' => string 'foo' (length=3)
  'typoscriptObjectPath' => string 'lib.test' (length=8)
  'currentValueKey' => null
  'table' => string '' (length=0)

lib.test = TEXT
lib.test.current = 1

Okay then it must be a problem with the current website implementation. I will check it. Perhaps it has been something in common with the temporary fix of another forge ticket of mine, but not sure.
Please leave it open, i will check it in the next hours/days.

yes I have checked it and have solved it, but forget to write it down here. Sadly i don't know anymore what exactly fixed this behaviour. So you can close this ticket.