TYPO3 Core

Hey and thanks for the report, I analyzed the issue a bit further.

Basically when adding an object to the cObjectViewhelper it automatically calls every public get... method available regardless of whether that method is in fact a simple getter or does more intensive computing - as it's probably originally meant to be used with simple models where that actually makes sense.

As we need to keep things backwards-compatible and getForLocalProcessing is an interface method we can't easily change things there.

There are multiple ways to tackle the issue anyhow but all I found are a bit ugly:

- Convert {image} in your example to an array with only necessary properties yourself before handing it over to the CObjectViewhelper
- Check for FileReference class in cObjectViewhelper to handle that differently (which is ugly as it would potentially mean building exceptions for single class types all over)

Do you (or anyone) have a better idea that keeps backwards compatibility?

As nobody else had any idea I would recommend going with Kais workaround if this happens in your projects. Going to close the issue now - so we have it documented as quirky.