Theme Pro Bug

[RivmanBx]

Latest version Version : 4.1.3
There is a bug in /framework/dist/css/admin/visual-composer.css

@font-face {
font-family: "fontawesome";
src: url("../../../fonts/font_awesome/fontawesome-webfont.eot?v=4.5.0");
src: url("../../../fonts/font_awesome/fontawesome-webfont.eot?#iefix&v=4.5.0") format("embedded-  opentype"), url("../../../fonts/font_awesome/fontawesome-webfont.woff?v=4.5.0") format("woff"), url("../../../fonts/font_awesome/fontawesome-webfont.ttf?v=4.5.0") format("truetype"), url("../../../fonts/font_awesome/fontawesome-webfont.svg?#fontawesome&v=4.5.0") format("svg");
font-weight: normal;
font-style: normal
} 

It’s good to write marketing sentences like “We use latest version of Font Awesome” but it’s also a good practice to test theme before release, for old references of old font names or look at the logs.

Hope to see this fixed soon, every release (update) break the manually made changes, and copying the 4.5.0 version of font in the folder is double use, since the “new” font are already there.

Thanks, and have a great day.

[christian]

Hey @RivmanBx,

Thanks for reporting. I’ll post that in our issue tracker so it will be queued to be changed.

[alexander]

Hi @RivmanBx,

Thanks for the heads up on this. When X was first released, we didn’t have a builder and our approach was to be tightly integrated with Visual Composer. For the past several years we’ve tried to avoid changing VC at all and we only override the backend if the Legacy X Integration setting is enabled. In the next release we’ve fixed the broken icons by removing our per element styling overrides and replaced them all with “X” generically.