The problem is that Beaver Builder inherits the theme’s H1-H6 tags, which is actually a good thing. Not sure why you want to override the Heading styles, but there are many ways to do it.
1)How about using a regular Text module and adding a Custom CSS class in line with your heading text?
Add the following to your Dynamik Custom “CSS” Area:
Not sure why you want to override the Heading styles, ...
Colin, it’s because it is an option within the Heading Module in BB and one should be able to use it as needed
That said, and I have posted this on the DWB forum; it is an issue with DWB, as this option works just fine, out of the BB box, as it were, with any other theme that I have tried. Namely, Genesis by itself, a few Genesis child themes, a couple of WP default themes (2015, 2014, 2013) and a few random ones from the WP theme repo. No need for custom CSS with them. This is why I am curious as why DWB behaves in this manner
Hi Lyle and Colin, I appreciate your input… Thanks
Lyle you beat me to the punch but Colin I thought I’d throw another one while you’re on the ropes…
The reason I want to override the DWB heading style is because I just want the font on ONE header to be big around 60px and in the bb header module it gives you that option to change the font size…
The header module also has the option to set a font size for mobile displays which is great as 60px is way to big for smaller devices
But that doesn’t work either…
So it’s frustrating I’m unable to use one of the bb’s features… It’s a bit like having a keyboard and the @symbol don’t work… I can get round it by copying and pasting but it’s not ideal. haha…
If it’s a bug that can’t be fixed then I would have to use the text module that you suggested.
But how would I make the font only smaller on mobiles and tablets?
me again someone from the DWB forum earleir kindly posted this…
This is clearly a CSS issue.
Dynamik has something like this
.content .page h3 {font-size:2.8rem;}
In this case the h3 tag wins.
where BB has this: (without the h3 tag and therefore is not specific enough)
.fl-node-54ff63ae6e1be .fl-heading {font-size:48px;}
All BB needs to do is add the h3 tag to the selector like this and it should work and be compatible with existing setups (note the node id number will likely change with each use)
.fl-node-54ff63ae6e1be h3.fl-heading
I’ve emailed it to billy and he just replied saying
Thanks for bringing that back, Jason We’ll take a look at implementing that! We’ll review asap
Beaver fingers, knees and elbows crossed its reviewed “TONIGHT”…
Thanks for asking. Releasing on Sundays gives us plenty of time to test and add in any last minute fixes that may come up during the week. Also, I usually have plenty of uninterrupted time on Sundays to focus on getting a release out without any issues.