[TYPO3-mvc] ExtBase 1.3 and cache

[Pankaj Lele]

Hello

I am trying out blog_example 1.2.0 from GIT with TYPO3 4.5.2. It seems 
the non-cachable controller actions are not handled properly and I 
always see the Blog/index action with link to Create new blog.

BTW, everything works fine if I set the page record to Cache=Disabled.

I have seen in ExtBase 1.2.x where TS conditions are generated to render 
the content element as USER_INT if the requested controller/action is 
registered as non-cached in Tx_Extbase_Utility_Extension::configurePlugin().

Now I looked into code of ExtBase 1.3 (which came with TYPO3 4.5.2) and 
there are no more TS conditions and the content element is always USER. 
Then I came to know that now it's handled through 
Tx_Extbase_MVC_Web_FrontendRequestHandler::handleRequest() via bootstrap.

I can see following TS in object browser.

[blogexample_pi1] = USER # TypoScript added by extension "BlogExample" # 
Setting BlogExample plugin TypoScript
[userFunc] = tx_extbase_core_bootstrap->run
[extensionName] = BlogExample
[pluginName] = Pi1

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?

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.

Am I missing something to be done with ExtBase 1.3 specific settings?

Thanks
-- 

With best regards,
Pankaj Lele
---------------------------

CTO & Executive Director
Lelesys Infotech Pvt. Ltd.
Pune/Goa, India

Web: http://www.lelesys.com

[Certified TYPO3 Integrator]