Actions
Bug #66423
closedFAL Indexer createIndexEntry careless about non-string compatible values in exception message
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
-
Start date:
2015-04-14
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
As topic says: when Indexer::createIndexEntry is called with something that is not string-compatible (which is the case for File instances, for example) then the possibly-object variable $identifier is inserted as part of the exception message without first checking if it can be converted to a string. Subsequently, the error message that gets dispatched is a php warning converted to exception - instead of the intended InvalidArgumentException.
Suggested fix: check type of variable; if object without __toString, use gettype($identifier) as part of exception message instead.
Actions