Bug #44902
ArrayImplementation uses unsetted(nulled) paths
| Status: | Resolved | Start date: | 2013-01-29 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Marc Neuhaus | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
The ArrayImplementation tries to render non existing paths when an path is unset with ">".
The Reason is, that the TypoScript Parser doesn't remove the path, instead it sets it to NULL.
As a quick fix i changed the ArrayImplementation to check if the path is null to skip it.
But in general this should be properly handled by the Parser.
Related issues
Associated revisions
[BUGFIX] Add a check for unsetted Paths in Arrays
When a path is unset it isn't really unset by the TypoScript
Parser, instead it's set to NULL. This can throw an error
of non existing paths that TypoScript tries to render.
As a temporary Fix this changeset adds a check if the
path is NULL to skip it.
Resolves: #44902
Change-Id: Ib00a17a54092cca7ff9786a42bbfe436e00bc6ab
History
#1 Updated by Gerrit Code Review over 2 years ago
Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/17785
#2 Updated by Sebastian Kurfuerst over 2 years ago
- Status changed from New to Resolved
- Assigned To set to Marc Neuhaus