- Issue created by @mondrake
- First commit to issue fork.
- Status changed to Needs review
5 months ago 10:20pm 11 April 2024 - 🇬🇧United Kingdom longwave UK
The warning was previously wrapped in EntityStorageException, here we don't change that, we just throw a real exception in preSave() instead.
- Status changed to RTBC
5 months ago 1:10am 12 April 2024 - Status changed to Needs work
5 months ago 6:51am 12 April 2024 - 🇬🇧United Kingdom catch
Let's say we add a core update in three months which calls this code, and you have a site where the file has gone missing from an image field (very likely given our ten years of file_usage being broken and randomly deleting files, or if you install file delete module and mistakenly delete a file in use). With the current code, the update will complete, but tell you something is wrong, but with the MR, the update will fail and your database is now in an unrecoverable state - you can't roll back the update and you can't complete it, so you'd have to restore a backup, if you have one.
We either need to keep the warning here, maybe by using the logger, or refactor the test coverage.
- First commit to issue fork.
- Status changed to Needs review
5 months ago 1:17pm 15 April 2024 - Status changed to RTBC
5 months ago 2:52pm 15 April 2024 - Status changed to Fixed
5 months ago 9:32pm 15 April 2024 - 🇬🇧United Kingdom alexpott 🇪🇺🌍
Committed and pushed 0298c95971 to 11.x and fea64b66ce to 10.3.x. Thanks!
-
alexpott →
committed fea64b66 on 10.3.x
Issue #3440038 by longwave, quietone, mondrake, catch: ImageItem logs an...
-
alexpott →
committed fea64b66 on 10.3.x
-
alexpott →
committed 0298c959 on 11.x
Issue #3440038 by longwave, quietone, mondrake, catch: ImageItem logs an...
-
alexpott →
committed 0298c959 on 11.x
Automatically closed - issue fixed for 2 weeks with no activity.