search

seyhunak / twitter-bootstrap-rails

Twitter Bootstrap for Rails 6.0, Rails 5 - Rails 4.x Asset Pipeline
https://github.com/seyhunak/twitter-bootstrap-rails
4.5k stars 996 forks source link

If LESS is customized: 'twitter/bootstrap/responsive.less' wasn't found #770

Closed counterbeing closed 10 years ago

counterbeing commented 10 years ago

I was having some issues with the current gem 'twitter-bootstrap-rails' and some of the grid system not loading for whatever reason. I decided to try out the latest master, and my grid issue went away. I then generated the app/assets/stylesheets/bootstrap_and_overrides.css.less less file, and everything seemed peachy. It is currently as the generator intended it, but the moment I change a single line, or even add a comment in, it blows up with 'twitter/bootstrap/responsive.less' wasn't found.

I'm very confused as to how this could be, because I'm not changing any of the LESS when it blows up. If I even add a blank line, or duplicate an existing line, that error comes back. Here's the last line in the file:

// @linkColor: #ff0000;

If I change that to:

// @linkColor: #Ff0000;

Everything fails. I've never seen anything quite like it, and the stack trace is only one layer deep where rails includes its assets in my layout.

Any help would be appreciated! I would also love to know how this is even possible, it has me so confused.

My setup: Rails 4.1.4 Ruby 2.1.0 Twitter Bootstrap Rails a4da0dc85a7d5ece81006004b3adec4de7cef391

toadkicker commented 10 years ago

Sounds like you have several issues happening. Let's start with the first:

'twitter/bootstrap/responsive.less' wasn't found is true, it doesn't exist. Look in vendor/toolkit/twitter/bootstrap for available files you want to import. Also if you're importing the same file twice, LESS with throw an exception. Its best in this case to @import twitter/bootstrap_base and add the other LESS files you want.

Secondly, the linkColor should be lowercase. I see this is true when I generate it; I'm not sure why you wanted to change that. It sounds unrelated by my guess.

Feel free to post your stack traces. They are helpful in helping make the gem easier to use.

Finally, I maintain a reference app and you're welcome to grab it.

counterbeing commented 10 years ago

Thanks a bunch Todd. I think you nailed part of the problem on the head. In between trying different things I managed to generate both the static setup and the LESS setup. That was what messed me up, once I realized I had the static css, I just removed it, and all of my problems went away.

May this save someone a couple of hours! Thanks so much!