You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I though that uploadAllCompleted event tells me, that all uploads are completed -> wrong 🤔
Since this event gets triggered on Dropzone.success, its fired after each uploaded file. The correct event would be Dropzone.queuecomplete. But with this event you do not have the data of the uploaded files. This needs investigation who uses uploadAllComplete and how ... currently greping mockup shows, that its not used at all, since tinyce now has the contentbrowser.
Mainly this is "just" a documentation issue, because all pat-uploadoptions get injected into Dropzone so you can simply use data-pat-upload="queuecomplete: my_complete_function" and register it as window.my_complete_function somehwere in your code.
The text was updated successfully, but these errors were encountered:
I though that
uploadAllCompleted
event tells me, that all uploads are completed -> wrong 🤔Since this event gets triggered on
Dropzone.success
, its fired after each uploaded file. The correct event would beDropzone.queuecomplete
. But with this event you do not have the data of the uploaded files. This needs investigation who usesuploadAllComplete
and how ... currently greping mockup shows, that its not used at all, since tinyce now has the contentbrowser.Mainly this is "just" a documentation issue, because all
pat-upload
options get injected intoDropzone
so you can simply usedata-pat-upload="queuecomplete: my_complete_function"
and register it aswindow.my_complete_function
somehwere in your code.The text was updated successfully, but these errors were encountered: