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

I updated to jquery-rails 1.0.18, but still getting old jquery #37

Closed
nathanvda opened this issue Nov 23, 2011 · 5 comments
Closed

I updated to jquery-rails 1.0.18, but still getting old jquery #37

nathanvda opened this issue Nov 23, 2011 · 5 comments

Comments

@nathanvda
Copy link

Hi, I updated to the new version, and restarted my server, but it still serves the old jquery. I am just running in development mode.

I did rake assets:clean just to be sure, but it did make any difference.

I am running rails 3.1.0. Is there something else I need to do to remove the old jquery. Now it is still loading jquery 1.6.2.

If you need more info, just ask.

@nfm
Copy link

nfm commented Nov 26, 2011

Do you have a copy of jQuery manually installed into app/assets/javascripts or vendor/assets/javascripts? What do your sprockets manifests look like?

@thomasmulloy
Copy link

I'm having the same issue, upgraded to latest gem version and still pegged to jquery 1.6.2, jquery was installed with a default rails 3.1 application creation.

@nfm
Copy link

nfm commented Dec 14, 2011

@thomasmulloy Have you run rake assets:clean to make sure there are no old precompiled assets hanging around? Can you post your javascript manifest files?

@thomasmulloy
Copy link

cool, i was able to get it updated (not sure if this is the best approach) by updating my gemfile to

gem 'jquery-rails', '~> 1.0' 

and running

bundle update jquery-rails

it was pegged to jquery-rails 1.0.16 and now is 1.0.19

@nathanvda
Copy link
Author

I am not sure how, but for me this problem fixed itself. Not sure what it could have been? My chrome that failed to load the actually changed application.js ? I failed to think of that before. Not sure what other causes could have been. I have not changed gemsets or anything, not done a complete bundle update or anything.

So I will close this.

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

No branches or pull requests

3 participants