Nikita Hovratov

Actually I was thinking about introducing relation resolving also for native types based on the TCA definition. We already introduced a simple TcaSchema to read TCA in a structured way....

@tehplague I agree we should implement ArrayAccess. I'm not sure myself, why I didn't do it. There was an issue with Fluid when the properties are not defined as class...

> To elaborate a bit: why can't we just let `ContentBlockData::__get` fallback to `_raw` instead of immediately returning `NULL` if a key was not found in `_processed`? We probably should....

Update: The ArrayAccess interface is implemented now: https://github.com/nhovratov/content-blocks/pull/220 The ContentBlockData is now based on the new Core Record Object: https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.2/Index.html So manipulating _processed would be possible now this way with...

@helhum Are you able to help us out here? Simply some advise would be sufficient if you are not able help hands on.

@helhum I believe this is not so dramatic anymore as it used to be. The symlinks are created as soon as TYPO3 boots e.g. with `typo3 cache:warmup`. So in deployment...

Thanks Helmut, we adapted your suggestion with symlinking into the Resources/Public folder. Tests already work. We will do some more testing and maybe check if junctions are easy to implement...

If we do this, it should align we the possibilities of the standard AssetCollectors. So it should be made a Core features first. See issues: https://forge.typo3.org/issues/91312, https://forge.typo3.org/issues/93511

Yep, it was invertStateDisplay: https://forge.typo3.org/issues/96135 This has to be fixed first in Core.

This might be fixed with https://review.typo3.org/c/Packages/TYPO3.CMS/+/77018 We also do not use custom asset ViewHelpers anymore in v13, so I'll close this issue :)