Project

General

Profile

Actions

Bug #33444

closed

Fatal error in configuration ($BE_USER->uc)

Added by Philipp Gampe about 12 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2012-01-25
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

This happens when expanding the [BackendComponents] and then expanding the [States].

This sets $theValue in t3lib_arrayBrowser::wrapValue() and t3lib_arrayBrowser::wrapArrayKey() to be an objects.

This results in warnings that strlen() needs have a string and that addslashes() needs to have a string as argument.

The fatal error result in t3lib_utility_Math::canBeInterpretedAsInteger() is called with this object.

Fix is simply: Add checks for objects before doing the processing.

I can reproduce this bug on 4.6 and 4.7, but not with 4.5.
It has something to do with how the tree states are stored, becaue if I switch the sources, but not reload the backend (from 4.5 to master/4.6) I can even clear temp configuration in user settings, but this error does not show up. Only after backend reload the wrong values are saved in the UC array.

Anyway this is only a related issue.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #33446: canBeInterpretedAsInteger fatals if given an objectClosedPhilipp Gampe2012-01-25

Actions
Actions

Also available in: Atom PDF