Bug #33282
closedPHP error when fileadmin/templates contains directory not readeable
0%
Description
If I have a directory in fileadmin/templates without execution (access)
permission, templavoila module return this error:
PHP Catchable Fatal Error: Argument 1 passed to
t3lib_div::getAllFilesAndFoldersInPath() must be an array, null given,
called in /usr/share/typo3/typo3_src-4.6.0/t3lib/class.t3lib_div.php on
line 3120 and defined in
/usr/share/typo3/typo3_src-4.6.0/t3lib/class.t3lib_div.php line 3110
It seems that the recursion in the related method in t3lib_div breaks with
the mentioned error if the access rights are not appropriate
Usually I load files in fileadmin with typo, so no problem. But if I create
directory directly on the server this error occours (eg. using git)
Files
Updated by Markus Klein almost 13 years ago
$fileArr can only be NULL if the array_merge() line is executed with a NULL parameter.
Hence, getFilesInDir() seems to return NULL in this case.
My first look into the code didn't reveal the place where this might happen.
Updated by Steffen Gebert almost 13 years ago
- Category set to Backend API
- Status changed from New to Needs Feedback
Ivan, could you please post a stack trace of that error? You get a stack trace, when you add your IP to devIPmask
in the Install Tool's All Configuration section.
Updated by Viktor Livakivskyi about 12 years ago
- File getfilesandfolders.PNG getfilesandfolders.PNG added
Hi, I'm experiencing same problem, but with extdeveval extension, which tries to find locallang.xml files and translate them to locallang.xlf.
It uses same getAllFilesAndFoldersInPath() method. But in our case we have .svn folders inside, which permissions are set to 700 root/root. And here t3lib_div::getAllFilesAndFoldersInPath() fails.
Stack trace attached
Updated by Alexander Opitz over 11 years ago
Hi,
this issue is very old, does it still exists with newer versions of TYPO3 CMS (4.7 or 6.1)?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
- Is Regression set to No
No feedback for over 90 days.
If you think, that this is the wrong decision, then please write to the mailing list typo3.teams.bugs with issue number and an explanation.