Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

2021, nearly 2022, and browsers *still don't support* uploading a few thousand pictures in a few hundred sub-folders! :(

more options

https://stackoverflow.com/questions/68736550/2021-nearly-2022-and-browsers-still-dont-support-uploading-a-few-thousand-p

2021, nearly 2022, and browsers *still don't support* uploading a few thousand pictures in a few hundred sub-folders! :(

i met a major disappointment this week, when i found out the one PHP + HTML5 solution for uploading more than a few thousand HD and 4K pictures to a Content Management System (plupload.com tied into my own https://github.com/nicerapp/nicerapp), just doesn't work yet. in 2021.

it is one thing that we, CMS builders i mean, needed to find a component like plupload.com which allows us to upload our pictures in 1MB chunks, then recombine them on the server, and make the thumbnail after that, but to not provide us with any means at all to get the relativePath of the files being uploaded, IS AN UTTER DISGRACE, if you ask me.

the CMS building community has been complaining about this to browser makers since at least 2014(!).

see https://www.plupload.com/punbb/viewtopic.php?id=4188 for details.

see https://github.com/nicerapp/nicerapp/blob/f6998dd03015fe8e0768b346ea7147dec314e6ab/nicerapp/userInterface/photoAlbum/4.0.0/jquery_ui_widget.3.1.3.php#L114 and https://github.com/nicerapp/nicerapp/blob/f6998dd03015fe8e0768b346ea7147dec314e6ab/nicerapp/userInterface/photoAlbum/4.0.0/jquery_ui_widget.3.1.3.php#L145 for a pinpointing of the problem..

and it's now 2/3 of the way through 2021 on the way to 2022(!!)... :(

we, the builders of apps and systems that run in the browser, need a solution for this big problem as soon as possible.

how hard can it be to properly support in document.getElementById('uploader').addEventListener('drop',function(event){...}) the functions event.dataTransfer.items[i].webkitGetAsEntry().createReader() and event.dataTransfer.items[i].webkitGetAsEntry().readEntries()?

IT IS PROBABLY EASY TO FIX, WHEN GIVEN PROPER ATTENTION AND PRIORITY!

2021/08/11 : So, i don't know if this is a plupload error or a Chrome error, the problem occurs on both Kubuntu->Chrome *and* Windows10->Chrome (for uploads of a few thousand pictures in a few hundred sub-folders), but it's up to the browser makers and the makers of plupload to fix it, as CMS builders simply do not have the means to produce a fix, let alone distribute that fix.

And one more thing : it is another disgrace that non-webkit browsers don't support the relativePath functionality at all.

THIS MUST BE FIXED, AND SOON TOO PLEASE!

i'll now post a link to this post on the various browser makers' support forums, and list those links in a comment to this post at stackoverflow.

https://stackoverflow.com/questions/68736550/2021-nearly-2022-and-browsers-still-dont-support-uploading-a-few-thousand-p 2021, nearly 2022, and browsers *still don't support* uploading a few thousand pictures in a few hundred sub-folders! :( i met a major disappointment this week, when i found out the one PHP + HTML5 solution for uploading more than a few thousand HD and 4K pictures to a Content Management System (plupload.com tied into my own https://github.com/nicerapp/nicerapp), just doesn't work yet. in 2021. it is one thing that we, CMS builders i mean, needed to find a component like plupload.com which allows us to upload our pictures in 1MB chunks, then recombine them on the server, and make the thumbnail after that, but to not provide us with any means at all to get the relativePath of the files being uploaded, IS AN UTTER DISGRACE, if you ask me. the CMS building community has been complaining about this to browser makers since at least 2014(!). see https://www.plupload.com/punbb/viewtopic.php?id=4188 for details. see https://github.com/nicerapp/nicerapp/blob/f6998dd03015fe8e0768b346ea7147dec314e6ab/nicerapp/userInterface/photoAlbum/4.0.0/jquery_ui_widget.3.1.3.php#L114 and https://github.com/nicerapp/nicerapp/blob/f6998dd03015fe8e0768b346ea7147dec314e6ab/nicerapp/userInterface/photoAlbum/4.0.0/jquery_ui_widget.3.1.3.php#L145 for a pinpointing of the problem.. and it's now 2/3 of the way through 2021 on the way to 2022(!!)... :( we, the builders of apps and systems that run in the browser, need a solution for this big problem as soon as possible. how hard can it be to properly support in document.getElementById('uploader').addEventListener('drop',function(event){...}) the functions event.dataTransfer.items[i].webkitGetAsEntry().createReader() and event.dataTransfer.items[i].webkitGetAsEntry().readEntries()? IT IS PROBABLY EASY TO FIX, WHEN GIVEN PROPER ATTENTION AND PRIORITY! 2021/08/11 : So, i don't know if this is a plupload error or a Chrome error, the problem occurs on both Kubuntu->Chrome *and* Windows10->Chrome (for uploads of a few thousand pictures in a few hundred sub-folders), but it's up to the browser makers and the makers of plupload to fix it, as CMS builders simply do not have the means to produce a fix, let alone distribute that fix. And one more thing : it is another disgrace that non-webkit browsers don't support the relativePath functionality at all. THIS MUST BE FIXED, AND SOON TOO PLEASE! i'll now post a link to this post on the various browser makers' support forums, and list those links in a comment to this post at stackoverflow.

Keazen oplossing

Alle antwurden (3)

more options

I don't think this is a support question since you already told us this is not a feature yet.

Firefox has a new "input" site for feature suggestions, and also there's still the Firefox Development forum. Have you filed a bug?

more options

thanks, jscher2000..

and i may have found a workable solution as well, simply by searching google for 'readentries bug'..

https://codepen.io/anon/pen/gBJrOP

more options

Keazen oplossing