Bug #60715

non-cacheable action and page cache

Added by Sebastian G over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
-
Start date:
2014-08-01
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2

Description

Hello,

i have an extbase extension with some controllers and actions.
All actions must be non-cacheable, because all the data is dynamic. Two actions are searchforms.
They must be important non cached! But if i don't add the noCache and noCacheHash attribute to fluid form tag, the actions are cached.

I can't find the problem.

Notes:
The page is cached. Is this the issue?

In older extensions for TYPO3 4.5 I must set this function - t3lib_extMgm::addPItoST43 - with the last param for USER/USER_INT in ext_localconf.php.
Everthing works fine, but now with TYPO3 6.2 its a massive problem for me.

Now in ext_localconf.php:

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'VENDOR.' . $_EXTKEY,
    'NAME',
    array(    // cacheable actions
        'Controller1' => '',
        'Controller2' => ''
    ),
    array(    // non-cacheable actions
        'Controller1' => 'function1, function2, function3',
        'Controller2' => 'function1, function2'
    )
);

if i wrote this:

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'VENDOR.' . $_EXTKEY,
    'NAME',
    array(    // cacheable actions
        'Controller1' => 'function1, function2, function3',
        'Controller2' => 'function1, function2'
    ),
    array(    // non-cacheable actions
        'Controller1' => 'function1, function2, function3',
        'Controller2' => 'function1, function2'
    )
);

I can not detect any change.

Please help me to find out my issue.

Thanks and best regards

Bastian

#1

Updated by Sebastian G over 7 years ago

  • % Done changed from 0 to 100

SORRY!!!

It's not a TYPO3 problem. Now I saw that the action name in switchableControllerActions in my flexform settings was not written in upper camel case.
I'am a little bit confused, because TYPO3 thrown no error. But everthing is ok now. I'm happy :-)

#2

Updated by Steffen Müller over 7 years ago

  • Status changed from New to Closed

Also available in: Atom PDF