Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing Google font error - No font faces were installed. #58997

Closed
kafleg opened this issue Feb 14, 2024 · 8 comments · Fixed by #59015
Closed

Installing Google font error - No font faces were installed. #58997

kafleg opened this issue Feb 14, 2024 · 8 comments · Fixed by #59015
Assignees
Labels
[Feature] Font Library [Type] Bug An existing feature does not function as intended

Comments

@kafleg
Copy link
Member

kafleg commented Feb 14, 2024

Description

While checking WordPress 6.5 Beta 1 and testing Google font installation, fonts are not installed.

image

Finding the issue and discussion can be found here in Slack, https://wordpress.slack.com/archives/C02RQBWTW/p1707883378714549

Solution Found:
Change the number on these two lines from 80100 to 80112 and see if you can install the fonts.

This worked for me.

Step-by-step reproduction instructions

  1. Install WordPress 6.5 Beta 1
  2. Go to Appearance > Editor
  3. Select a heading or paragraph
  4. Click on Styles and then Typography
  5. click on manage fonts icons
  6. Click on Install Fonts and select a font to install
    (Now you can see the issue)

Screenshots, screen recording, code snippet

Recording: https://i.rankmath.com/v/27NfsL

Screen.Recording.on.2024-02-14.at.12_06_19.mp4

Environment info

Environment details on my end:

  • WP: 6.5 Beta 1 (Updated via CLI)
  • Local Server: Laragon
  • PHP: 8.1
  • Browser: Edge
  • OS: Windows
  • Theme: Twenty-Twenty Four
  • Fonts tested: ABeeZee
  • Plugins: None

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

@kafleg kafleg added the [Type] Bug An existing feature does not function as intended label Feb 14, 2024
@huzaifaalmesbah
Copy link
Contributor

huzaifaalmesbah commented Feb 14, 2024

Reproduction Report

First attempt i got this error but second attempt installed successfully.

Environment

  • WordPress: 6.5-beta1-57631
  • PHP: 8.3.2
  • Server: nginx/1.25.3
  • Database: mysqli (Server: 11.2.2-MariaDB / Client: mysqlnd 8.3.2)
  • Browser: Chrome 121.0.0.0
  • OS: macOS
  • Theme: Twenty Twenty-Four 1.0
  • MU Plugins: None activated
  • Plugins:
    • Test Reports
Screenshot 2024-02-14 at 12 46 32 PM

@costdev
Copy link
Contributor

costdev commented Feb 14, 2024

@huzaifaalmesbah Just to clarify: The error you received is due to filesystem permissions that must be handled on the system.

The problem reported in this issue is that the woff/woff2 font format has a different MIME type from PHP 8.1.12 onwards. The Font Library's code that handles this change checks for >= PHP 8.1.0, rather than >= PHP 8.1.12, causing a failed MIME type check for PHP 8.1.0 through 8.1.11.

To verify this issue, a PHP version between 8.1.0 and 8.1.11 must be running on the server during the test.

@hellofromtonya
Copy link
Contributor

Hello @huzaifaalmesbah 👋 The issue you found is being tracked in this Core Trac ticket. I'm not seeing a Gutenberg issue opened for it yet though. Hey @matiasbenedetto is there a GB issue for it?

@hellofromtonya hellofromtonya added the [Status] In Progress Tracking issues with work in progress label Feb 14, 2024
@matiasbenedetto
Copy link
Contributor

matiasbenedetto commented Feb 14, 2024

Hello @huzaifaalmesbah 👋 The issue you found is being tracked in this Core Trac ticket. I'm not seeing a Gutenberg issue opened for it yet though. Hey @matiasbenedetto is there a GB issue for it?

Hi @hellofromtonya this is a different issue than the reported in the trac ticket you linked.

We need to create a track ticket for the fix added by @costdev in #59015 to move that change to the core repo.

@hellofromtonya
Copy link
Contributor

We need to create a track ticket for the fix added by @costdev in #59015 to move that change to the core repo.

@matiasbenedetto Ticket already exists https://core.trac.wordpress.org/ticket/60536 in Core. @costdev and I will get the fix sync'd back into Core.

Hi @hellofromtonya this is a different issue than the reported in the trac ticket you linked.

@matiasbenedetto the issue @huzaifaalmesbah showed in the test report above is the same one you reported in Trac 60528. Will that issue be fixed here in Gutenberg first? If yes, is there already a GB issue opened for it?

@matiasbenedetto
Copy link
Contributor

@matiasbenedetto the issue @huzaifaalmesbah #58997 (comment) is the same one you reported in Trac 60528. Will that issue be fixed here in Gutenberg first? If yes, is there already a GB issue opened for it?

Sorry @hellofromtonya, I thought that you were referring to the original issue. I think there was no ticket for that in Gutenberg I created one ( #59023 ) referencing @huzaifaalmesbah comment and adding the trac ticket link

@hellofromtonya hellofromtonya removed the [Status] In Progress Tracking issues with work in progress label Feb 14, 2024
@hellofromtonya
Copy link
Contributor

Fix synch'd into Core with https://core.trac.wordpress.org/changeset/57632.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Font Library [Type] Bug An existing feature does not function as intended
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants