I realize that this is not technically an Omega problem per se, but I wanted to note it here so that A) the gemfile.lock could be updated and B), people experiencing trouble with SIngularity layouts might find this issue and remedy their problem.

My specific issue was that I was trying to use fixed gutters, which are a feature of Singularity 1.1.2 (the latest version as of 08-21-2013. Singularity was up-to-date on my system, however in the gemfile.lock, it specifies that Singularity 1.0.8 should be used. If you try to use fixed gutter variables with this old version of Singularity, you get some weird, broken results.

Since Omega 4.x is so closely tied to Sass-based grid systems, should we keep a closer eye on the gemfile.lock that comes with it? Should there be explicit instructions for users that they may need to update it right away after creating their subtheme? What if the drush omega subtheme creator tells users to run "bundle update" after they finish installing their subtheme? I'm just posing possible questions & solutions.

Comments

fubhy’s picture

Hmm. Do you mean the Gemfile.lock in your subtheme? Because omega does not ship with any Gemfile.lock. That file is generated as part of the 'bundle install' process. So it's 100% up to you to maintain and update it if desired.

fubhy’s picture

Did you read about and are you using RVM as I suggest in various issues here in the issue queue?

Kendall Totten’s picture

Status: Active » Closed (works as designed)

I am, I think perhaps it came from an existing test subtheme I was using a few months ago, and I wrongly assumed that Omega had generated it, when I probably did as I was learning to use RVM. Sorry about that!