Closed wolframarnold closed 12 years ago
I created a simple pull request for fixing that: https://github.com/maxim/bootswatch-rails/pull/3
I just removed those variable definitions so the original ones from bootstrap-sass are taken into account. It fixed it for me.
Thanks for doing this. I didn't have time to make a pull request, but just removing the definitions should do it, yes.
Wolf
On Thu, Apr 26, 2012 at 10:38 AM, Mathieu Lajugie < reply@reply.github.com
wrote:
I created a simple pull request for fixing that: https://github.com/maxim/bootswatch-rails/pull/3
I just removed those variable definitions so the original ones from bootstrap-sass are taken into account. It fixed it for me.
Reply to this email directly or view it on GitHub: https://github.com/maxim/bootswatch-rails/issues/2#issuecomment-5363289
www.RubyFocus.biz --- San Francisco --- direct: 650-576-9048
+1.
Remove the definitions or redefine the Sprite Paths correctly.
The commit above fixes this issue and can be closed.
Thanks @maxim for bootswatch-rails!
I think there is a bug in the bootswatch-rails code.
It overrides the variables as follows:
However, in the boostrap-sass package, these variables are set with the
asset_url
helper:It's not even clear why that Bootswatch library needs to override these variables, because they're the same as the default.