Skip to content

Releases: chrmrtns/safefonts

SafeFonts Free v1.1.9 - CSS Variables & CSS Reference

14 Nov 07:24
@chrmrtns chrmrtns
v1.1.9
be78a96

Choose a tag to compare

View all tags
SafeFonts Free v1.1.9 - CSS Variables & CSS Reference Latest
Latest

🎯 New Features

  • CSS Variables Support - All fonts now generate CSS variables in the format --safefonts-{slug}
  • CSS Reference Page - New admin page with comprehensive documentation for CSS variables, Gutenberg classes, and implementation details
  • Manual Builder Integration - Use CSS variables with any builder or theme supporting CSS custom properties (Builderius, Bricks, Oxygen, etc.)

🐛 Bug Fixes

  • Auto-regeneration - Now works correctly for both single plugin updates and bulk updates
  • CSS regeneration hook - Properly detects updates from all update methods

📖 Documentation

  • Updated README with CSS variables feature
  • Updated requirements to WordPress 6.2+
  • Complete CSS implementation documentation in new CSS Reference page

💡 Usage

After updating, visit SafeFonts → CSS Reference to see all your CSS variables and copy them for use in custom CSS or builder typography fields.

Example: font-family: var(--safefonts-your-font-slug);

🔗 Links

Assets 2
Loading

SafeFonts v1.1.0 - Family Folder Organization & WordPress.org Compliance

29 Oct 09:58
@chrmrtns chrmrtns
v1.1.0
9f0f9a8

Choose a tag to compare

View all tags
SafeFonts v1.1.0 - Family Folder Organization & WordPress.org Compliance

🎉 SafeFonts v1.1.0 Released

This release brings improved font organization, WordPress.org compliance updates, and important coding standards fixes.

🆕 New Features

Font Family Folder Organization

  • Hierarchical Storage: Fonts are now organized in dedicated family folders (e.g., /roboto/, /open-sans/)
  • New Database Column: Added family_slug column for faster family-based queries
  • Automatic Migration: Existing fonts are seamlessly moved to family folders on plugin update
  • Smart Cleanup: Empty family folders are automatically removed when the last font is deleted

🔧 Improvements

WordPress.org Compliance

  • Marketing Claims Removed: Updated language to be factual and guideline-compliant
  • GDPR Wording Refined: Now matches industry standards (Borlabs/Complianz pattern)
  • Better Descriptions: More action-oriented, clearer explanations
  • "Getting Google Fonts" Section: Added prominent section with accurate download sources

User Interface

  • Badge Colors: Font weight badge now uses yellow instead of red to avoid confusion with delete button
  • File Path Handling: Relative paths now include family folder structure

WordPress Coding Standards

  • WP_Filesystem API: Replaced rename() with WP_Filesystem::move() for file operations
  • Proper Initialization: Added correct WP_Filesystem initialization in migration function
  • Standards Compliant: Passes WordPress.WP.AlternativeFunctions coding standard

📋 Technical Details

Database Changes

  • Schema version bump for migration support
  • New family_slug column in database table
  • Improved query performance for family-based operations

Migration Process

  • Automatic: Runs seamlessly on plugin activation/update
  • Safe: Only migrates fonts that need it (checks for / in file path)
  • Idempotent: Can run multiple times without issues
  • Preserves Data: Updates database paths after successful file moves

📁 File Structure Changes

Before (v1.0.9):

/wp-content/uploads/safefonts/
├── roboto-regular-400.woff2
├── roboto-bold-700.woff2
├── open-sans-regular-400.woff2
└── open-sans-italic-400.woff2

After (v1.1.0):

/wp-content/uploads/safefonts/
├── roboto/
│   ├── roboto-regular-400.woff2
│   └── roboto-bold-700.woff2
└── open-sans/
    ├── open-sans-regular-400.woff2
    └── open-sans-italic-400.woff2

🔗 Resources

Download Google Fonts

Documentation

⚠️ Upgrade Notice

Automatic Migration: When you update to v1.1.0, existing fonts will be automatically moved to family folders. This is a one-time operation that happens seamlessly during plugin activation.

No Action Required: The migration is fully automatic and safe. Your fonts will continue to work without any configuration changes.

Backup Recommended: As with any plugin update, we recommend backing up your database before updating (though the migration is designed to be safe and reversible).

📊 Compatibility

  • WordPress: 5.0+
  • PHP: 7.4+
  • Tested up to: WordPress 6.8
  • Gutenberg: Full integration
  • WordPress 6.5+ Font Library: Supported

🙏 Thank You

Thank you for using SafeFonts! This release makes the plugin more organized, compliant with WordPress.org standards, and ready for wider distribution.

If you encounter any issues with the migration or have suggestions for future releases, please open an issue on GitHub.

Full Changelog: https://github.com/chrmrtns/safefonts/blob/main/readme.txt

Loading

SafeFonts v1.0.9

22 Oct 19:48
@chrmrtns chrmrtns
v1.0.9
7b850fa

Choose a tag to compare

View all tags
SafeFonts v1.0.9

SafeFonts v1.0.9

Secure, GDPR-compliant font management for WordPress with seamless Gutenberg integration.

🎉 What's New

Improvements

  • ✨ CSS Tab Navigation - Help & Documentation page now uses clean CSS tabs for better organization
  • 🎨 Purple Branding - Consistent purple color scheme throughout admin interface
  • 🌍 Translation Ready - Full i18n support with POT file included

Fixes

  • 🔧 Removed manual load_plugin_textdomain() per WordPress.org guidelines
  • 📝 WordPress.org compliance improvements

Technical

  • CSS-only tabs (no JavaScript required)
  • Full internationalization support
  • Cleaner tabbed interface without long scrolling pages

🚀 Features

  • 🔒 GDPR Compliant - 100% local font hosting, no external requests
  • ✨ Gutenberg Integration - Fonts automatically appear in block editor
  • 🎨 WordPress 6.5+ Font Library - Full Site Editor integration
  • 🛡️ Secure Upload Validation - Magic byte verification, MIME type checking
  • ⚡ Font Preloading - Reduce FOIT for better performance
  • 📱 Responsive Admin - Modern, clean interface

📋 Requirements

  • WordPress 5.0+
  • PHP 7.4+

🎯 Supported Font Formats

  • WOFF2 (recommended)
  • WOFF
  • TTF
  • OTF

📦 Installation

  1. Download safefonts-1.0.9.zip from this release
  2. Go to WordPress Admin → Plugins → Add New → Upload Plugin
  3. Upload the zip file and activate
  4. Go to SafeFonts menu to start uploading fonts

🆙 Upgrade to Pro

Want page builder integration? SafeFonts Pro includes:

  • Elementor, Bricks, Beaver Builder, Divi, Oxygen support
  • Bulk ZIP import
  • Priority support

🐛 Support

Full Changelog: https://github.com/chrmrtns/safefonts/blob/main/readme.txt

Loading