Indexing broken in 1.3.2
after upgrading to 1.3.2, upload in BE for editors respective indexing of new records by dring-by does not work any more.
- under 1.3.2, admins can upload failes and trigger successful indexing of unknown files
- files can be indexed as admin, so there is no general error in extracting file (meta) data
- editors can successful upload files
- indexing fails for editors with DAM 1.3.2
- indexing works for editors with DAM 1.3.1, having the same setting of access rights as above, just downgraded extension
Up to 1.3.1 editors logged in, changed to the directory where they wanted to upload files and did it. Upload and indexing afterwards worked, the files could now be used.
Two days ago I updated to 1.3.2 (not 1.3.2-dev). The same procedure, but:
- directly after upload the editor gets schreen "upload.jpg". Sorry for german screens, translated message (by google):
None of the high-load operations could be completed.
If this problem persists, please use another browser, contact your administrator or disable the "flash interface to upload" option in the user settings.
After closing the popup the user gets the error you can see in directory.jpg. changing to other directories work, but this directory not any more. Each time the user wants to list the directory where he just uploaded files to, he gets this error.
But whe nentering this directory as admin (until now this was only an editor), we see tht the uploaded file is there, and filesize is correct, but we see also that file has not been indexed. As dam does indexing of new files when browsing through the directories, when opening the directory it has been indexed.
And when we are editor again and open the directory, the error is gone and we may use the file as usual.
But the very interesting thing:
Editors were able to upload file before the update from 1.3.1 to 1.3.2. And after downgrade, this is now also the case. I didn't change any access rights, but now editors are able to upload files again.
I have exactly the same issue on three different TYPO3 installations:
a) TYPO3 4.5.30, PHP 5.3.3/mod_apache
b) TYPO3 4.7.15, PHP 5.3.3/mod_apache
c) TYPO3 4.7.15, PHP 5.4.19/fast_cgi
[BUGFIX] Indexing broken for editors with limited access rights
Since #43308, DAM respects the TCAdefaults for indexing of files.
Since the default UserTS config is not necessarily set, the array
containing this data is not initialized. To prevent
array_merge_recursive from throwing an exception, an empty array
must be initialized before the UserTS config is possibily set.
Reviewed-by: Lorenz Ulrich
Tested-by: Lorenz Ulrich