04:59:30 <mddz> There is the flux:field.file viewhelper which can have a upload folder specified, but I can't get multiple file selection to work, despite it having attributes suggesting it should be possible.
04:59:50 <cweiske> I cannot explain why I think something. I just do.
05:06:16 <mddz> I don't want to know why you are thinking it, but why it is not possible ;)
05:07:09 <mddz> I can't quite understand the reasoning for all these different File-related viewhelpers with vastly different capabilites, but I guess it is caused by TYPO3
05:08:56 <cweiske> it is currently not possible because the view helper does not have an uploadfolder attribute, see https://fluidtypo3.org/viewhelpers/flux/master/Field/InlineViewHelper.html
05:11:47 <mddz> yeah, I saw thad (and got a PHP error when trying if it was possible anyways)
05:12:36 <mddz> so is there any 'best practive' for multiple file upload with defined upload folder?
05:13:05 <mddz> I don't want to get the userupload folder get messed up by dozens of content elements which use images
05:13:47 <cweiske> you could disable the upload button at the inline fal element
05:13:53 <cweiske> so users are forced to upload through the file list
05:16:29 <mddz> I am not quite sure which file list you mean?
05:16:58 <cweiske> on the left side of your typo3 backend
05:17:38 <mddz> ah I see, but I wanted to use a upload folder which is outside of the users reach
05:18:58 <mddz> but it works with flux:field.file and uploads/tx_myext/...
05:19:32 <cweiske> ah ok, so you don't mean fileadmin/
05:43:43 <mikeMM> hey.. i use v:content.render with vhs 2.4.. when a page is not translated my content-elements are not rendered... i found this link... but it does not help me further.. is there allready a fix for this issue?
05:44:36 <mikeMM> oh.. can not paste link... Issue: FluidTYPO3/vhs/issues/761
05:45:01 <cweiske> no, the issue represents the current state of affairs
05:46:11 <mikeMM> ok.. the github issue says the problem is only there when the page is translated but not the content elements... in my case it's not working when there is no translation for the page at all
05:46:40 <cweiske> then please add your observation as comment to the issue
05:46:49 <cweiske> should be the same underlying problem
06:37:46 <fka> i have a custom ce with the following field in the configuration: <flux:field.relation name="settings.dummy" size="5" minItems="1" maxItems="99" table="mymodel" />. Now, in the main part, i want to display the selected records. transform="array" works as expected, but i still only got the uids. transform="ObjectStorage" and "mymodel" seem to do not
06:37:46 <fka> hing in my case, i still get a string with comma-separated uids. any hint what i am doing wrong? :) thx
06:48:38 <cweiske> there is a difference between storing the selected records in the database, which is done as CSV
06:48:48 <cweiske> and the other side is actually reading those values
06:49:53 <cweiske> in your main section, you need to "expand" the csv values to a list of objects
06:53:29 <fka> thx for your answer. which viewhelper can do this for me? or must i use a userfunc/own vh for this?
06:53:50 <cweiske> I thought that one could use one of the view helpers in https://fluidtypo3.org/viewhelpers/vhs/master/Resource/RecordViewHelper.html
06:54:03 <cweiske> but there does not seem to be one that supports CSV values
07:06:44 <fka> no, i mean not in combination with csv values. when i set transform="array" i can iterate over the selected pids.
07:07:37 <fka> but as i want the whole model object and not only a field associated to resources i think it is the wrong vh for my usecase
07:30:59 <fka> ok i was using transform wrong, ObjectStorage needs the Modeltype as written in the docu and instead of mymodel i have to set the full namespace, ofc *facepalm*
07:31:18 <fka> it is still not working tho, but i think im heading in the right direction
08:01:12 <fka> the problem is, my classes don't get autoloaded (they are not listed by get_declared_classes())... i built my extension with the extension builder, so i thought all naming conventions should be fine...
08:18:07 <fka> ok after fixing my extension everything works like a charm. sorry for wasting your time... the problem was i used the tablename as value for the transform attribute, not the classname
08:18:15 <fka> this is the code: <flux:field.relation transform="ObjectStorage<Vendor\Extkey\Domain\Model\MyModel>" name="settings.dummy" size="5" minItems="1" maxItems="5" table="mymodel_table" />
12:38:04 <fka> i've got a problem with custom content controller... the Actio-method for my contentelement is not called... however, the initialization methods (initializeProvider, initializeSettings...) are correctly called...
12:38:15 <fka> any ideas what the problem might be?
12:55:53 <fka> ok i changed the namespace of my ContentController from 'FluidTYPO3\Fluidcontent\Controller' to the namespace used in my extension. now the action methods are called, but the initialization methods no longer work :(