BugWP logo BugWP
Back to Community
Home / Community / Plugin → Omgf | gdpr/dsgvo compliant, faster google fonts. easy.

Troubleshooting Common OMGF Plugin Errors: A Guide to Fixes and Workarounds

30 threads Sep 7, 2025 Plugin → Omgf | gdpr/dsgvo compliant, faster google fonts. easy.

Content

Users of the 'OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.' plugin occasionally encounter errors that can disrupt their website's functionality. Based on community reports and resolutions, this guide outlines the most common errors, their likely causes, and the steps you can take to resolve them.

1. PHP Version Compatibility and Deprecation Errors

Error Example: implode(): Passing glue string after array is deprecated.

Why it happens: This error occurs when running an older version of the OMGF plugin on a newer PHP version (e.g., PHP 7.4+) that has deprecated certain functions.

Solution: The most straightforward fix is to update the OMGF plugin to the latest version. The development team frequently addresses PHP compatibility issues in new releases.

2. Fatal Errors During Optimization (Save & Optimize)

Error Examples:

  • Uncaught TypeError: ucfirst(): Argument #1 ($string) must be of type string, array given
  • Uncaught ArgumentCountError: array_intersect() expects at least 1 argument, 0 given

Why it happens: These are bugs within the plugin's optimization logic, often triggered by specific, sometimes unexpected, data configurations when the "Save & Optimize" or "Refresh Cache" button is clicked.

Solution: These specific errors have been patched in subsequent plugin updates. Ensure your plugin is updated to the latest version. If the error persists after updating, try clearing OMGF's cache from its settings and then attempt the optimization process again.

3. Output Buffering Conflicts

Error Example: PHP Fatal error: print_r(): Cannot use output buffering in output buffering display handlers

Why it happens: This error indicates a conflict with how the plugin handles output buffering, particularly in environments where other plugins or themes are also manipulating output buffers (common on multisite installations or with page builders).

Solution: A fix for this was included in a beta release and later in a stable update. Updating OMGF should resolve it. If you are using a caching plugin, clear its cache after updating OMGF.

4. Cache-Related Issues and 400 Errors

Error Example: Error: 400 – File exists, but is 0 bytes in size. Is allow_url_fopen enabled on your server?

Why it happens: This can happen if a file wasn't downloaded correctly into OMGF's cache directory, often due to a temporary server issue during the initial optimization.

Solution:

  1. First, confirm that allow_url_fopen</code is enabled on your server. Your hosting provider can help with this.
  2. Navigate to OMGF's settings and use the option to delete its local cache files.
  3. Run the optimization process again to re-download the font files.
  4. Clear your browser cache before testing.

5. Class Not Found & Function Errors After Update

Error Examples:

  • Uncaught Error: Class 'OMGF_Admin_Settings_Builder' not found
  • Fatal error: Uncaught Error: Call to undefined function omgf_init()

Why it happens: Major updates sometimes refactor code, renaming or removing classes and functions. If a server-level opcache or object caching does not clear its stored code after the update, it will try to call the old, now non-existent code.

Solution: After any plugin update, it is a best practice to flush all caching layers. This includes:

  • Your WordPress caching plugin (e.g., WP Rocket, W3 Total Cache).
  • Server-level OPcache or Object Caching (e.g., Redis, Memcached). You may need to contact your hosting provider for assistance with this.
  • Your browser cache.

6. PHP Notices and Warnings

Error Example: PHP Notice: Undefined index: _wpnonce or PHP Notice: Undefined offset

Why it happens: These are not fatal errors but notices that appear when WP_DEBUG is enabled. They point to minor issues in the code, such as checking for a variable that hasn't been set yet.

Solution: The development team is typically very responsive to these reports and often releases minor updates to squash these notices. Keeping the plugin updated will usually resolve them.

General Troubleshooting Steps

If you encounter an error not listed above, follow these general steps:

  1. Update: Always ensure both WordPress and the OMGF plugin are updated to their latest versions.
  2. Clear Caches: Flush all caching layers—WordPress, browser, server (OPcache, Redis), and CDN.
  3. Check PHP Version: Confirm your server is running a PHP version that is compatible with your version of OMGF (generally PHP 7.4 or higher).
  4. Conflict Test: Temporarily switch to a default WordPress theme (like Twenty Twenty-Four) and disable all other plugins. If the error disappears, re-enable them one-by-one to identify the conflict.

Many errors are resolved quickly by the 'OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.' team through updates. Checking the plugin's changelog can often confirm if a fix for your specific issue has been released.

Related Support Threads Support