Title: Uncaught TypeError…
Last modified: December 29, 2016

---

# Uncaught TypeError…

 *  [rishnak](https://wordpress.org/support/users/rishnak/)
 * (@rishnak)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/uncaught-typeerror-14/)
 * Hello,
 * I keep getting this error in the chrome console after enabling Jetpack:
 * Uncaught TypeError: Cannot read property ‘type’ of undefined
    at o.h [as ready](
   bootstrap d85f1be…:formatted:46) at o.<anonymous> (bootstrap d85f1be…:formatted:
   46) at bootstrap d85f1be…:formatted:46 at XMLHttpRequest.n (bootstrap d85f1be…:
   formatted:46) at h (bootstrap d85f1be…:formatted:46) at d (bootstrap d85f1be…:
   formatted:46)
 * Any solutions?
 * br,
    Rishnak

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

 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [9 years, 7 months ago](https://wordpress.org/support/topic/uncaught-typeerror-14/#post-8639706)
 * Could you add the following to your site’s wp-config.php file?
 *     ```
       define( 'WP_DEBUG', true );
   
       if ( WP_DEBUG ) {
   
               @error_reporting( E_ALL );
               @ini_set( 'log_errors', true );
               @ini_set( 'log_errors_max_len', '0' );
   
               define( 'WP_DEBUG_LOG', true );
               define( 'WP_DEBUG_DISPLAY', false );
               define( 'CONCATENATE_SCRIPTS', false );
               define( 'SAVEQUERIES', true );
   
       }
       ```
   
 * Your `wp-config.php` file may already include a line that says “define(‘WP_DEBUG’,
   false);”. You can remove it, and replace it by the code above.
 * Once you’ve done so, try to reproduce the error, and check your console again;
   you should have more details about the exact file that’s causing the issue.
 * You can then replace `define('WP_DEBUG', true);` by `define('WP_DEBUG', false);`
   in the code above.
 * Let me know what you find!
 *  Thread Starter [rishnak](https://wordpress.org/support/users/rishnak/)
 * (@rishnak)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/uncaught-typeerror-14/#post-8640046)
 * Ok, I did that, and now it gives this error message in the console, looks about
   the same to me…
 * The concanated link is:
    [https://widgets.wp.com/notifications/webpack:/webpack/bootstrap](https://widgets.wp.com/notifications/webpack:/webpack/bootstrap)
   d85f1beecde5aa35f824
 * Uncaught TypeError: Cannot read property ‘type’ of undefined
    at o.h [as ready](
   bootstrap d85f1be…:32) at o.<anonymous> (bootstrap d85f1be…:32) at bootstrap 
   d85f1be…:9 at XMLHttpRequest.n (bootstrap d85f1be…:16) at h (bootstrap d85f1be…:
   16) at d (bootstrap d85f1be…:16)
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [9 years, 7 months ago](https://wordpress.org/support/topic/uncaught-typeerror-14/#post-8643840)
 * Thank you, that link is helpful. It would seem that the problem is linked to 
   the Notifications module.
 * I can’t seem to be able to reproduce this issue on my end. Would you mind contacting
   us via [this form](http://jetpack.com/contact-support/) and mention this thread?
   I’d like to run some tests with you on your site to try to understand what’s 
   happening.
 * Thanks!

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

The topic ‘Uncaught TypeError…’ 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/)

 * 3 replies
 * 2 participants
 * Last reply from: [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * Last activity: [9 years, 7 months ago](https://wordpress.org/support/topic/uncaught-typeerror-14/#post-8643840)
 * Status: not resolved