Back to Community
Home / Community / Plugin → Maintenance

Troubleshooting Font Issues in the Maintenance Plugin

18 threads Sep 9, 2025 Plugin → Maintenance

Content

Many users of the popular Maintenance plugin for WordPress encounter issues related to fonts. These problems can range from fonts not displaying correctly to compliance and performance concerns. This guide compiles the most common font-related issues and their solutions, based on community discussions and official responses.

Common Font Issues and Their Solutions

1. Google Fonts Not Displaying Correctly for Non-Latin Scripts

The Problem: Users have reported that text in Cyrillic, Greek, or other non-Latin scripts does not render correctly when using a Google Font. The text may fall back to a default font in browsers like Firefox or IE, while working in Chrome.

The Reason: Historically, the plugin loaded only the basic Latin character subset for Google Fonts to optimize performance. This meant it lacked the glyphs required for other writing systems.

The Solution: The Maintenance team has worked to add support for extended character sets like latin-ext and cyrillic in newer versions. Ensure your plugin is updated to the latest version. If the problem persists in an updated plugin, it may be a bug that should be reported.

2. Avoiding External Fonts for GDPR Compliance

The Problem: Loading fonts from external servers like Google Fonts or Bunny Fonts can create privacy and GDPR compliance issues for sites with European visitors.

The Reason: The plugin's default behavior is to load selected Google Fonts from Google's servers.

The Solution: The simplest solution is to select a "standard" font. At the top of the font dropdown menu in the plugin's settings, you will find a list of common web-safe fonts (e.g., Arial, Helvetica, Georgia). Choosing one of these will prevent any external network requests for fonts, keeping your site compliant. Note: Some users have reported the plugin loading Bunny Fonts even when not selected; the Maintenance team has acknowledged this as a bug to be fixed in a future update.

3. Customizing Font Sizes and Styles

The Problem: Users often find the default font sizes too large or too small for their maintenance page design.

The Solution: You can easily override the default styles using the "Custom CSS" box in the plugin's settings. For example, to change the headline and description text, you can use the following CSS:

.site-content h2 {
    font-size: 5em;
}
.site-content h3.description {
    font-size: 1.5em;
    line-height: 1.5em;
}

Use your browser's inspector tool to identify the correct CSS selectors for the elements you wish to style.

4. Missing or Outdated Google Fonts List

The Problem: The list of available Google Fonts within the plugin is not exhaustive and may be missing newer fonts.

The Reason: The list is hard-coded into the plugin and requires manual updates by the developers.

The Solution: The Maintenance team has added specific fonts like Martel Sans upon user request in past updates. To request a new font be added, you can report it as a suggestion. For immediate needs, you may need to use a standard font or utilize the Custom CSS option to manually assign a font family, though this will not handle loading the font file itself.

5. Using Third-Party Font Services (Adobe Fonts, Typekit)

The Problem: The plugin does not natively support integrating fonts from services like Adobe Fonts or Typekit.

The Reason: The plugin's architecture is designed around its built-in font options. Adding @import or <link> code for other services via the Custom CSS field is not possible for technical and security reasons.

The Solution: Official responses indicate that integrating these services requires source code modifications, which is outside the scope of the free plugin's support. This typically requires custom development work.

6. Font Conflicts with Themes

The Problem: In rare cases, a function name conflict between the plugin and your theme can cause a fatal error, breaking your site.

The Reason: This happens if both the theme and the plugin declare a function with the same name (e.g., add_google_fonts()).

The Solution: The Maintenance team has addressed this in the past by renaming their functions to avoid conflicts. If you encounter this, ensure your plugin is updated to the latest version. If the issue persists in the latest version, it should be reported as a new bug.

Conclusion

Most font issues with the Maintenance plugin can be resolved by selecting a standard font for compliance, using the Custom CSS field for styling, and ensuring you are running the latest version of the plugin to benefit from the most recent fixes and font additions. For more complex issues, like adding entirely new font services, custom coding is unfortunately required.

Related Support Threads Support