TYPO3 Core

bug_11663_part1.diff contains no changes at all, just comments and code cleanup.

bug_11663_part2.diff makes sure that an error is displayed if there is a cHash error and disableNoCacheParameter is enabled. This is required since pages that are cached depend on a correct cHash.

bug_11663_part3.diff skips a condition which seems useless anyway now that we use locking. Otherwise, again conflicts may occur if disableNoCacheParameter is enabled.

bug_11663_part4.diff finally contains a condition that sticks to enabling $TSFE->no_cache if one of the following conditions are met:
- either one of $TSFE->forceTemplateParsing || $TSFE-displayEditIcons || $TSFE->displayFieldEditIcons is enabled (Frontend editing)
- $TSFE-fePreview is enabled (Frontend preview)
- tslib_feTCE is loaded (again, related to frontend editing)
- tslib_AdminPanel is loaded (includes date simulation, group preview, frontend editing, etc.)

If there is anything missing in this list, please let me know.

Those 4 patches have not been tested by myself yet, but they should fix the issue completely.
A backport for TYPO3_4-2 will follow next...

For TYPO3 4.2, patches have been slightly modified:
- part1: Don't make code cleanups, just add the comments
- part2: Trunk version can (must!) be used
- part3: Instead of removing the whole condition, just skip it if disableNoCacheParameter is enabled. Eventually this may be a good solution for Trunk as well(?)
- part4: Instead of checking for tslib_AdminPanel, check for t3lib_tsfeBeUserAuth

+1
patches for 4.2 tested: the applied fine and solved the problem;
regards georg