Title: Fatal PHP Error error
Last modified: August 21, 2016

---

# Fatal PHP Error error

 *  Resolved [NanoWisdoms](https://wordpress.org/support/users/nanowisdoms/)
 * (@nanowisdoms)
 * [12 years, 7 months ago](https://wordpress.org/support/topic/fatal-php-error-error/)
 * Great plugin, but I’m getting the following errors reported
 * [15-Oct-2013 21:29:06] PHP Fatal error: Class ‘Gc_MessageBar_Service_Locator’
   not found in /home4/nanowisd/public_html/nwblog/wp-content/plugins/gc-message-
   bar/init-options.php on line 6
    [15-Oct-2013 21:30:39] PHP Fatal error: Class‘
   Gc_MessageBar_Service_Locator’ not found in /home4/nanowisd/public_html/nwblog/
   wp-content/plugins/gc-message-bar/init-options.php on line 6
 * I’m using version 2.1.5.
 * Any suggestions?
 * [http://wordpress.org/plugins/gc-message-bar/](http://wordpress.org/plugins/gc-message-bar/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [GetConversion](https://wordpress.org/support/users/getconversion/)
 * (@getconversion)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/fatal-php-error-error/#post-4224620)
 * After you update to 2.2.1 the issue has to disappear. If not, please return to
   me.

Viewing 1 replies (of 1 total)

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

 * ![](https://s.w.org/plugins/geopattern-icon/gc-message-bar_bd9878.svg)
 * [GC Message Bar](https://wordpress.org/plugins/gc-message-bar/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/gc-message-bar/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/gc-message-bar/)
 * [Active Topics](https://wordpress.org/support/plugin/gc-message-bar/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/gc-message-bar/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/gc-message-bar/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [GetConversion](https://wordpress.org/support/users/getconversion/)
 * Last activity: [12 years, 6 months ago](https://wordpress.org/support/topic/fatal-php-error-error/#post-4224620)
 * Status: resolved