Dropzone Errors

Wappler Version : Both 5.8.2 and 6.0.0 Beta 3
Operating System : Windows 10
Server Model: NodeJS
Database Type: Both None and SQLite
Hosting Type: Localhost

Expected behavior

What do you think should happen?

When using the File Upload under a form, converting it to a dropzone the dropzone should upload the file or files via the Server Connect action. When converting it back to a non-dropzone file upload it works as expected.

Actual behavior

What actually happens?

When using the Dropzone I receive the error of “Uncaught TypeError: this.updateData is not a function” and the files are not uploaded. Tested the dropzone on an existing project, then a new project with only a file upload and on version 5.8.2. Always receive the same error. Tested both on Firefox, Chrome, and Edge. Tested multiple and single file upload. Only dropzone errors out.

How to reproduce

  • Detail a step by step guide to reproduce the issue
  • A screenshot or short video indicating the problem
  • A copy of your code would help. Include: JS, HTML.
  • Test your steps on a clean page to see if you still have an issue

I created a brand new project as NodeJS with no database to see if it was my existing project causing the error. Used the built in form options. Tried using as much defaults as I can in this example. See the screenshots below for all the settings. Removing the dropzone successfully allows for uploads.

image
image
image
image
image
image

This last screenshot is after submitting the images

Please let me know if it is something I am doing wrong or further adjustments or testing needed. Thanks

Are you on the stable or beta extensions channel?

Initially on Beta extensions and 6.0.0 B3 when I was running into this issues but I put a fresh install of 5.8.2 and on Stable with experimental features turned off to make sure it was not that. The screenshots are from my quick demo test using 5.8.2 stable

I checked again swapping Beta and Stable and restarted Wappler then was prompted finally to update after that restart. It works again on Stable so when on Beta Extensions is when the issue happens.

Edit: To add more info, I also tested it on 6.0.0 Beta 3 on Stable extensions and it does work there as well.