Francois Suter wrote: > b) it had been solved somewhere in the development of 4.2, but I can't > say when it was resolved exactly. just set it to fixed in 4.2.0 in this case. Ingo -- Ingo Renner TYPO3 Core Developer, Release Manager TYPO3 4.2