Symptom: On themes that register legacy Customify type => typography fields (e.g. Bucket), the generated front-end CSS outputs font-family: Array; for the affected selectors. The browser discards the invalid value and falls back to a default serif font, and the Typography section no longer renders in the Customizer. Affected site is on Customify 2.10.8 (latest), WP 7.0, PHP 7.4.33 — so this is not an outdated-plugin issue.
Evidence:
includes/class-customify-fonts-global.php:214-234 — standardize_font_fields_config() converts the legacy typography field type to font, but the years-old saved value is not normalized to a font_family string.includes/class-customify-fonts-global.php:1008-1023 — getCSSValue() expects $value['font_family'] to be a string; with the un-normalized legacy value it is an array, so the emitted rule becomes font-family: Array.- pixelgrade/bucket
theme-utilities/includes/functions/customify.php:111-203 (hooked at :348) — registers google_titles_font / google_nav_font / google_body_font as type => typography; their exact selectors are the ones broken on the live site.
Repro: Theme registers a legacy typography Customify field with a saved value from an older Customify/PixTypes era -> load the front end on Customify 2.10.8 / WP 7.0 -> font CSS emits font-family: Array.
HelpScout: https://secure.helpscout.net/conversation/3352261813
Symptom: On themes that register legacy Customify
type => typographyfields (e.g. Bucket), the generated front-end CSS outputsfont-family: Array;for the affected selectors. The browser discards the invalid value and falls back to a default serif font, and the Typography section no longer renders in the Customizer. Affected site is on Customify 2.10.8 (latest), WP 7.0, PHP 7.4.33 — so this is not an outdated-plugin issue.Evidence:
includes/class-customify-fonts-global.php:214-234— standardize_font_fields_config() converts the legacytypographyfield type tofont, but the years-old saved value is not normalized to afont_familystring.includes/class-customify-fonts-global.php:1008-1023— getCSSValue() expects $value['font_family'] to be a string; with the un-normalized legacy value it is an array, so the emitted rule becomesfont-family: Array.theme-utilities/includes/functions/customify.php:111-203(hooked at :348) — registers google_titles_font / google_nav_font / google_body_font astype => typography; their exact selectors are the ones broken on the live site.Repro: Theme registers a legacy
typographyCustomify field with a saved value from an older Customify/PixTypes era -> load the front end on Customify 2.10.8 / WP 7.0 -> font CSS emitsfont-family: Array.HelpScout: https://secure.helpscout.net/conversation/3352261813