-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting but not uploading #107
Comments
I don't immediately see what's going wrong. If |
I had the same problem,
to:
|
Sorry for the late answer. I'll publish my module on GitHub as soon as I can : it's implementing a very easy way to use socket.io and socketio-file-upload in Vue. Thank you for the great work! |
@oz- Would be really nice if you could share how you sloved the Problem as fast as you can. I have the exact same Error atm. |
I'm using SocketIOFileUpload in a modular Express+Nuxt.js application.
On the client side I'm relying on the VueSocket.io library to connect through socket.io, so I ended up making a VueSocketIOFileUpload plugin to make it available in all my components.
The instance of SockettIOFileUpload is created by passing the
this.$socket
instance returned by VueSocket.ioVue.prototype.$uploader = new SocketIOFileUpload(Vue.prototype.$socket)
Then I can access to the instance in my app through
this.$uploader
Client-side
Server-side
The 'start' event is called both client-side and server-side but then... nothing happens and if my files are visible in the upload folder, they have a zero size
FYI I'm uploading on a hard drive mounted on Ubuntu 18.04 if it does matter
I tried to create my folders with full permissions and without hiding them by the '.' but nothing worked
Both my server and the websockets are secured
Any idea on what is happening?
Thank you!
EDIT:
Also tested by importing directly the client libray in one of my module.
And on the main HD of my server...
Same behavior...
What am I doing wrong?
After some time debugging, it appears that the
loadCb
(on the FileReader) is never called.I might precise that Express is not used at all for the routing...
The text was updated successfully, but these errors were encountered: