Actions
Bug #55714
closed
Not available storages assigned to user shouldn't cause "hard failure"
Status:
Closed
Priority:
Should have
Assignee:
Category:
File Abstraction Layer (FAL)
Target version:
Start date:
2014-02-06
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
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 
Updated by 
Updated by 
Updated by
Actions