Bug #76934
closedPHP 7.1: AbstractMenuContentObject declares uidRegister as string while it's used as array
100%
Description
PHP 7.1 throws an exception on menu generation as $rL_uidRegister is declared to be string but used as array.
Updated by Gerrit Code Review almost 8 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48799
Updated by Christian Kuhn almost 8 years ago
- Subject changed from AbstractMenuContentObject declares uidRegister as string while it's used as array to PHP 7.1: AbstractMenuContentObject declares uidRegister as string while it's used as array
Updated by Gerrit Code Review almost 8 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48799
Updated by Gerrit Code Review almost 8 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48799
Updated by Susanne Moog almost 8 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 377e12c154fb72467d13351fef7beb04f2210ef1.
Updated by Kasper Ligaard over 7 years ago
Exact same problem in TYPO3 7.6: Type of variable $rL_uidRegister is defined as string, but is always used as array. So when upgrading to PHP 7.1, the error becomes apparent. Applying the patch-set to TYPO3 7.6 HEAD seems to fix the error.
Updated by Gerrit Code Review over 7 years ago
- Status changed from Resolved to Under Review
Patch set 1 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/50974
Updated by Gerrit Code Review over 7 years ago
Patch set 2 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/50974
Updated by Tymoteusz Motylewski about 7 years ago
- Status changed from Under Review to Resolved
I'm closing the issue as all related issue has been resolved and all patches were merged.