Task #8630
Story #8796: As Roger I want a flexible and powerful TCA Concept in order to define my objects
Use the permission model inside JavaScript
| Status: | Closed | Start date: | 2010-07-03 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | UI | |||
| Target version: | - |
Description
We (Andi, Sebastian, Patrick, Karsten), discussed this at t3dd.
- enhance the policy system that you can add something like (... && UserInterface(F3.TYPO3.[someComponent]), and if this component is ACCESS_DENY, then this sould be transferred to a JSON array.
- TODO: Improve the way we can write that.
- in Application.bootstrap, we will only run bootstrappers in case they are not denied.
- We will add all DENIED resources to every Domain Object we transfer to the client side (be it via JSON, Page Template, ...)
- JavaScript will update its permissions (f.e. "currentPage.permissions"), and if the permissions change, this will trigger change events. Components can listen to this and react appropriately (i.e. disable/enable the button).
History
#1 Updated by Sebastian Kurfuerst almost 5 years ago
- Parent task set to #8796
#2 Updated by Sebastian Kurfuerst about 4 years ago
- Project changed from Base Distribution to TYPO3.Neos
#3 Updated by Sebastian Kurfuerst about 4 years ago
- Category set to UI
- Priority changed from Should have to Could have
#4 Updated by Sebastian Kurfuerst almost 4 years ago
- Status changed from New to Closed
Closing issue because it is either obsolete in the new FE architecture, or duplicate.