PFont
| 开发者 | wordpress-parsi |
|---|---|
| 更新时间 | 2026年10月12日 07:29 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
PFont keeps one central font library and adds those fonts to the native font dropdowns of the editors and builders you already use. It only uses documented, verified hooks and never edits core, theme or builder files.
What it does
- Upload WOFF2, WOFF, TTF and OTF files. Every file is checked by its real contents (magic bytes), not only by its name.
- Add Google Fonts from the CDN (Google or the privacy-friendlier Bunny Fonts), or download them to your own server with one click.
- Ships five Persian/Arabic presets you can add in one click: Vazirmatn, Estedad, Parastoo, Lalezar and Markazi Text (all SIL Open Font License). Nothing is enabled automatically.
- Loads a font only on pages that actually use it. Pages without custom fonts get no extra CSS, requests or JavaScript.
- WOFF2 first,
font-display: swapby default, preconnect only when a CDN font is used. - Honest integration status screen: every integration shows Active, Limited, Unsupported or Not detected, with the reason.
- A searchable library that previews every font in your own text, in Persian or Latin, at any size.
- A type tester for each font: weight, italic, size, line height, alignment and right-to-left, plus a size waterfall, the character set and copyable CSS.
- Optional: use one of your fonts for the WordPress admin area (Settings → WordPress admin). Icons, code fields and the content you edit keep their own fonts.
- Classic Editor (TinyMCE): font dropdown, fonts preview inside the editor.
- Block Editor: fonts appear in Typography → Font for every block and in Global Styles. Theme fonts are kept (the list is appended, not replaced).
- Elementor: own "PFont" group in every typography control. Elementor's own Google entries are never overwritten by CDN copies.
- Astra: fonts appear in the Customizer typography controls. Local fonts are never sent to Google.
- Kadence: fonts appear in the Customizer. GeneratePress: type the family name in its Font Manager; the plugin loads the files.
安装:
- Upload the plugin ZIP under Plugins → Add New → Upload Plugin, then activate it.
- Open Settings → PFont.
- Add one of the available fonts on the Library screen, or upload your own under "Add new font".
- Choose where each font should appear in the library table, then pick the font in your editor or builder.
常见问题:
Why is a font I added from Google not in Elementor's "PFont" group?
Elementor already ships many Google Fonts (including Vazirmatn, Lalezar and Markazi Text). A CDN copy would only duplicate it, so the plugin leaves Elementor's own entry in place and Elementor loads it. If you host the font on your server or upload it, the plugin takes over that entry so Elementor stops requesting it from Google.
Does it slow my site down?
No global CSS is added. Each page gets at most one small inline style block with the @font-face rules it needs, plus a CDN stylesheet only if a CDN font is used on that page.
Which file format should I upload?
WOFF2. It is the smallest format and supported by all current browsers.
Can I change the font of the WordPress admin area?
Yes. Under Settings → WordPress admin, choose any enabled font from your library. It is applied to the dashboard screens and the admin toolbar. Icons, code fields and the content you edit keep their own fonts. The login page, the Customizer and the toolbar on the front end are not changed. If the font loads from a CDN it is requested on every admin screen, so hosting it on your server is the better choice.
Why is there no Divi or WoodMart integration?
Both already include a custom font upload of their own, so a second layer is not needed. Upload the font in Divi (the Upload button inside any font menu) or in WoodMart (Theme Settings → Typography → Custom fonts). Version 1.2.0 removed the earlier Divi and WoodMart support. Fonts and settings you saved are kept; Media Library copies made by the old WoodMart helper are not deleted, so WoodMart keeps working.
What happens to my fonts when I delete the plugin?
Nothing, unless you enabled the uninstall options under Settings. Font files and settings are kept by default.
Can I add fonts from code?
Yes. Use the pfont_registered_fonts filter to add font records, pfont_cdn_presets to change the preset list and pfont_integrations to add or replace an integration adapter. Every hook is documented in the source with a docblock.
更新日志:
1.5.0
- Removed the "Custom stylesheet URL" field. Loading a stylesheet from an arbitrary address is not allowed in the plugin directory. Fonts come from Google Fonts or Bunny Fonts, are hosted on your server, or are uploaded. A font that was saved with a custom URL is kept but disabled; open it and choose a Google font or upload its files.
- Security: every form value is sanitized the moment it is read, before validation, and only the sanitized copy is kept when a save fails.
- Every option, transient, form field, nonce, action, CSS class and script handle now uses the
pfontprefix. Saved fonts and settings are moved to the new option names automatically on the first request after the update. - Removed the deprecated
ucf_*hook names that 1.4.0 still fired next to thepfont_*ones. Only thepfont_*hooks remain. - Block Editor: the font preset slug is now
pfont-{id}instead ofucf-{id}. Fonts picked in the Block Editor before this update must be picked again in the block or in Styles.
- Plugin Check: all reported errors and warnings fixed.
- Developers: hooks, global functions and constants now use the
pfont_/PFONT_prefix, because WordPress.org asks for a prefix of at least four characters. The old hook names still worked in this version and showed a deprecation notice. - Removed the
load_plugin_textdomain()call. WordPress loads the translations by itself. - Replaced
array_is_list()with an own helper, so the plugin keeps working with "Requires at least: 6.4". - The development file
phpcs.xml.distis nowphpcs.xml(".dist" files are not allowed in the plugin directory).
- Library: when the library is empty, the Persian and Arabic fonts are shown first and the upload card below them.
- "Add font" is now "Add new font" (sidebar and page title) and "Upload files" is now "Upload custom font".
- Add/Edit font: the font details and its files (or weights and styles) are one section instead of two.
- Fixed: a PHP warning ("Undefined array key files") when adding a new uploaded font. On servers that display errors it could stop the redirect after saving.
- The plugin is now called PFont. Only the name changed: your fonts, settings, files and the fonts already chosen in your content are untouched.
- Buttons, switches, checkboxes, radio buttons, chips and sliders now use your WordPress admin colour scheme (Users → Profile → Admin Color Scheme) instead of black.
- Library: the "Add font" button next to the page title was removed. "Add font" stays in the sidebar.
- Elementor: the font group is now labelled "PFont".
- New: choose a library font for the WordPress admin area under Settings → WordPress admin.
- Fixed: on themes with their own fonts (for example Twenty Twenty-Five), the theme's fonts were replaced by one nameless entry. Fonts were missing from the Block Editor font list and Appearance → Fonts stopped with "Something went wrong" (can't access property "localeCompare", name is undefined). Theme fonts are now kept and your fonts are appended.
- Fixed: CDN fonts were loaded inside the Block Editor canvas but not on the editor screen around it.
- Removed: Divi 4, Divi 5 and WoodMart support. Both products include their own custom font upload. Saved fonts are not affected.
- Readme: new "External services" section.
- New admin interface: sidebar navigation, card-based settings with switches, and a Help page.
- Library: live search, your own preview text, Persian/Latin samples and a size slider; switches save instantly.
- New font page with a type tester, size waterfall, character set, details and where the font appears.
- Integrations: platforms that are not installed no longer show font counts; Astra, Divi and WoodMart sites no longer see a misleading "Unsupported" Customizer entry.
- Copy buttons fall back gracefully when the browser refuses clipboard access.
- First release.