TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-05-22T07:31:50ZTYPO3 Forge
Redmine TYPO3 Core - Bug #59017 (Closed): Exception while trying to edit disabled file storagehttp://forge.typo3.org/issues/590172014-05-22T07:31:50ZRico Sonntagrico.sonntag@netresearch.de
<p>Clicking on a disabled file storage in list view to edit it, results in:</p>
<pre>
#1314085990: Desired storage is not in the list of available storages.
</pre> TYPO3 Core - Bug #58918 (Rejected): FileRepository: addToIndex is marked as deprecated but altern...http://forge.typo3.org/issues/589182014-05-19T13:03:57ZRico Sonntagrico.sonntag@netresearch.de
<pre>
public function addToIndex(File $fileObject) {
GeneralUtility::logDeprecatedFunction();
return $this->getIndexerService()->indexFile($fileObject, FALSE);
}
</pre>
<p>getIndexerService() is a protected method, so there is no way to fix the deprecated warning!</p> TYPO3 Core - Bug #58872 (Closed): ResourceStorage::addFile throws exception due invalid file perm...http://forge.typo3.org/issues/588722014-05-16T14:37:51ZRico Sonntagrico.sonntag@netresearch.de
<p>/typo3/sysext/core/Classes/Resource/ResourceStorage.php => addFile</p>
<p>A call to addFile</p>
<pre>
$file = $resourceStorage->addFile(
$pathToFile,
$resourceStorage->getRootLevelFolder()
);
</pre>
<p>throws the exception "File name is invalid." (Code: 1320288991). Parameter $targetFileName is allowed to be empty but $this->assureFileAddPermissions does not take it into account. Instead the targetFileName is evaluated two lines later:</p>
<pre>
$targetFileName = $this->driver->sanitizeFileName($targetFileName ?: PathUtility::basename($localFilePath));
</pre>
<p>Do you really test your stuff before you release it (Commit 054207881d3be1d76b8205231c8847947d5c2e4c for instance)? Its a pain to work with TYPO3 6.2 and FAL. Really annoying.</p> TYPO3 Core - Bug #56641 (Closed): FAL: FileListController.phphttp://forge.typo3.org/issues/566412014-03-07T10:37:56ZRico Sonntagrico.sonntag@netresearch.de
<p>Accessing the file list with an user whom is not allowed to read (user access rights) from a directory results in an uncaught exception.</p>
<p>1. Create a new backend user <br />2. Disable "Directory: Read" from file operation permissions <br />3. Switch to new user<br />4. Try to access filelist module</p> TYPO3 Core - Bug #56530 (Closed): FAL: Permissions and Exceptionshttp://forge.typo3.org/issues/565302014-03-04T13:52:09ZRico Sonntagrico.sonntag@netresearch.de
<p>The permission checks to folders/files are partly wrong. Folders are checked against file permissions. Some methods (copyFolder, moveFile) catch all exceptions and print an error message instead. Messages of caught exception are thrown away, instead of printing them to the user a new message is generated with partly different content.</p> TYPO3 Core - Bug #56527 (Closed): ResourceStorage: userPermissions => recursiveDeleteFolderhttp://forge.typo3.org/issues/565272014-03-04T12:45:42ZRico Sonntagrico.sonntag@netresearch.de
<p>Change the user permissions to allow recursive folder deleting results always to false. The userPermission array inside ResourceStorage contains an entry "folder_recursivedelete" but the storage tries to match against "recursivedeleteFolder".</p> TYPO3 Core - Bug #56511 (Closed): /typo3/sysext/core/Classes/Utility/File/ExtendedFileUtility.php...http://forge.typo3.org/issues/565112014-03-04T08:22:19ZRico Sonntagrico.sonntag@netresearch.de
<p>Method func_delete catches an InsufficientFileAccessPermissionsException instead of an expected InsufficientFolderAccessPermissionsException.</p> TYPO3 Core - Bug #56494 (Closed): FAL readonly: Directory copying results in BE exceptionhttp://forge.typo3.org/issues/564942014-03-03T14:51:24ZRico Sonntagrico.sonntag@netresearch.de
<p>Trying to copy a readonly directory to another directory results in an backend exception displayed. This is caused because <code>ExtendedFileUtility.php</code> just catches <code>InsufficientFolderAccessPermissionsException</code> but <code>InsufficientFolderReadPermissionsException</code> and <code>InsufficientFolderWritePermissionsException</code> are not derived from it.</p> TYPO3 Core - Bug #56443 (Closed): FAL driver configuration: Setting capabilities to readonly show...http://forge.typo3.org/issues/564432014-02-28T14:56:31ZRico Sonntagrico.sonntag@netresearch.de
<p>Setting a driver to readonly (is writable capability not checked) results in always showing the DragUploader after clicking somewhere in the filelist</p> TYPO3 Core - Bug #56427 (Rejected): FAL driver configuration: No configured flexform results in e...http://forge.typo3.org/issues/564272014-02-28T13:03:25ZRico Sonntagrico.sonntag@netresearch.de
<p>The FAL driver configuration allows an optional flexform to be specified.</p>
<p><code>/typo3/sysext/core/Classes/Resource/Driver/DriverRegistry.php</code><br /><pre>
public function registerDriverClass($className, $shortName = NULL, $label = NULL, $flexFormDataStructurePathAndFilename = NULL) {
...
}
</pre></p>
<p>The configuration screen displays the error <code>Data Structure ERROR: Line 1: Invalid document end</code> if no flexform is given, if the driver need none.</p>
<p><code>ext_localconf.php</code></p>
<pre>
/* @var \TYPO3\CMS\Core\Resource\Driver\DriverRegistry $registry */
$registry = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance(
'TYPO3\CMS\Core\Resource\Driver\DriverRegistry'
);
$registry->registerDriverClass(
'DriverClass',
'Shortname',
'Label'
);
</pre>