[BUGFIX] New content elements are always stored on pid 0 89/30389/3
authorNicole Cordes <typo3@cordes.co>
Sun, 25 May 2014 17:30:54 +0000 (19:30 +0200)
committerMarkus Klein <klein.t3@mfc-linz.at>
Mon, 26 May 2014 09:58:13 +0000 (11:58 +0200)
commitee8967465adbb735ce4bb7108a1e24a7c228dbf5
treecf5480becb919c3b07a43f8ad0c76c167dd092a5
parent9a47bd202aa6f1088db189c0703d712a4d9dd41f
[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/30389
Reviewed-by: Fabien Udriot
Tested-by: Fabien Udriot
Reviewed-by: Alexander Opitz
Tested-by: Alexander Opitz
Reviewed-by: Markus Klein
Tested-by: Markus Klein
typo3/sysext/backend/Classes/Controller/ContentElement/NewContentElementController.php