When I compiled with a preprocessor client I received the error

variable @container-lg-desktop is undefined
--sites\all\themes\wo\bootstrap\less\grid.less line 277
---sites\all\themes\wo\less\style.less

I see that grid.less expect this variable (container-lg-desktop) but in our variables.less we have container-large-desktop. For an east fix I added container-lg-desktop in variables.less with the same value as container-large-desktop

Comments

Anonymous’s picture

This is caused by a version mismatch.

You are using /bootstrap source 3.0.0, but the theme requires bootstrap 3.0.1 or higer.

However, LESS 0.4.0 no longer works with bootstrap 3.0.3.

Effectively, this theme is now broken.

lmeister’s picture

Thankyou, I experienced this issue but your comments got me on the right track.

I used bootstrap source 3.0.3 then upgraded the files in my drupal bootstrap sub theme /less folder. The two files I copied in from bootstrap source were:
Bootstrap.less (Modify the import paths in this file similar to old one)
Variables.less (Change path for @icon-font-path similar to old one)

Now everything compiles without error. I'm using LESS.js (1.6.0) through WinLess.

cimo75’s picture

#2 worked for me

Darko’s picture

To avoid any variables mismatch you can also add
@import "../bootstrap/less/variables.less";
at the top of your imports in bootstrap.less file ( make sure it goes before you include your own overrides in @import "variables.less";)
This way you will have all the variables available regardless of the bootstrap version release (at leaset from 3.0.0 to 3.0.3 that I tested)

markhalliwell’s picture

Status: Active » Closed (duplicate)
Related issues: +#2164305: Update to 3.1.1

Marking as a dup of this issue.

Also, I would strongly recommend against using the above @import. This is extremely bad practice. As I've stated before in other issues, the reason you are getting errors is because it is telling you what is wrong. The errors needs to be fixed, not masked. If you @import the variables.less file, you will continue using the incorrect variables in your sub-theme. This can cause confusion as a person might expect the changed variable to affect the compiled code (which it may not since certain variable names may have changed or do not exist, as is in this case).