-
Notifications
You must be signed in to change notification settings - Fork 390
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
defaults.js Not Created #54
Comments
Okay, I see you have to replace:
with:
But, the pointers to the CSS files are still messed up. Still looking for help. |
Having same issue, got past the js, but the CSS sill an issue. Any help appreciated. |
|
that didn't work for me :( No such file or directory - Asset file not found at 'C:/pro-app/public/javascripts/C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/jquery-rails-2.0.2/vendor/assets/javascripts/jquery.js' hope someone can help us with this problem. |
move public/stylesheets/web-app-theme to app/assets/stylesheets/web-app-theme Voila! it works again. |
Also move public/images/web-app-theme to app/assets/images/web-app-theme. |
Changing the line in application.html.erb worked for me. No css errors. |
Thanks knoguchi, it works! |
Followed the instructions here from knoguchi, worked great. Wonder if we can get an update. |
Hello every one.!!! please, help me. |
I'm rather new to Ruby on Rails and Web-App-Theme... and this is the first issue I've ever posted on Github.
When I try even the most basic Rails app with Web-App-Theme, it seems to me that defaults.js is not created. Here's how I tried (I'm using Rails 3.2.0):
Then I edit the Gemfile to add the following: gem 'web-app-theme'
Note: adding "gem 'web-app-theme', '
> 0.8.0'" gave me errors about compatibility, so I just dropped the '> 0.8.0' part and it worked.This seems to work fine when I visit http://localhost:3000/people
When I go to http://localhost:3000/people I get an error message:
When I search the testapp directory, there is no file called 'defaults.js' anywhere.
Am I doing something wrong or is this a bug of some sort?
Thanks for your help.
The text was updated successfully, but these errors were encountered: