add uploadfolder TSConfig override possibility
|Status:||Needs Feedback||Start date:||2007-05-13|
|Priority:||Should have||Due date:|
right now with TSConfig it is possible to override these config parameters of a group field:
group - size, autoSizeMax, max_size, show_thumbs, maxitems, minitems
it would be VERY USEFUL to add 'uploadfolder'.
to simply modify line 344 of class.t3lib_tceforms.php to
'group' => array('size', 'autoSizeMax', 'max_size', 'show_thumbs', 'maxitems', 'minitems','uploadfolder'),
isn't enough (TCE uses the overridden value to "read" files, but when it has to WRITE them, they go to nonoverridder TCA uploadfolder)
can anybody give a deeper eye in it?
(issue imported from #M5623)
Updated by Oliver Hader about 6 years ago
The override possibility is for the TCEFORM object of Page TSconfig.
Changing the uploadFolder would also mean to inform other affected parts (e.g. also FE) that something has changed - and these are not TCEFORM at all.
Updated by Stefano Cecere about 6 years ago
yes i understand..
so there is no way to easily modify the uploadfolder by TS or conditions...
i was exploring Dynamic Flexforms, but it seems to not be able to just MODIFY an existing field (it just adds/moves them)
(how do people organize files attached to thousands of records? all in just one folder?)
Updated by Stefano Cecere over 5 years ago
hasn't anybody need of this feature?
is everybody storing all records files in just one static upload folder?
i think that an even better solution would be NOT adding parameters in the TSConfig, but in the upload field definition TCA, like this:
'uploadfolder' => 'myfolder/###REC_FIELD_subfolder###';
where 'subfolder' is a string field of that record.
so i can figure some records to store its files in 'subdir1', and others in 'subdir2' ...
Updated by Martin Kutschker over 5 years ago
The problem is also that if you move a record from one part to hte other the value of the upload folder could also change. So not only the FE must be somehow be informed of that seeting, but also every move operation in the DB may result in move operations in the file system as well. And to make things worse: consider the record to be moved in a workspace!
While I sometimes wished to have such a feature myself, I think it's not possible.