[TYPO3-mvc] ExtBase 1.3 and cache

[Franz Koch]

Hey,

...
> My question is, if the object "blogexample_pi1" is set permanently to be
> USER (cached) then how TYPO3 knows that it should be rendered out of the
> cache?

it's not permanently set to USER. There is a method to dynamically 
convert any USER object to USER_INT since TYPO3 4.4 and Extbase is now 
making use of it. The old TS condition approach had quite some issues.

> For example if I submit new blog form to the action =
> "index.php?id=2&tx_blogexample_pi1[action]=create&tx_blogexample_pi1[controller]=Blog"
> then in this case TYPO3 treats this as USER object and never goes to the
> tx_extbase_core_bootstrap->run and it shows the old cached content of
> Blog/index.

Having cached actions at first and then trying to trigger a noncached 
one is always a problem - regardless of Extbase or not. You would have 
to pass a cHash along with the action in order to tell TYPO3 to render 
the page again - but USER_INT plugins shouldn't pass cHashes as they 
would trigger new entries in the page cache where they in general are 
not needed. I already discussed this with Bastian and we didn't come up 
with a overall solution for those scenarios except of putting USER and 
USER_INT action on different pages for now.

-- 
kind regards,
Franz Koch