Font Library: first time install fails if /wp-content/fonts isn't created.

[mmaattiiaass]

The first time the user want to install a font via the font library, it fails with this error message:

Some font faces were installed. There were some errors. Fetch error: Unable to create directory wp-content/fonts. Is its parent directory writable by the server?

After the first attempt, the font installation process works as expected.

This happens because the /wp-content/fonts is not created by the time of the first attempt, after the first one it is created and it works as expected. A fix for this probably consists of creating the folder before trying to write in it.

[hellofromTonya]

Issue opened in Gutenberg ​https://github.com/WordPress/gutenberg/issues/59023. The issue will be diagnosed and resolved there. When ready, the fix and any tests will be resynchronized here with a Core patch.

Moving this Trac ticket into 6.5 for tracking.

[mmaattiiaass]

I've been trying to reproduce this issue but I couldn't do it. Today, I spent a few hours creating new environments using wordpress-develop env, wp-env, apache running locally, and other platforms like instaWP, and it didn't fail for me. It seems to be very tricky to reproduce. Because of this, I tend to think it is related to a race condition in wp_mkdir_p. Could that be possible?

[oglekler]

Bug Report

Description

The first upload of fonts creates an error message, even if they were uploaded and the folder was created.

Environment

• WordPress: 6.5 RC1
• PHP: 8.1.9
• Server: Apache
• Database: mysqli (Server: 10.8.4-MariaDB / Client: mysqlnd 8.1.9)
• Browser: Chrome 122.0.0.0
• OS: Windows 10/11
• Theme: Twenty Twenty-Four 1.0

[swissspidy]

Issue opened in Gutenberg ​https://github.com/WordPress/gutenberg/issues/59023. The issue will be diagnosed and resolved there.

Closing as reported-upstream for now. There hasn't been any progress on the issue, so regardless of resolution it won't be in time for 6.5 anymore.