Style Manager

From IThemes Codex
Revision as of 09:08, December 1, 2011 by Sridhar (Talk | contribs)
Jump to: navigation, search



Style Manager is a plugin for iThemes Builder that provides a easy interface to adjust styling of various elements of Builder theme at a basic level.

It can be downloaded from Member Panel.

Style Manager Support Forum

Style Manager Video

Above video is 73-minute recording of "Builder Style Manager Exposed" webinar from that shows you how to use the Builder's style manager to control the look of your site.

Corresponding blog post.


Styles appear in preview window but not on the site

  • Use Firefox. Do not use other browsers, especially IE when using Style Manager.
  • Ensure that your site is hosted on a server that runs PHP 5, not PHP 4. ServerBuddy plugin can be used to check this and more. You can contact your host for help on upgrading from a older version of PHP to version 5.

Preview window is too small to be usable

Ensure that WordPress address and Site address are the same at Settings -> General.

More info.

How to add fonts

It is possible to add font stacks and font sizes by adding code to child theme's functions.php.

Example code:

function customize_font_stacks( $font_stacks ) { 
    $new_font_stacks = array(
        "Arial, 'Helvetica Neue', Helvetica, sans-serif"  => 'Arial',
        "Baskerville, 'Times New Roman', Times, serif"    => 'Times',
        "'Century Gothic', 'Apple Gothic', sans-serif"    => 'Century Gothic',
    return array_merge( $font_stacks, $new_font_stacks );
add_filter( 'builder_filter_style_manager_general_font_families', 'customize_font_stacks' );
function customize_font_sizes( $font_sizes ) { 
    $new_font_sizes = array(
        '37px'      => '37px',
        '37%'       => '37%',
        '37pt'      => '37pt',
    return array_merge( $font_sizes, $new_font_sizes );
add_filter( 'builder_filter_style_manager_general_font_sizes', 'customize_font_sizes' );

Video Instructions:

A useful site for font families is

Source: Style Manager Suggestions section at

For an example of using @font-face fonts in Style Manager, see this.

Background color does not appear on the nav bar in the preview window

This is happening because the nav bar has a background image set (depending on the child theme) in child theme's style.css. The solution is to set Background Image to None.


Color changes for links are not showing in the preview window

Make sure you are changing these in the correct section.

Links can be styled in these sections:

  1. Links
  2. Post/Page Content Styling
  3. Module Sidebars -> Widgets
  4. Widget Bar Module -> Widgets

Changes don't appear in Preview although it shows the generated code in CSS Preview

This is most probably due to a more specific CSS being applied to the element of interest via child theme's style.css.

To illustrate this, please see

Even though the text color for widgets of widget bar module has been set to be white in Style Manager, text in the preview window (and on the site) is not white.

This is because of color property in the following from style.css:

.builder-module-sidebar .widget p {
    margin-top: 0;
    color: #333333  ;

There is no option to style paragraphs inside widgets in Style Manager.

So we will have to manually add the following CSS either inside Custom CSS or in child theme's style.css to get our desired white color text inside widget bar module's widgets:

.builder-module-widget-bar .widget p {
    color: #FFFFFF  ;

Changes like setting body background image appear in the preview but not on the site

Webpage elements like Slideshow plugin and AWeber widget script could directly inject CSS into the content of the site.

Ex.: The style injected by AWeber has a rule of body {}. This empty body rule is overriding the one created by Style Manager that sets the background, causing the background modification to be lost in the generated stylesheet.

To diagnose this problem, observe CSS rules in the CSS Preview box such as #af-form-1602098000 { overflow: hidden; } as Style Manager would never produce such a rule. This means that rules from other styles are bleeding into Style Manager's generated stylesheet.

The way to manually work around the issue is to navigate the preview to a view that is free of any styles in the content. Ex.: Let's say there is a View that uses the Full Width Layout (no aWeber widget) for archives (no slideshow slider). Navigate the preview to any archive page, wait for the CSS Preview to refresh, and then save the uncorrupted Style.

To summarize, the fix is:

  1. Edit the Style in Style Manager
  2. Navigate in your preview to a page that does not have an problem causing elements like Aweber form or a Slideshow
  3. Save the Style

Forum topic:

Unable to generate stylesheet file. Check file permissions for your uploads directory

When you get the following upon saving a style in Style Manager

Unable to generate stylesheet file. Check file permissions for your uploads directory. The stylesheet will still function but will not be as efficient as it could be.

the fix is to correct the wrong path that is present for "Store uploads in this folder" field at Settings -> Media. Change it to "wp-content/uploads".

Useful tips and forum links

  • See this forum topic on permissions. Summary: "Anyway I discovered the css files being created in wp-content/uploads were being created with rw rw — permissions and as soon as I changed the file permissons to be rw rw r it all worked perfectly."
  • If you are using 1&1 hosting, create a single line .htaccess file with this code "AddType x-mapp-php5 .php" and upload it to the root. Source
  • At Settings -> General, if WordPress address (URL) and Site address (URL) are the same location (which is usually the case), ensure that they are exactly the same. Ex.: "" for both the fields is good, not "" for one and "" for the other.


It is not possible to apply one set of styles to the complete module or individual widgets of a module differently than other modules of that type. i.e., the styles that you set to widget bar modules will apply to all widget bar modules. Ex.: You will not be able to apply say, a blue background to just one widget bar module while the rest of them have been set to say, a red background via Style Manager. For such changes, style.css has to be edited manually.

Personal tools
iThemes Codex
Codex Navigation