Bug #44902

ArrayImplementation uses unsetted(nulled) paths

Added by Marc Neuhaus almost 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2013-01-29
Due date:
% Done:

0%


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

Related to TYPO3.TypoScript - Bug #44903: Unsetting paths only sets the Path to NULL instead of unsetting New 2013-01-29

Associated revisions

Revision 978db1f2 (diff)
Added by Marc Neuhaus almost 7 years ago

[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 almost 7 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 almost 7 years ago

  • Status changed from New to Resolved
  • Assignee set to Marc Neuhaus

Also available in: Atom PDF