Closed sypets closed 4 months ago
Indeed, but having the title
"Die Gesundheit der B\u00fcrgerinnen und B\u00fcrger wird nach dem Programm der Weltgesundheitsorganisation (World Health Organization-WHO) \u201eGesundheit f\u00fcr alle bis zum Jahre 2000\" aus dem Jahre 1977 als ein Zustand des v\u00f6lligen k\u00f6rperlichen, geistigen und sozialen"
I've the feeling your editors have a strange notion of what means a title and what should rather go to the description :-)
I've the feeling your editors have a strange notion of what means a title and what should rather go to the description :-)
True! 😄
Yes, true, this should not be, really.
The problem is, the metadata extraction task aborts now because of a very few (probably old files). Only solution I see is manually sifting through the logs and handling the files individually, e.g. changing the title. (this can be done for example with exiftool).
I understand it probably should not be responsibility of this extension to make sure metadata fits in the DB. However, TYPO3 also does not make sure, so this leads to aborted scheduler task.
closing. Feel free to reopen if this should be handled.
It’s ok to keep it open, as this is a possible problem and ideally it should get solved. But just hardcoding a substr($title, 0, 255) or alike is not really good as, even if questionable, we cannot rule out someone enlarges this field with a custom extension. So the perfect solution would be to check actual size for each field.
Rereading this, I have the feeling TYPO3 Core is (a bit) faulty here. Of course this is not expected to happen if you edit the metadata with the Backend edit form, but if an extension (like EXT:extractor) provides some metadata to the Core using the official API, it shouldn't be its responsibility to understand the underlying DB schema and "cut" a value based on the schema, instead, this is logically the responsibility of the Core (TYPO3\CMS\Core\Resource\Index\MetaDataRepository
) to know its own schema and cut content accordingly, or at least handle the "data too long" warning (logically this shortens automatically and isn't an "exception" per se).
Do you agree?
That makes sense what you wrote.
It would be nice if this did not result in an exception - but I understand that this is something which should rather be handled in TYPO3 where the DB schema is known.
From my end, all files which caused problems have been fixed manually and everything was extracted. If there is a rare case of a file causing problems in the future, I think we can live with that.
Thanks for your great work!
The database field in sys_file_metadata.title is tinytext which should be 255 bytes (not chars).
| title | tinytext | YES | | NULL | |
Ideally it should be checked if title fits before updating.
Log message
Stack trace:
version