Hi,
I just started using Page Builder and noticed that t adds the class “widget” to all items.
In many themes widget areas are styled differently from the way the regular content is styled. I personally feel that the widget class should not have been added in the first place.
I’m modifying the Twenty-Fifteen template and widgets have a distinct style (smaller fonts and a % margin).
Here’s the panel being created and “widget” is added to the classes.
How can I best remove “widget” from being added?
In such a way that theme and Page Builder updates will noyt overwrite the changes.
Thank you for your help!
Regards,
Dennis
Here’s the code which shows “widget” being added.
Never mind. I just uninstalled PageBuilder.
In my opinion a plugin should only style elements that it specifically adds so it will respect the design of the website it is used in. Most plugins do not, so you waste a lot of time needlessly correcting css / creating a child theme.
I’m a bit disappointed because I really like the SiteOrigin products but will revisit again.
The little quotes at the bottom right are brilliant! :-)
Hi Dennis
Thanks for reaching out.
We do our very best to get everyone promptly but during busy times, as we’re having now, unfortunately, do attend to our premium theme customers first, hence the delay.
Ideally, as Page Builder grows (we have over 600,000 active installs now), themes will stop targeting the top level widget class and be more specific. Twenty Fifteen knows where it’s own widget areas are so it would be super easy for it to prefix those. If you’d like to give Page Builder another go it would be relatively quick to roll back the Twenty Fifteen widget styles for Page Builder. Let me work that up for you quickly.
Here we go, this is a good start. Insert into a Custom CSS plugin:
I’ll get back to you tomorrow regarding your question why aren’t we filtering out the widget class to begin with. It’s a good question for sure.
Hi Andrew,
Thank you for your replies. Much appreciated!
It goes without saying that support for paying customers goes first.
Also, the solution you provided works perfectly.
Why didn’t I come up with that :-)?
I still think that plugins should avoid styling common elements and classes (body, h1, .widget etc.) but PageBuilder stays installed.
P.s. Unfortunately I cannot change the thread to [solved] perhaps you can do that?
Thanks for your understanding. We’ve chatted about the challenge this morning. It’s not possible, for legacy reasons, to remove the widget class at this stage. But, we’ll definitely look at provide an option in Page Builder settings to remove it. I’ll chat further with Greg about this later today.
If there is anything more I can help with, just post here and I’ll jump in.
Cheers for now :)
OK, thanks for the update.
I have one additional question.
When I open a page which uses PageBuilder I briefly see the normal WP editing area (filled with shortcodes etc.). Is it possible to switch to the editing area without losing the PageBuilder content (I know you can switch)?
Sometimes it’s easier to edit code.
On one of my sites, which uses Visual Page Builder, for instance I created one FAQ accordion and made the other 30+ using Excel and copy/paste (example
etc.).
Thank you once again.
Unfortunately not. If you switch back everything will be dumped into the Text tab. When you try go back to Page Builder all content will go in a single SiteOrigin Editor widget.