Bug #102404
Updated by Peter Kraume 6 months ago
In frontend context the field scope in table sys_csp_resolution is filled with a concatenation of "frontend." and the site configuration identifier. When the site identifier identifiert is too long, new entries in sys_csp_resolution fail for frontend requests: <pre> Uncaught TYPO3 Exception: #1406: An exception occurred while executing a query: Data too long for column 'scope' at row 1 </pre> This can happen e.g. in a fresh TYPO3 installation where there was no manual site configuration. Then the site identifiert looks like this: @autogenerated-1-c4ca4238a0b923820dcc509a6f75849b@ autogenerated-1-c4ca4238a0b923820dcc509a6f75849b The scope would then be @frontend.autogenerated-1-c4ca4238a0b923820dcc509a6f75849b@ frontend.autogenerated-1-c4ca4238a0b923820dcc509a6f75849b which is tool long. To mitigate the problem we need to double the field size at least. This will solve the problem for the above mentioned case. But since the site identifier has a TCA configuration for max. 255 chars I'd go for varchar(264). Possible implication: the scope is used in the CSP backend module in a table view. A very long field value might break the design of the table.