Task #51762
closed
Epic #55070: Workpackages
Epic #54260: WP: FAL Missing Issues / Features / API
Story #54267: As an Editor I want to use a FAL withouth bugs
Exception instead of nice warning when opening filelist as restricted be-user after updating 6.1.3 -> 6.1.4
Added by Simon Schick over 10 years ago.
Updated over 6 years ago.
Category:
File Abstraction Layer (FAL)
Description
After updating from 6.1.3 to 6.1.4, I get an exception like in the attached screenshot, when opening the filelist as restricted backend-user.
Before, I just got a nice, blue, warning - see attached screenshot.
Files
- Category set to File Abstraction Layer (FAL)
- Status changed from New to Accepted
- Target version changed from 2463 to 6.2.0
Just to have this note added: The mount-point shown here has the flag "is browsable" set to FALSE.
- Assignee set to Steffen Ritter
- Complexity set to no-brainer
- Is Regression set to No
- Parent task set to #54267
I'm experiencing the same problem right now in 6.2.0beta4. The restricted be-user wants to access the file mount (which is fileadmin/user_upload). When the user loads the file list module the above mentioned exception is displayed. I've also inserted the UserTS proposed here: http://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2013-003/. An admin user does not get the exception. The file mount is browseable.
Edit: For testing I've created a subfolder in fileadmin/user_upload/ and set this as root for the file mount. But it does not solve the problem. The exception is still thrown.
- Status changed from Accepted to Needs Feedback
please check if that still is happening in the current master as of today;
sadly that won't be backported as it introduced a new class.
Error display is now as attached screenshot. Only happens when the filesystems rights are changed when the user is browsing the folder in the list or the user modifies the GET parameter for the path.
If the folder is not accessible the link to the detailed view is not existing.
So, the new screen is fine for me, since a "normal" user won't see it.
- Status changed from Needs Feedback to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
I've checked out the current master as of today. With this version I don't get any exception. The behavior is as expected, i.e. the user can show the "root" of the file mount.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
