Hi,
We use plupload to let users of our platform upload folders containing a lot of files.
Some users have a very long folder-tree to organize their files, and they just drag&drop the whole thing.
We have noticed that files stored very deeply are sometimes completely ignored by the process (they are not listed in the queue widget, and thus, not uploaded.) Strangely enough :
- if I drag&drop contents stored locally at [c:] (with my full foldertree), a file stored deeply is correctly taken into account,
- if I drag&drop the same contents stored locally at [c:\blablabla(...)\blablabla], here the same file is ignored.
It looks as if PLUpload has issues retrieving the value of "relativePath" when its absolute value is too long.
Are you aware of any such issue ?
In our case, not uploading the file because of a path issue is not a problem per se. But having no warning that some files were not taken into account is misleading, because users believe they have uploaded the whole thing while the result is incomplete.
Thanks for any help you can provide.
Best regards,
LP
Hi,
We use plupload to let users of our platform upload folders containing a lot of files.
Some users have a very long folder-tree to organize their files, and they just drag&drop the whole thing.
We have noticed that files stored very deeply are sometimes completely ignored by the process (they are not listed in the queue widget, and thus, not uploaded.) Strangely enough :
It looks as if PLUpload has issues retrieving the value of "relativePath" when its absolute value is too long.
Are you aware of any such issue ?
In our case, not uploading the file because of a path issue is not a problem per se. But having no warning that some files were not taken into account is misleading, because users believe they have uploaded the whole thing while the result is incomplete.
Thanks for any help you can provide.
Best regards,
LP