Skip to content
Discussion options

You must be logged in to vote

This is most likely due to the autoDiscover feature of Dropzone.

When Dropzone starts, it scans the whole document, and looks for elements with the dropzone class. It then creates an instance of Dropzone for every element found. If you, later on, create a Dropzone instance yourself, you'll create a second Dropzone which causes this error.

So you can either:

  1. Turn off autoDiscover globally like this: Dropzone.autoDiscover = false;, or
  2. Turn off autoDiscover of specific elements like this: Dropzone.options.myAwesomeDropzone = false;

You don't have to create an instance of Dropzone programmatically in most situations! It's recommended
to leave autoDiscover enabled, and configure your Dropzo…

Replies: 1 comment 3 replies

Comment options

enyo
Feb 8, 2021
Maintainer Author

You must be logged in to vote
3 replies
@ShinodasCodes
Comment options

@enyo
Comment options

enyo Sep 24, 2021
Maintainer Author

@enyo
Comment options

enyo Oct 25, 2021
Maintainer Author

Answer selected by enyo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
2 participants