Font Library: Support alternate paths for fonts (WP_FONTS_DIR
)
#55063
Labels
[Feature] Typography
Font and typography-related issues and PRs
[Status] In Progress
Tracking issues with work in progress
[Type] Bug
An existing feature does not function as intended
What problem does this address?
For sites hosted on webhosts with immutable filesystems, installing fonts into
wp-content
is not a straightforward process unless those files are committed to an environment without those file write restrictions and deployed upstream. Providing a constant (or a filter) where a safe path can be defined allows users (or hosts) to be able to install fonts natively as intended without running into filesystem permission issues.What is your proposed solution?
Introducing a constant, e.g.
WP_FONTS_DIR
which, likeWP_CONTENT_DIR
orWP_UPLOADS_DIR
, allows a user to explicitly define an alternate path to installed fonts which is used instead of the default path (wp-content/fonts
).The text was updated successfully, but these errors were encountered: