Add fonts upload location to Site Health report

[swissspidy]

Just like Site Health lists the paths to the plugins/themes/uploads directories, we should list the path to the fonts directory (and its size) there as well.

[swissspidy]

There could also be a general check whether wp-content itself is writable or not.

Edit: this already exists!

Added the font directory in the array for site health table iteration

[krupajnanda]

I tested changes with mentioned GH PR and it shows the font dir path and size to Site Health.

Test Report

Description

This report validates whether the indicated patch works as expected.

PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260

Environment

• WordPress: 6.6-alpha-57778-src
• PHP: 8.2.15
• Server: nginx/1.25.3
• Database: mysqli (Server: 8.0.36 / Client: mysqlnd 8.2.15)
• Browser: Chrome 123.0.0.0
• OS: macOS
• Theme: Twenty Twenty-Four 1.0
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.1.0

Actual Results

1. ✅ Added changes are working as expected with given PR.

Additional Notes

• Any additional details worth mentioning.

Supplemental Artifacts

Add as Attachment

Thanks for the PR, @andr3ribeiro! Perhaps a good addition to this would be to include the fonts dir "is writable" check found on the Filesystem Permissions tab. This work is something we could probably get merged early this cycle.

[iamfarhan09]

Bug Report

Description

According to this report, the patch indicated works as expected.

PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260

Environment

• WordPress: 6.6-alpha-57778-src
• PHP: 7.4.33
• Server: nginx/1.25.1
• Database: mysqli (Server: 8.0.37 / Client: mysqlnd 7.4.33)
• Browser: Chrome 124.0.0.0
• OS: macOS
• Theme: Twenty Twenty-Four 1.0
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.1.0

Actual Results

1. ✅ I have tested the added changes with the given PR and they are working as expected.

Attachment Screenshot at May 10 10-52-59.png​ added

[naeemhaque]

Bug Report

Description

This report validates whether the indicated patch works as expected.
PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260

Environment

• WordPress: 6.6-alpha-57778-src
• PHP: 7.4.33
• Server: nginx/1.23.2
• Database: mysqli (Server: 8.0.36 / Client: mysqlnd 7.4.33)
• Browser: Chrome 124.0.0.0
• OS: macOS
• Theme: Twenty Twenty-Four 1.0
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.1.0

Steps to Reproduce

Actual Results

1. ✅ The PR is working like expected result.

[naeemhaque]

Test report #60719 by @naeemhaque

[iamfarhan09]

Ticket #60719 @iamfarhan09

[imasikur22]

Bug Report

Description

According to this report, the patch indicated works as expected.
PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260

Environment

• WordPress: 6.6-alpha-57778-src
• PHP: 8.2.18
• Server: nginx/1.25.5
• Database: mysqli (Server: 8.0.37 / Client: mysqlnd 8.2.18)
• Browser: Chrome 124.0.0.0
• OS: macOS
• Theme: Twenty Twenty-Four 1.0
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.1.0

Expected Results

1. ✅ The PR is working like expected result.

Additional Notes

• The result is working fine but the status is showing "Loading..."

[imasikur22]

Test report #60719 by @ imasikur22

[tofajjal02]

Bug Report

Description

According to this report, the patch indicated works as expected.

PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260

Environment

• WordPress: 6.6-alpha-57778-src
• PHP: 8.2.18
• Server: nginx/1.25.5
• Database: mysqli (Server: 8.0.37 / Client: mysqlnd 8.2.18)
• Browser: Chrome 124.0.0.0
• OS: macOS
• Theme: Twenty Twenty-Four 1.0
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.1.0

Actual Results

1. ✅ The pr working is final as a expected result

[tofajjal02]

Ticket #60719 @tofajjal02

[sarkarripon]

Bug Report

Description

According to this report, the patch indicated works as expected.
PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260

Environment

• WordPress: 6.6-alpha-57778-src
• PHP: 8.2.18
• Server: nginx/1.25.5
• Database: mysqli (Server: 8.0.37 / Client: mysqlnd 8.2.18)
• Browser: Chrome 124.0.0.0
• OS: macOS
• Theme: Twenty Twenty-Four 1.0
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.1.0

Actual Results

1. ✅ PR worked fine from my end

Supplemental Artifacts

Add Inline:

[prottoysarkar]

Bug Report

Description

According to this report, the patch described works as expected.

PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260

Environment

WordPress: 6.6-alpha-57778-src
PHP: 7.4.33
Server: nginx/1.25.1
Database: mysqli (Server: 8.0.37 / Client: mysqlnd 7.4.33)
Browser: Chrome 124.0.0.0
OS: macOS
Theme: Twenty Twenty-Four 1.0
MU Plugins: None activated
Plugins:
Test Reports 1.1.0

Actual Results

✅ I tested the changes with the given PR and they work as expected.

[prottoysarkar]

Ticket #60719 @prottoysarkar

[zunaid321]

Bug Report

Description

This report validates whether the indicated patch works as expected.
PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260

Environment

• WordPress: 6.6-alpha-57778-src
• PHP: 8.2.12
• Server: nginx/1.25.3
• Database: mysqli (Server: 8.0.36 / Client: mysqlnd 8.2.12)
• Browser: Chrome 124.0.0.0
• OS: Windows 10/11
• Theme: Twenty Twenty-Four 1.0
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.1.0

Expected Results

1. ✅ PR worked fine but the status was stuck at "loading".

Supplemental Artifacts

Screenshot:

[imranhasanraaz]

Test Report
Description
According to this report, the patch described works as expected.
PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260

Environment

• WordPress: 6.6-alpha-57778-src
• PHP: 8.2.19
• Server: nginx/1.25.5
• Database: mysqli (Server: 8.0.37 / Client: mysqlnd 8.2.19)
• Browser: Chrome 124.0.0.0
• OS: Windows 10/11
• Theme: Twenty Twenty-One 2.2
• MU Plugins: None activated
• Plugins:
  • Hello Dolly 1.7.2
  • Test Reports 1.1.0

Actual Results
✅ I tested the changes with the given PR and they work as expected.
Screenshot:

[rajinsharwar]

Tested changes with mentioned the PR and it shows the font dir path and size to Site Health.
PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260
Environment
WordPress: 6.6
PHP: 8.1.23
Server: nginx
Database: mysqli
OS: Windows

✅ The font directory is showing correctly.

As this ticket has an adequate number of test reports, marking this for 'commit'.

[nazmul111]

Test Report

Description

This report validates whether the indicated patch works as expected.
PR tested: ​https://github.com/WordPress/wordpress-develop/pull/6260

Environment

• WordPress: 6.6-alpha-57778-src
• PHP: 8.2.19
• Server: nginx/1.25.5
• Database: mysqli (Server: 8.0.37 / Client: mysqlnd 8.2.19)
• Browser: Chrome 125.0.0.0
• OS: Windows 10/11
• Theme: Twenty Twenty-Four 1.0
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.1.0

Expected Results

1. ✅ PR worked fine but the status was stuck at "loading".

[nazmul111]

After Applying this patch for #60719

[audrasjb]

Works fine

[audrasjb]

Thanks everyone for testing 😅

The PR works fine on my side as well.
Self assigning for commit.

I committed the changes suggested by @peterwilsoncc directly to the PR.

[audrasjb]

In 58299:

Site Health: Add fonts upload location to Site Health report.

Just like Site Health lists the paths to the plugins/themes/uploads directories, this changeset adds the path to the fonts directory (and its size).

Props swissspidy, andr3ribeiro, krupajnanda, ironprogrammer, iamfarhan09, naeemhaque, imasikur22, tofajjal02, sarkarripon, prottoysarkar, zunaid321, imranhasanraaz, rajinsharwar, nazmul111, audrasjb, peterwilsoncc.
Fixes #60719.

Committed in https://core.trac.wordpress.org/changeset/58299

[audrasjb]

@ironprogrammer I committed the current PR without the change you suggested, to make sure this enhancement can ship in time for 6.6 beta 1. We can either reopen this ticket for a follow-up patch or open a new one.

[ironprogrammer]

Replying to audrasjb:

@ironprogrammer I committed the current PR without the change you suggested, to make sure this enhancement can ship in time for 6.6 beta 1. We can either reopen this ticket for a follow-up patch or open a new one.

Thanks, @audrasjb! I'll create a PR with the follow-up patch shortly (I've got it stashed somewhere).

Follow-up to ​#6260.

Trac ticket: https://core.trac.wordpress.org/ticket/60719

[audrasjb]

In 58310:

Site Health: Add a wp_is_writable() for fonts directory.

This changeset adds a check in Site Health to display whether the fonts directory is writable or not.

Follow-up to [58299].

Props ironprogrammer.
Fixes #60719.

committed in https://core.trac.wordpress.org/changeset/58310

[desrosj]

In 58408:

Coding Standards: Apply changes after running composer format.

This applies several formatting related changes made while running composer format.

Follow up to [55720], [58171], [58271], [58282], [58283], [58292], [58299], [58303], [58332].
See #51857, #60719, #60895, #61021, #61118, #61228, #61276, #61324.