Mak, need your help. KrafterPro seems to be causing an issue and I'd like to show it to you and then maybe you can help.
Mak, need your help. KrafterPro seems to be causing an issue and I'd like to show it to you and then maybe you can help.
Issue: If KraftePro is activated on the website, in a text module, and within the text module I have text wrapped within an < h2 > tag. And when I set the < h2 > font size under the "Design" tab, the font size doesn't reflect the changes that I make. Whether I manually enter 20px or 5rem, or a Clamp value, .. the size of the font (when looking in the Divi Visual Builder) doesn't change. The font size changes when I look at the webpage outside of the Divi Visual Builder, but in the Visual Builder, the font size says the same, regardless of what I change. If KrafterPro is deactivated, then this issue goes away.
Can we meet up so I can show this to you in a Zoom call? I'm not sure what's causing the issue.
Please let me know.
Gary
Hi Gary,
Thanks for the clear description. I found the cause, so we don't need a Zoom call.
In the Visual Builder, KrafterPRO applied its default heading size more strongly than Divi's Text-module Heading 2 setting. Your font size changes were being overridden in the builder. The front end wasn't affected, which is why it looked right on the live page.
I've fixed it and tested it. Typing 20px, 5rem or a clamp() value in the Design tab now updates the text in the builder. I'm releasing a patch in a few hours. Once it's out, update KrafterPRO, then close and reopen the Visual Builder.
One thing to expect: an h2 with no size set in the Text module may show Divi's default size in the builder rather than the fluid size. The live page still uses the fluid size, and any size you set on the module takes priority.
I'll let you know when the patch is live. If it still misbehaves after updating, send me a screenshot or a short screen recording and I'll look again.
Thanks for flagging this,
Mak
@funnelstoincome Thanks. You're the best. -Gary
@funnelstoincome Did you release the fix yet? Please let me know what version has the fix so I can make sure I’m installing the correct version. Thanks.