Title: PHP Fatal Error
Last modified: July 24, 2018

---

# PHP Fatal Error

 *  Resolved [Daniel Proczko](https://wordpress.org/support/users/diggler/)
 * (@diggler)
 * [7 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-143/)
 * I encountered a PHP Fatal error indicating the jetpack plugin:
    [Tue Jul 24 19:
   55:06.068630 2018] [:error] [pid 19318] [client 194.187.170.101:13302] PHP Fatal
   error: Class ‘Jetpack_Simple_Payments’ not found in /nas/content/live/newmindgroup/
   wp-content/plugins/jetpack/modules/widgets/simple-payments.php on line 479
 * *At this moment I’ve disabled the plugin.

Viewing 1 replies (of 1 total)

 *  Plugin Support [Fotis](https://wordpress.org/support/users/fstat/)
 * (@fstat)
 * [7 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-143/#post-10525903)
 * Hi there,
 * Please update to the latest Jetpack version (6.3.2) as it fixes a compatibility
   issue with the Simple Payment Widget. You can read more about it here:
 * [https://jetpack.com/2018/07/04/jetpack-6-3-2-simple-payment-fix/](https://jetpack.com/2018/07/04/jetpack-6-3-2-simple-payment-fix/)
 * If this still doesn’t work or you have more questions, just let me know and I’ll
   be happy to help!

Viewing 1 replies (of 1 total)

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

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Fotis](https://wordpress.org/support/users/fstat/)
 * Last activity: [7 years, 9 months ago](https://wordpress.org/support/topic/php-fatal-error-143/#post-10525903)
 * Status: resolved