3 ms·
Very odd. If you drag the zip onto your laptop and the drop event listener doesn't pick up on it, your browser would likely just "download" the zip you dropped.
by andrewxhill 9y ago
Very odd. If you drag the zip onto your laptop and the drop event listener doesn't pick up on it, your browser would likely just "download" the zip you dropped. Which explains what you see I'm guessing. What I'm not sure about is why the JS doesn't pick up on the drop event and process the file. Do you have any settings that would block JS? What browser are you using?
- forcer 9y agoI tried in latest versions of FF and CH and it does not work (on Windows10). When I drag the ZIP archive to the area it does not do anything. Do all people just try on MAC or why it does not work for me?
- carsonfarmer 9y agoHi forcer, when you drag it over the 'drop zone' does the little zip image/icon disappear?
- carsonfarmer 9y agoOk, this looks like this issue: https://github.com/textileio/textile-facebook/issues/4 https://github.com/textileio/textile-facebook/issues/4 We'll try to update this soon!
- carsonfarmer 9y agoFixed on github, should be live soon(ish)
- carsonfarmer 9y agoShould have a fix in the latest code on github, should be live soon(ish)
- gk1 9y agoStill not working for me. The drag+drop area shows a "Click to Download" button so it's registering the dropped folder, but when I download it there's nothing different about the folder.
- s0l1dsnak3123 9y agoMy export from Facebook is 5.5GB - for large zipfiles like mine, the UI doesn't do anything when you drop the file onto the event listener.
- carsonfarmer 9y agoYes this is a known 'issue': https://github.com/textileio/textile-facebook/issues/2 https://github.com/textileio/textile-facebook/issues/2. Unfortunately, some browsers don't like large files being dragged-and-dropped like this. The 'solution' for now seems to be to unzip on your computer, remove the messages folder, re-zip, and try again. This should reduce your zip file significantly. Let me know if that helps at all. We're working on a more permanent fix for this in the mean time.