Bug #55714
Not available storages assigned to user shouldn't cause "hard failure"
| Status: | Resolved | Start date: | 2014-02-06 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Georg Ringer | % Done: | 100% |
|
| Category: | File Abstraction Layer (FAL) | Spent time: | - | |
| Target version: | 7.4 (Backend) | |||
| TYPO3 Version: | 6.2 | Is Regression: | No | |
| PHP Version: | Sprint Focus: | |||
| Complexity: |
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?
Related issues
Associated revisions
[BUGFIX] Invalid sys file storages must be ignored
If a storage is not available anymore, it must be ignored
Change-Id: Ie00af1bc086871c046ac4556c0119fc82d30a17e
Resolves: #55714
Releases: master, 6.2
Reviewed-on: http://review.typo3.org/41693
Reviewed-by: David Greiner <hallo@davidgreiner.de>
Reviewed-by: Jan Helke <typo3@helke.de>
Tested-by: Jan Helke <typo3@helke.de>
Reviewed-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
Tested-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
[BUGFIX] Invalid sys file storages must be ignored
If a storage is not available anymore, it must be ignored
Change-Id: Ie00af1bc086871c046ac4556c0119fc82d30a17e
Resolves: #55714
Releases: master, 6.2
Reviewed-on: http://review.typo3.org/41696
Reviewed-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
Tested-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
History
#1 Updated by Sebastian Fischer over 1 year 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.
#2 Updated by Gerrit Code Review 16 days 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
#3 Updated by Georg Ringer 16 days ago
- Assigned To set to Georg Ringer
- Target version set to 7.4 (Backend)
#4 Updated by Gerrit Code Review 16 days 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
#5 Updated by Georg Ringer 16 days ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset f4dc2c661dcb3fbe6206800dfa470534ce9175fd.