TYPO3 Core

But

tt_content.uploads.20.renderObj.10.stdWrap.if.isGreaterThan.field = layout

What makes you think that it is wrong? This value is there since the beginning of this TypoScript already...

Because this condition checks if an image should be shown (renderObj.10) depending on the layout field.
It makes no sense to show an thumbnail only if layout 2 or higher is selected.

• Only file name - 0
• File name and file extension icon - 1
• File name and thumbnail (if possible) - 2

The condition would fit perfectely to this field.

If you select uploads_type option 2 - no image is shown with the default css_styled_content settings.

If you change the value like described above, everything works fine.

Let's see if I can understand what happens:

1) CSS styled content has always used the "layout" field to set the appearance of the filelinks CE
2) since 7.6 in FLUID Styled content, a new field called "uploads_type" has been introduced and is used instead of the layout field

3) If you use ONLY CSS styled content and disable FLUID styled content from Ext manager, uploads_type will become absent.

this is why tt_content.uploads.20.renderObj.10.stdWrap.if.isGreaterThan.field = layout has been kept in CSC, I think.

Ok, never tried to disable fluid_styled_content.
But setting the appearance via layout isn't very fancy.

As Riccardo already explained this has been the case since the beginning of this TypoScript. css_styled_content is not be used in combination with fluid_styled_content to prevent such conflicts you run into now.
We can't change the working of this in css_styled_content anymore and that was the reason I rejected this issue.

@Philipp you can make things a bit "fancier" via TSConfig:

TCEFORM {
   tt_content {
    layout{
      types{
        uploads{
          altLabels.0 = whatever
          altLabels.1 = whatever another label
          altLabels.2 = whatever etc
          altLabels.3 = whatever etc etc

        }
      }
    }
  }
}