Added the beta to a site I’d already set up (staging), and the custom fonts aren’t coming through.
The Font Family is set up correctly. In this case, with Libre Baskerville. However, inspecting the front end just shows “inherit” for the font family of the headline element.
Same here. If “Inherit” gets unticked in the Dev tools, then the font is a correct one.
@devinelston, thanks for the heads up here. The CSS you’re showing looks like that of a Text element. I’m not sure how that could be getting mixed up. Would you mind sharing a link to the page for this? Thanks!
Yeah, you’re right about that screenshot – it’s a Text element. Affects Headline elements too but doesn’t turn Headlines INTO Text elements 
Ok thanks! I’m still not seeing this happen. I’ve made some adjustments though that might help - let me know if you see anything like this in the next beta.
@alexander , if it helps, the same issue is with all the headlines on the staging site (Outwardbound) that I have shared credentials for. The other one with old Pro has the normal font (Anton font).
Thanks! I’ll have a look.
@alexander, this is still happening for me in Beta 3.
Font Settings:
Builder:
Front end CSS:
So, it just looks like the font-family isn’t getting passed through?
Ok, I think I finally cracked this. Crazy type error that was hard to catch. Some older font IDs like the internal “Headings” had IDs like 48656164696e6773 which was mistakenly getting converted to a number with an exponent in PHP… should be all set here for the RC.
