Make WordPress Core

Opened 8 months ago

Closed 3 months ago

#60028 closed defect (bug) (worksforme)

Custom heading Fonts in theme.json and editor are overruled

Reported by: perthykjaerjensen's profile perthykjaerjensen Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.4.2
Component: Bundled Theme Keywords: has-screenshots reporter-feedback close
Focuses: Cc:



When I try to change the heading fonts in the editor, the font is visible. It will show up in the preview. But as soon as "save" is clicked the standard font is still there.

I have the same problem in twentytwentyfour/styles/

## Here I add a custom font

## Now I click save

The theme fonts is still there.

Since this is a problem in both Twenty Twenty Four and my theme from scratch I asume that this is a bug.

Attachments (2)

font-a.png (478.7 KB) - added by poena 3 months ago.
font-b.png (347.2 KB) - added by poena 3 months ago.

Download all attachments as: .zip

Change History (6)

#1 @poena
3 months ago

  • Component changed from Themes to Bundled Theme
  • Keywords reporter-feedback added
  • Severity changed from major to normal

Hi @perthykjaerjensen
I am changing the component from "Themes" to "Bundled theme" in case this is a problem with Twenty Twenty-Four, and for increased visibility.

Because this ticket was created four months ago, before the Font Library feature, I want to ask how you added the custom font choice to the theme?

Looking at the screenshots you provided, it does not look like the font that is used after you click save is the default font, "Cardo". To me, it looks more like the font family is missing.

I wonder if perhaps there is a typo in theme.json, because that is known to break some styling.

3 months ago

3 months ago

#2 @poena
3 months ago

I uploaded your images, so that they are not lost if your site changes.

#3 @karmatosed
3 months ago

  • Keywords close added

@perthykjaerjensen are you able to confirm if this was a typo? I agree with @poena that with the feature of the font library this should resolve or is expected to your issue. That said, if you are still experiencing this please let us know.

As we haven't had any response on this I am going to tentatively add the close keyword for now. We can always remove it or continue discussion should that be more valid. Thank you everyone.

#4 @karmatosed
3 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from new to closed

As this has waited a little while I am going to now close this. Thank you everyone for your collaboration so far.

Note: See TracTickets for help on using tickets.