Bug #35083
involving SecurityContext in Widget's __wakeup situation leads to an exception
| Status: | New | Start date: | 2012-03-21 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Object | |||
| Target version: | - | |||
| PHP Version: | Complexity: | |||
| Has patch: | No | FLOW3 version affected: | Git master | |
| Votes: | 0 |
Description
I experience the situation that the attached exception occurs.
I have an object with an injected \TYPO3\FLOW3\Security\Context. This object is created and stored inside the widgetConfiguration.
After a subsequent request of the page the attached exception occurs. It seems that the DI after the __wakeup is not fully correctly handled and the securityContext lost its request property.
Related issues
| related to TYPO3.Flow - Bug #37227: securityContext->getParty is not available in widget context | On Hold | 2012-05-16 |