Now when calling $TSFE->set_no_cache(), a reason can be provided and logged, making it easier to find why cache was disabled on a page. Ex: $TSFE->set_no_cache(‘Reached an unstable condition in extension xyz’); More info: Fix #11669: Provide a reason for why $TSFE->set_no_cache() has been triggered http://bugs.typo3.org/view.php?id=11669
Posts By: Dan Osipov
Windows 7 update: Black Screen of Death
Well, I asked Microsoft for more variety in Windows, and they listened! Proof? Windows 7 Black Screen of Death! That’s right, I was tired of the age old Blue Screen of Death, and asked Microsoft to spice it up – change the colors or whatnot. And Microsoft listened. Windows 7 = my idea.
doNotLoadInFE
New key in EM_CONF array, ‘doNotLoadInFE’ can be set to “1” for extensions that are only used in backend and have no front end components. This speeds up the frontend generation process, since extensions not doing anything in the FE will not be loaded on FE calls. More info: RFC #11474: Store separate extlist for… Read more »
Front Editing tt_news records
One of the major features in TYPO3 4.3 is the advanced frontend editing. Although its not part of the official distribution, it is available as an extension, and adds amazing functionality to your TYPO3 driven site. But did you know that you can edit any other record in the frontend using feeditadvanced functionality? Here is… Read more »
FE session data lifetime
New setting stored in $GLOBALS[‘TYPO3_CONF_VARS’][‘FE’][‘sessionDataLifetime’] defines the lifetime of frontend session data in seconds. The setting can be modified in the Install tool. More info: FYI24 Feature #11508: Integrate possibility to define lifetime of frontend session data http://bugs.typo3.org/view.php?id=11508 FYI24: Feature #11510: Store timestamp of last modification of session data to frontend user object http://bugs.typo3.org/view.php?id=11510