I made a child theme from the Bootstrap 7.x-2.1 base theme. I then assigned the class "icon-arrow-left" to an element in some page markup, as per bootstrap methodology.
After adding the TB Mega menu I get two icons for this element overlaid on each other, the bootstrap version and the fontawesome version (but only on elements outside of the TB Mega menu).
Commenting out the rules on line 57 of font-awsome.css gets rid of the glyphicons used by bootstrap, showing only their fontawesome counterparts.
| Comment | File | Size | Author |
|---|---|---|---|
| overlaid-icons.png | 441 bytes | davidlovere |
Comments
Comment #1
davidlovere commentedI decided to go ahead and disable font-awesome by commenting out lines 227 -232 of tb_megamenu.module and lines, 39 - 44 of tb_megamenu.admin.inc, as well as line 1 of base.css. This may not be the best solution but it works in my environment.
It would be nice if your software could give the admin a choice of whether or not to use font-awesome, thus eliminating the problem of customization.
Comment #2
ñull commentedThere is also the fa module that depends on the fa library. It would be better to make tb_megamenu compatible with that and not install its own (outdated) fa. I need the square versions of twitter, google and facebook and in the tb_megamenu they are not available. tb_megamenu should probably use the library folder too.
Comment #3
dsrikanth commentedThank you so much for #1! That did the trick for me.
Comment #4
ñull commentedA new upgrade overwrote my changes. Please come up with a solution for this!Comment #5
ñull commentedComment #6
ñull commentedIt was not this module that messed things up but fontawesome and icon (api). icon dev version is compatible with fontawesome 4.x, but the latest release version of fontawesome module is using the older 3.2.1 which is not compatible with icon api. Sorry for me overreacting and accusing wrongly
Comment #7
ñull commentedThe code of beta5 checks the presence of fontawesome in libraries so this ticket can be closed now