Symfony UX Dropzone
Edit this pageSymfony UX Dropzone
Symfony UX Dropzone is a Symfony bundle providing light dropzones for file inputs in Symfony Forms. It is part of the Symfony UX initiative.
It allows visitors to drag and drop files into a container instead of having to browse their computer for a file.
Installation
Before you start, make sure you have Symfony UX configured in your app.
Then, install this bundle using Composer and Symfony Flex:
1 2 3 4 5
$ composer require symfony/ux-dropzone
# Don't forget to install the JavaScript dependencies as well and compile
$ yarn install --force
$ yarn encore devAlso make sure you have at least version 3.0 of
@symfony/stimulus-bridge in your package.json file.
Usage
The most common usage of Symfony UX Dropzone is to use it as a drop-in replacement of the native FileType class:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
// ...
use Symfony\UX\Dropzone\Form\DropzoneType;
class CommentFormType extends AbstractType
{
public function buildForm(FormBuilderInterface $builder, array $options)
{
$builder
// ...
->add('photo', DropzoneType::class)
// ...
;
}
// ...
}Customizing the design
Symfony UX Dropzone provides a default stylesheet in order to ease usage. You can disable it to add your own design if you wish.
In assets/controllers.json, disable the default stylesheet by
switching the @symfony/ux-dropzone/src/style.css autoimport to
false:
1 2 3 4 5 6 7 8 9 10 11 12 13 14
{
"controllers": {
"@symfony/ux-dropzone": {
"dropzone": {
"enabled": true,
"fetch": "eager",
"autoimport": {
"@symfony/ux-dropzone/src/style.css": false
}
}
}
},
"entrypoints": []
}Note
Note: you should put the value to false and not remove the line
so that Symfony Flex won’t try to add the line again in the future.
Once done, the default stylesheet won’t be used anymore and you can implement your own CSS on top of the Dropzone.
Extend the default behavior
Symfony UX Dropzone allows you to extend its default behavior using a custom Stimulus controller:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
// mydropzone_controller.js
import { Controller } from '@hotwired/stimulus';
export default class extends Controller {
connect() {
this.element.addEventListener('dropzone:connect', this._onConnect);
this.element.addEventListener('dropzone:change', this._onChange);
this.element.addEventListener('dropzone:clear', this._onClear);
}
disconnect() {
// You should always remove listeners when the controller is disconnected to avoid side-effects
this.element.removeEventListener('dropzone:connect', this._onConnect);
this.element.removeEventListener('dropzone:change', this._onChange);
this.element.removeEventListener('dropzone:clear', this._onClear);
}
_onConnect(event) {
// The dropzone was just created
}
_onChange(event) {
// The dropzone just changed
}
_onClear(event) {
// The dropzone has just been cleared
}
}Then in your form, add your controller as an HTML attribute:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
// ...
use Symfony\UX\Dropzone\Form\DropzoneType;
class CommentFormType extends AbstractType
{
public function buildForm(FormBuilderInterface $builder, array $options)
{
$builder
// ...
->add('photo', DropzoneType::class, [
'attr' => ['data-controller' => 'mydropzone'],
])
// ...
;
}
// ...
}Backward Compatibility promise
This bundle aims at following the same Backward Compatibility promise as the Symfony framework: https://symfony.com/doc/current/contributing/code/bc.html
However it is currently considered experimental, meaning it is not bound to Symfony’s BC policy for the moment.
