1) Auto uploading of files do not work when the file field is part of a repeater area, you need to specify each possible field name
For example, in the Custom Files config you would need to enter
2) Cannot use square brackets in the names of the fields, such as "document[0]"
3) Cannot use curly brackets and therefore cannot use shortcodes in the names of the fields in the custom files list, for example if you were to try and get around issue 1 by putting the upload file action within an Event Loop, and call the field using 'document[{var:loop_event.key}]. Your debug will look a little like the following:
For example, in the Custom Files config you would need to enter
documents1:pdfso on and so forth.
documents2:pdf
documents3:pdf
...
2) Cannot use square brackets in the names of the fields, such as "document[0]"
3) Cannot use curly brackets and therefore cannot use shortcodes in the names of the fields in the custom files list, for example if you were to try and get around issue 1 by putting the upload file action within an Event Loop, and call the field using 'document[{var:loop_event.key}]. Your debug will look a little like the following:
Array
(
[upload24] => Array
(
[path] => /..../components/com_chronoforms6/chronoforms/uploads/
[document[{var] => Array
(
[extensions] => Array
(
[0] => loop_event25.key}]:txt
)
[info] => File is not present.
)as you can see, it's a little broken.
hello,
Use the mediafinder widget within a repeater because it stores a location of the file and not a database relation. The fileupload widget uses the system_files table and connects via a polymorphic relation to the main record. That type of relationship can't be setup through a repeater's contents, so you'll have to use the mediafinder widget to store the location of the file in the repeater widget's data column.
try this and ping if it helps
regards
diraj
Use the mediafinder widget within a repeater because it stores a location of the file and not a database relation. The fileupload widget uses the system_files table and connects via a polymorphic relation to the main record. That type of relationship can't be setup through a repeater's contents, so you'll have to use the mediafinder widget to store the location of the file in the repeater widget's data column.
try this and ping if it helps
regards
diraj
Another bug - it says there's been a reply to this post, but I can't see it.
This topic is locked and no more replies can be posted.
