Bug #41571
UriBuilder doesn't properly handle arguments of SubRequests
| Status: | Closed | Start date: | 2012-10-03 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Marc Neuhaus | % Done: | 0% |
|
| Category: | - | |||
| Target version: | TYPO3 Flow Base Distribution - 2.0 beta 1 | |||
| PHP Version: | Complexity: | |||
| Has patch: | No | Affected Flow version: | Git 1.2 (master) |
Description
If you're creating a link inside a SubRequest that link currently doesn't add/remember the Arguments, Controller, etc from the parentRequest if it's nested more than one level.
For example: I'm creating a kind of Application Frame/Scaffold to integrate other Packages/Controller, for that i've created an ScaffRuntime to encapsulate the other controllers inside a SubRequest and add that generated content to my layout. Now, if i use a controller which uses the ExposeRuntime to expose some Models the links generated inside that SubRequest don't carry on the arguments set in the ScaffRuntime, which results in completly useless links and redirects.
Links in SubRequest should carry all arguments of parentRequests with it, because normally a link inside a SubRequest doesn't change anything about there parents, because they probably don't even know about them.
Associated revisions
[BUGFIX] UriBuilder doesn't properly handle arguments of SubRequests
If you're creating a link inside a SubRequest that link currently
doesn't add/remember the Arguments, Controller, etc from the
parentRequest if it's nested more than one level:
MainRequest->SubRequest->SubRequest
This change fixes the mergeArgumentsWithRequestArguments
to properly add all of parentRequests for links inside SubRequests.
Related: #41571
Releases: 1.2
Change-Id: Iae8a2a8a39d47d7e99743d78188dccdd4238ccfb
History
#1 Updated by Christoph Gross over 2 years ago
http://forge.typo3.org/issues/35790 Is it possible that these two bugs are connected?
#2 Updated by Marc Neuhaus over 2 years ago
- Status changed from New to Closed
Not sure if that one is related.
This ticket is saved/resolved by the way.
Had falsely an Related instead of Resolves in my commit