Support » Plugin: Widget Wrangler » Intrusive CSS for widget content

  • Hi Jonathan (this is Diana from the Meetup.)
    I’m using Widget Wrangler for the first time on a Genesis website. When I create and add widget content using the Post editor, the widget content is placed with class tags for “widget” and for “content” which actually mucks things up, and looks like a widget-inside-a-widget, and is not word wrapping inside the sidebar, as “content” inherits a defined width, and “widget” inherits an additional left padding style. Is this markup being inserted by Widget Wrangler?

    Guided Tour of Scandinavia in August 2017

    I didn’t see a place where I could manage the default CSS for the Widget Wrangler widgets, is there such a thing, or must I create my own set of CSS rules for classes “widget” and “content” specific to Widget Wrangler class?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Jonathan Daggerhart


    Hi Diana,

    That extra wrapping div is probably add by Widget Wrangler. You should be able to get rid of it by disabling “Theme compatibility” on the admin page: Widget Wrangler >> Settings. This setting has a confusing name and is mainly for purchased themes that modify the sidebar html significantly.

    Let me know if that doesn’t work for some reason.


    Thanks, Jonathan.

    While disabling the Theme Compatibility setting resolves one problem (the left extra border and spacing) it doesn’t address the theme-forced 740px for class=content. Also, when the theme compatibility setting is turned off, I can’t add class “wwrangler” in the Sidebars setting, so it doesn’t appear in the hierarchy for CSS customization convenience. The option to modify the sidebar classes only appears when Theme Compatibility is turned on. So…. I’ll leave Theme compatibility on, and write a bit of CSS to fix the display. Just a suggestion: I’ve worked with customizing other plugins, and it’s always a great convenience when the developer anticipates this need and adds a blank custom wrapper class so the designer doesn’t have to modify code (horrors) to introduce a parent class. Ciao!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Intrusive CSS for widget content’ is closed to new replies.