Title: Fatal error
Last modified: April 2, 2020

---

# Fatal error

 *  Resolved [Argentum](https://wordpress.org/support/users/argentum/)
 * (@argentum)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-3453/)
 * Hi,
    Got a nasty fatal error after I followed the instruction to go to the front
   page and then return and click here.
 * Uncaught Error: Cannot use object of type WP_Error as array in /mysite//public_html/
   dev/wp-content/plugins/host-webfonts-local/includes/class-api.php:53 Stack trace:#
   0 /mysite//public_html/dev/wp-content/plugins/host-webfonts-local/includes/admin/
   class-auto-detect.php(55): OMGF_API->get_font_styles(‘petit-formal-sc…’, ‘latin’)#
   1 /mysite//public_html/dev/wp-content/plugins/host-webfonts-local/includes/admin/
   class-auto-detect.php(38): OMGF_Admin_AutoDetect->init() #2 /mysite//public_html/
   dev/wp-content/plugins/host-webfonts-local/includes/class-omgf.php(98): OMGF_Admin_AutoDetect-
   >__construct(Array) #3 /mysite//public_html/dev/wp-content/plugins/host-webfonts-
   local/includes/class-omgf.php(29): OMGF->do_auto_detect() #4 /mysite//public_html/
   dev/wp-content/plugins/host-webfonts-local/host-webfonts-local.php(78): OMGF-
   >__construct() #5 /mysite//public_html/dev/wp-content/plugins/host-webfonts-local/
   host-webfonts-local.php(84): omgf_init() #6 /mysite//public_html/ in /mysite//
   public_html/dev/wp-content/plugins/host-webfonts-local/includes/class-api.php
   on line 53
 * Looks bad! 😉
    Should I

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [Daan van den Bergh](https://wordpress.org/support/users/daanvandenbergh/)
 * (@daanvandenbergh)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-3453/#post-12615548)
 * Aiii, you’re right. Looks bad 😉
 * I didn’t add error handling there. Which explains the Fatal Error. I’ve released
   an to fix the fatal error and return a readable error.
 * It won’t fix anything for you, though. Seems to be a bug in the Google Fonts 
   Helper API. The request to [https://google-webfonts-helper.herokuapp.com/fonts/petit-formal-script?subsets=latin](https://google-webfonts-helper.herokuapp.com/fonts/petit-formal-script?subsets=latin)
   returns a 503 error.
 * I posted an issue to the developer, hopefully he’ll respond.
 *  Thread Starter [Argentum](https://wordpress.org/support/users/argentum/)
 * (@argentum)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-3453/#post-12615892)
 * Yep, almost like a white page of horror! 🙂
 * I am using a Google Font named Formal Petit Script, but only in pages made with
   Elementor. I can’t get the plugin to find that font. Poppins is good, used everywhere.
   Could Elementor have something to do with it?
 *  Plugin Author [Daan van den Bergh](https://wordpress.org/support/users/daanvandenbergh/)
 * (@daanvandenbergh)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-3453/#post-12615920)
 * Yes, I know. Formal Petit Script returns an error in the Google Fonts Helper 
   API.
 * Like I said, I posted an issue to the developer of the API, hopefully he’ll respond.
   I hope it’s a temporary thing.
 * The latest update in OMGF makes sure you get a readable error, instead of a ‘
   white page of horror’ 😉
 *  Thread Starter [Argentum](https://wordpress.org/support/users/argentum/)
 * (@argentum)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-3453/#post-12616123)
 * Aye, I know it was the Formal Petit Script too. But I realised that that font
   is used in Elementor pages, after I posted the topic, and that perhaps the developer
   of the API would benefit in knowing that?
 *  Plugin Author [Daan van den Bergh](https://wordpress.org/support/users/daanvandenbergh/)
 * (@daanvandenbergh)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-3453/#post-12616132)
 * Oh boy, seems like $#!T has hit the fan there: [https://github.com/majodev/google-webfonts-helper/issues/99](https://github.com/majodev/google-webfonts-helper/issues/99)

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Fatal error’ is closed to new replies.

 * ![](https://ps.w.org/host-webfonts-local/assets/icon-256x256.png?rev=3300821)
 * [OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.](https://wordpress.org/plugins/host-webfonts-local/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/host-webfonts-local/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/host-webfonts-local/)
 * [Active Topics](https://wordpress.org/support/plugin/host-webfonts-local/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/host-webfonts-local/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/host-webfonts-local/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Daan van den Bergh](https://wordpress.org/support/users/daanvandenbergh/)
 * Last activity: [6 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-3453/#post-12616132)
 * Status: resolved