Dan Osipov wrote: > Must have been a temporary, or cache issue, as its working now. good to know, thanks! best Ingo -- Ingo Renner TYPO3 Core Developer, Release Manager TYPO3 4.2