Logo with Jetpack Wp Debug Error

Asked on September 20, 2015 in Troubleshooting.
Jetpack is installed and Wp_DEBUG is true i got a php error and in logs i got this. is there any solution ?[20-Sep-2015 19:29:47 UTC] PHP Notice:  Undefined index: medium in
C:\wamp\www\wordpress\wp-content\plugins\jetpack\modules\theme-tools\site-logo\inc\functions.php on line 66

 

 

[20-Sep-2015 19:29:47 UTC] PHP Stack trace:

 

 

[20-Sep-2015 19:29:47 UTC] PHP   1. {main}() C:\wamp\www\wordpress\index.php:0

 

 

[20-Sep-2015 19:29:47 UTC] PHP   2. require() C:\wamp\www\wordpress\index.php:17

 

 

[20-Sep-2015 19:29:47 UTC] PHP   3. require_once() C:\wamp\www\wordpress\wp-blog-header.php:16

 

 

[20-Sep-2015 19:29:47 UTC] PHP   4. include() C:\wamp\www\wordpress\wp-includes\template-loader.php:75

 

 

[20-Sep-2015 19:29:47 UTC] PHP   5. get_header() C:\wamp\www\wordpress\wp-content\themes\layerswp\builder.php:11

 

 

[20-Sep-2015 19:29:47 UTC] PHP   6. locate_template() C:\wamp\www\wordpress\wp-includes\general-template.php:45

 

 

[20-Sep-2015 19:29:47 UTC] PHP   7. load_template() C:\wamp\www\wordpress\wp-includes\template.php:514

 

 

[20-Sep-2015 19:29:47 UTC] PHP   8. require_once() C:\wamp\www\wordpress\wp-includes\template.php:555

 

 

[20-Sep-2015 19:29:47 UTC] PHP   9. wp_head() C:\wamp\www\wordpress\wp-content\themes\sohi\header.php:6

 

 

[20-Sep-2015 19:29:47 UTC] PHP  10. do_action() C:\wamp\www\wordpress\wp-includes\general-template.php:2270

 

 

[20-Sep-2015 19:29:47 UTC] PHP  11. call_user_func_array:{C:\wamp\www\wordpress\wp-includes\plugin.php:503}() C:\wamp\www\wordpress\wp-includes\plugin.php:503

 

 

[20-Sep-2015 19:29:47 UTC] PHP  12. jetpack_og_tags() C:\wamp\www\wordpress\wp-includes\plugin.php:503

 

 

[20-Sep-2015 19:29:47 UTC] PHP  13. jetpack_og_get_image() C:\wamp\www\wordpress\wp-content\plugins\jetpack\functions.opengraph.php:111

 

 

[20-Sep-2015 19:29:47 UTC] PHP  14. jetpack_get_site_logo_dimensions() C:\wamp\www\wordpress\wp-content\plugins\jetpack\functions.opengraph.php:250

 

 

[20-Sep-2015 19:29:47 UTC] PHP Notice:  Undefined index: medium in C:\wamp\www\wordpress\wp-content\plugins\jetpack\modules\theme-tools\site-logo\inc\functions.php on line 67

 

 

[20-Sep-2015 19:29:47 UTC] PHP Stack trace:
Reply
  • Possible Answers to Your Question:

  • 2 Answer(s)
    Answered on September 22, 2015.

    Hi there,
    That is a jetpack error- I assume they are aware of it and will resolve it through an update. Note that when you have debug on, you will see debug errors and messages. Always have debug disabled on a live site.

    Thanks Vail 🙂

    on September 22, 2015.

    I’ve understood the jetpack WP URL with virtually all statement I’ve ever left finished the plugin. I currently have it dynamic on my site animation services and I don’t think I’ve forwarded a comment without seeing it.

    on April 24, 2019.
    Reply
    Answered on December 7, 2015.

    Try using these instructions on how to troubleshoote jetpack bugs. If nothing happens, don’t hesitate to contact me further. I hope we will solve your issue!

    Thank you so much for your assistance & as the website designers, it is the best answer for countering JetPack plugin issue. 

    on July 27, 2018.

    I had faced that error to on my staff leasing company website glad I managed to solve it.
    Jetpack for wordpress is really good

    on August 20, 2018.

    Thank you for providing solution. After visiting 13 websites from Google I found solution in your website. Working as developer in reputed web design company

    on August 29, 2018.

    thanks for you post this information. i am working as a website developer in Mumbai

    on November 21, 2018.

    Thanks for this wonderful post. These things will really help us in development. Hello We are Limra Technosys is leading
    mobile app development company in Mumbai,
    SEO agency in Mumbai,
    Digital marketing agency in navi mumbai
    E-commerce service providers,
    responsive web designers,
    software development company in Mumbai   

    on December 4, 2018.
    Reply