TYPO3 Core

Same problem here:
Website running fine with 6.2.10 on one server using fileadmin/_processed_ for thumbnails.
Copying this wwebsite and database to onother typo3 6.2.10 will try to use typo3temp/_processed_
This fails with all new img-tags linking to one single thumbnail in typo3temp/_processed_

It looks like no new thumbnails are created and one single still existing thumbnail
in typo3temp is used for all new images.

fileadmin/_processed_ is not checked in the install-tool.

Please post the identifiers of the original files for which processed files are generated in typo3temp/_processed_

There is no problem with the original picture-filenames:
They are placed inside a content element from /fileadmin/media
In the backend the thumbnails are shown from /fileadmin/_processed_ (!!) in both systems.
In both systems backend-thumbs are ok!!
Th folder fileadmin/_processed_ is writeable in both systems from the backend.

But when looking at the front-end the one system shows the
new created thumbnails like and its is ok:
fileadmin/_processed_/csm_Picturename_7ed5cfd48f.jpg

The other system, also a typo3 v6.2.11, wants to show a file named
typo3temp/_processed_/csm_RANDOM_OR_FIRST_FILENAME_abchashetc.jpg

This filename is not computed new when adding a new image to this content element.
It takes some other picturename already existing in typo3temp.

The problem more closer is located in the extension
css_styled_content TYPO3 v4.5

Replacing this extension with the normal "css_styled_content"
removes the problem. Thumbs are calculated al right.

Including this static extension "css_styled_content TYPO3 v4.5" again
reproduces the problem.

So I will have a look on this sys-extension if there are any
differences in the two installations.

Setting
[FE] [activateContentAdapter] to ON
solved the problem!

Can this ticket be closed?