-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Font Library: Support alternate paths for fonts (WP_FONTS_DIR
)
#55063
Comments
For context, the hosting discussion that led to this ticket being opened) happened in Make/Core slack in the Providing the constant suggested in this ticket makes sense, to unblock web hosts supporting it. As @jazzsequence noted in the slack thread:
IMO this needs to be done as part of the introduction of the Font Library into Core. cc @matiasbenedetto @azaozz |
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: