Getting a warning

[bolin-chen]

I just follow the guide to test uploading simply. But I get the warning that "The provided value 'undefined' is not a valid enum value of interface XMLHttpRequestResponseType." in "http-call-client.js:101" Is that normal using CollectionFS?

[rhyslbw]

Would need a reproduction repo to look into this

[ptrmrrs]

I've started getting this warning too, even though the files appear to upload successfully. I'm using the S3 adapter to two stores with graphicsmagic for resizing. This is with Chrome version 43.0.2357.81 (64-bit)

I don't recall receiving this warning previously. I just ran the same test on Safari and didn't get a warning. Any chance this is a Chrome thing?

Give me a yell if you want to test my build. It's not on GitHub, but I'm sure we can arrange something.

[thomaslove]

I'm getting this issue as well. Files uploading successfully with FS.Filesystem but still getting the same error. Chrome as well

[tinchoz49]

Same here! :+1:

The uploader is working excellent but i'm getting the same warning.

Chrome version: 43.0.2357.81 (64 bit) Adapter: GridFS

[JohnBernardsson]

Yup! For me everything seems to be working but I am also getting the warning. Seems to be only in Chrome... at least Firefox doesn't give me any warnings. I am using cfs:s3 with cfs:filesystem

[MichelFloyd]

I just started seeing this error on Mac/Chrome as well (but files seem to be uploading ok). Error does not occur on Mac/FF

[kenken17]

Having same warning here. Is that what we should fix on our side?

[constantinmusca]

I have also seen the warning. Any update on the matter ?

[Ethaan]

Same here

[MichelFloyd]

Still seeing this problem :(

[mgoldberg524]

I've made an example repo that produces the warning for me on Google Chrome 43.0.2357.130 if it could be of some help.

[rhyslbw]

Hey guys, I'm quite time poor here at the moment to even look into this, but if anyone can resolve the problem I can review and roll it in

[kodamirmo]

I had the same issue on chrome/mac but when I built the project the error was gone!!

[clarkritchie]

We're seeing this, too.

[genyded]

Not sure if the same fix would apply here, or where to make it but https://github.com/aldeed/meteor-http-extras/pull/8 had the same error and that pull fixed it. Seems to only happen in chrome and in dev mode.

[Obiwarn]

same problem here

[isAlmogK]

I'm getting this issue as well I take it's not fixed

[miri-am]

same here

[minafarid]

same here

[ekuiter]

same here (Chrome / Mac with gridfs / dropbox)

[mbabauer]

I am also getting this error: Mac / Chrome / filesystem

[WanielDeiss]

same here: Chrome 45.0.2454.93 (64-bit) Mac 10.10.5 Meteor 1.1.0.3 cfs:filesystem 0.1.2 cfs:standard-packages 0.5.9

[johngonzalez]

same here: Versión 45.0.2454.93 (64-bit) Ubuntu 14.04 Meteor 1.2.0.1 cfs:[email protected] cfs:[email protected] cfs:[email protected]

[udisun]

This issue isn't fixed yet. Still have it, the problem is that the name is not taken from the file although the file contains a valid name property.

for some reason it looses it

[Maay]

+1

[Maay]

@udisun did u manage to fix it?

[ptrmrrs]

I'm beginning to think this project is mostly dead. Nothing has been updated in months and issues like this remain unresolved.

I've since moved my project to slingshot and have had far fewer issues. It was a lot easier to configure too.

[udisun]

My pull request fixed the issue. But without the maintainer merging it we are stuck

[Maay]

@udisun i've made your changes locally but still got the same problem.

[thearabbit]

I have the same problem.

cfs:standard-packages
cfs:gridfs
yogiben:autoform-file