[BUGFIX] New content elements are always stored on pid 0 19/30419/2
authorMarkus Klein <klein.t3@mfc-linz.at>
Mon, 26 May 2014 16:00:45 +0000 (18:00 +0200)
committerMarkus Klein <klein.t3@mfc-linz.at>
Thu, 5 Jun 2014 06:41:55 +0000 (08:41 +0200)
commit05bbf37596ce8b0747375ccd1106ec867e37874e
treea1e4610bf8964b97caca826bfb61b9fa148cfc9e
parent4fbb25042c47e0dc4e30e2d637e2b55906844a11
[BUGFIX] New content elements are always stored on pid 0

Due to patch https://review.typo3.org/#/c/30305/ the string comparison
on colPos fails and new content elements are always stored on pid 0.
This patch corrects the check for an integer colPos type by setting the
unused variable to NULL.

Resolves: #59059
Releases: 6.2, 6.1, 6.0, 4.7, 4.5
Change-Id: Iecd7f0cacf5c9315d882eebeb3893bcfa63ae7eb
Reviewed-on: https://review.typo3.org/30419
Tested-by: SITS Developer
Reviewed-by: Markus Klein
Tested-by: Markus Klein
typo3/sysext/cms/layout/db_new_content_el.php