Bug #55714
closed
Not available storages assigned to user shouldn't cause "hard failure"
100%
Description
It's been mentioned on the German TYPO3-list yesterday/today that a user receives
Oops, an error occurred!
Could not find row with uid "2" in table sys_file_storage More information regarding this error might be available online.
when logging in. It was assumed that there was a storage with uid 2 assigned to the user and afterwards deleted.
I see two problems here:
1) Once the storage is deleted you might not be able to remove the reference in the user-settings anymore. Or would it go away if you open and just save the user again?
2) Can we / do we want to avoid the "hard" failure for the user right after login? Maybe just show a notice or so?
Updated by Sebastian Fischer over 10 years ago
to 1. from my understanding. If you edit a user record the available storage get added to the field. This differes from what is stored in the database. On saving the unavailable record gets removed from the selection in the user record.
Updated by Gerrit Code Review over 9 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41693
Updated by Georg Ringer over 9 years ago
- Assignee set to Georg Ringer
- Target version set to 7.4 (Backend)
Updated by Gerrit Code Review over 9 years ago
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41696
Updated by Georg Ringer over 9 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset f4dc2c661dcb3fbe6206800dfa470534ce9175fd.
Updated by Riccardo De Contardi about 7 years ago
- Status changed from Resolved to Closed