"Index Name" fields in Structures' flexforms must not have uniqueInPid

[Siegfried Schweizer]

Consider having METS files containing structure names differring from the DFG viewer set, and other METS files having compatible ones to that. You'd then have to add multiple structures to your setup like that:

-------------------

Display Label
Volume

Index Name
volume

-------------------
and
-------------------

Display Label
Volume

Index Name
Volume

-------------------

But when saving the second one, Typo3 adds a number starting by zero to the string, e.g. Volume0. This is due to the flexform field having the uniqueInPid attribute (which indeed seems to be case-unsensitive). This should be removed in order to be able to have different Index Names to equal Display Labels.

[Siegfried Schweizer (siegfried-schweizer)]

After adding all these Structures and subsequent reindexing, all thumbnails that were present before are gone now.

[Sebastian Meyer (sebastian-meyer)]

This seems to be a collation problem within the database. Only binary fields are handled case-sensitive by MySQL when selecting records.

Could you please check the collation of your database, the table "tx_dlf_structures" and the field "tx_dlf_structures.index_name"?

Does this bug occur even if you use binary collations like "utf8_bin"?

[Sebastian Meyer (sebastian-meyer)]

To make this clear: since most MySQL collations (including TYPO3's default collation "utf8_general_ci") are case-insensitive, I assume this isn't simply done by removing "uniqueInPid" from flexform configuration as this will likely lead to unpredictable results when selecting those records from database.

Could you please do some testing on this issue? Just remove "uniqueInPid" as eval-function from the field configuration in tca.php and you are ready to go!