Skip to content
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

data.result is cloudinary_cors.html contents #333

Open
brandoncc opened this issue Jan 26, 2019 · 6 comments
Open

data.result is cloudinary_cors.html contents #333

brandoncc opened this issue Jan 26, 2019 · 6 comments
Assignees
Labels

Comments

@brandoncc
Copy link
Contributor

I'm using the jquery fileupload method to upload files. data.result is an object as expected in < 1.1.2, but as soon as I go to 1.1.3+, it contains the HTML that is in cloudinary_cors.html. I also just recently did a Rails 5 upgrade so I am not sure if it is something to do with that. Any help would be appreciated!

@yakirp
Copy link
Contributor

yakirp commented Jan 29, 2019

Hi @brandoncc
Could you please elaborate about the version you mentioned -(1.1.2,1.1.3) versions of what?

Thanks

@yakirp yakirp self-assigned this Jan 29, 2019
@brandoncc
Copy link
Contributor Author

The cloudinary gem @yakirp

I currently have to use:

gem 'cloudinary', '= 1.1.2' 

If I go to 1.1.3, the problem I described happens and I have no idea why.

@yakirp
Copy link
Contributor

yakirp commented Feb 4, 2019

Hi @brandoncc ,
Maybe you should try with a newer version? The version you're using is 3 years old...

Please let me know

Thanks,
Yakir

@brandoncc
Copy link
Contributor Author

That is what I was working on when I found this problem. I worked my way backward down versions until I found the version where the problem started and opened this issue.

@yakirp
Copy link
Contributor

yakirp commented Feb 5, 2019

Ok, thanks. So It's not happened on newer versions, right?

@brandoncc
Copy link
Contributor Author

I believe you misunderstood me. It happened on the latest version when I updated to it, so I worked my way backward through the versions until I identified where the problem started. To be clear, it happens in the latest version of the gem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants