Global font-weight option is not applied

Support
#1

I would like to use a custom font in Cornerstone that I have integrated using the font manager. However, the desired font weights should also be used.

screenshot_ 2025-07-03 um 09.42.57

In the global options for the body font, I have set the desired weight to 300:

screenshot_ 2025-07-03 um 09.44.54

However, the font weight remains fixed at 400!

screenshot_ 2025-07-03 um 09.45.45 screenshot_ 2025-07-03 um 09.46.30

Only if I manually set it to 300 in the Chrome developer tool, for example, can you see the difference and the correct result.

screenshot_ 2025-07-03 um 09.47.43 screenshot_ 2025-07-03 um 09.48.05

The only thing I have noticed is that the weights are split into ‘Managed’ and ‘Exact’, is there a difference?

screenshot_ 2025-07-03 um 09.49.20

But why doesn’t the global option work?

#2

Hello @Regnalf,

Thank you for the inquiry.

Looks like you’re testing it on a Headline or a heading element. Did you also apply the same font weight to the Headings? Please create a test page and provide the login details in the secure note so we can check the issue further.

Best regards,

#3

No, the text in the screenshot is a normal p element, on a normal WordPress page that was not created with Cornerstone. The headling h6 has slipped into the screenshot.

Unfortunately, I cannot provide access to the original site, as the site is still under development and is limited to my IP address, but I have no control over this and it would take weeks before I could register an IP.

But I have found a crucial clue to narrow down the problem. When I wanted to prepare it for you on one of my test pages, I noticed that it works with the ‘Renew’ stack, but not with the ‘Starter’ pack. So for some reason the font weights for the body are not applied, but for the headings it works in both packs.

Maybe you try it again with the ‘Starter’ pack, if you can’t reproduce it then, I will set up access at least to my test server.

#4

Thank you for the info.

We are able to reproduce the issue on our end. Looks like the css rule from pro/framework/legacy/functions/frontend/generated-css/base.php , or possibly the entire file, is not being included when the Starter stack is loaded. We’ll forward this to our channel to confirm if this behavior is intentional. Thank you for your patience.

/* <body>
// ========================================================================== */

body {
  font-style: <?php echo ( $x_body_font_is_italic ) ? 'italic' : 'normal'; ?>;
  font-weight: <?php echo $x_body_font_weight; ?>;
  color: <?php echo $x_body_font_color; ?>;
  <?php if ( $x_design_bg_image_pattern == '' ) : ?>
    background-color: <?php echo $x_design_bg_color; ?>;
  <?php else : ?>
    background: <?php echo $x_design_bg_color; ?> url(<?php echo x_make_protocol_relative( $x_design_bg_image_pattern ); ?>) center top repeat;
  <?php endif; ?>
}

In the meantime, you can manually declare this css rule in the Custom Code > Global CSS field.

Best regards,

#5

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.