Skip to content

Issue with Google Fonts persistence after Jetpack deactivation in WordPress 6.5 (RC2) #36371

@briceduclos

Description

@briceduclos

Impacted plugin

Jetpack

Quick summary

In WordPress 6.5 (RC2), after making changes in the Font Library, deactivating the Jetpack Google Fonts module or the entire Jetpack plugin results in all previously added Google Fonts being permanently printed (more than 600 lines) on the website's front-end. This happens without providing users an option to remove these fonts.

Steps to reproduce

  1. Install WordPress 6.5 RC2.
  2. Activate the Jetpack Google Fonts module.
  3. Install a new Google Font using the Font Library feature (which saves the font settings to the database).
  4. Deactivate the Jetpack Google Fonts module.
  5. Check the website's front end and observe that all previously added Google Fonts are still being loaded, with no way to remove them.

A clear and concise description of what you expected to happen.

No response

What actually happened

Jetpack adds its Google Fonts using the wp_theme_json_data_default hook, which means the fonts cannot be managed or removed through the Font Library. #33203

Impact

All

Available workarounds?

No but the platform is still usable

Platform (Simple and/or Atomic)

No response

Logs or notes

No response

Metadata

Metadata

Assignees

Labels

BugWhen a feature is broken and / or not performing as intendedTriaged[Feature] Google Fonts[Focus] CompatibilityEnsuring our products play well with third-parties[Plugin] JetpackIssues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/[Pri] Normal[Status] Priority Review TriggeredThe guild in charge of triage has been notified of this issue in Slack

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions