Jetpack 2.7 and Blog-in-Blog

  • theKiwi

    (@thekiwi)


    10 years, 3 months ago

    I upgraded a site to JetPack 2.7 today, and that caused Blog in Blog to stop working, generating error messages like

    Notice: Undefined index: current_post_id in /Library/WebServer/Documents/TNG_WordPress/wp/wp-content/plugins/blog-in-blog/blog-in-blog.php on line 669

    and the “Call Stack” references things like

    16 0.2862 30958336 Jetpack_Media_Summary::get( ) ../functions.twitter-cards.php:53
    17 0.2870 30974648 Jetpack_Media_Summary::get_excerpt( ) ../class.media-summary.php:181

    Deactivating JetPack allows the pages with Blog in Blog on them to show correctly.

    Activating JetPack and the errors are back.

    Blog-in-Blog was working correctly with the previous version of JetPack.

    I’m nowhere near clever enough to figure out what the problem might be.

    Thanks

    Roger

    http://wordpress.org/plugins/jetpack/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    10 years, 3 months ago

    The Notice is something the Blog in Blog plugin authors should be able to fix for you, but that shouldn’t stop the plugin from working normally.

    What happens when both Jetpack and Blog in Blog are active? Are the Blog in Blog shortcodes displayed in plain text on the page? Or are they not displayed at all?

    Could you also try to deactivate Jetpack’s Open Graph meta tags and let me know if it helps? You can do so with this simple plugin:
    http://i.wpne.ws/M7Le

    Thread Starter theKiwi

    (@thekiwi)

    10 years, 3 months ago

    Thank You Jeremy!!

    Installing that plugin to disable the Open Graph meta tags has solved the problem for now.

    To your other points – when both plugins were active, the blog-in-blog content displayed as expected, but the page was preceded by many instances of the warnings as shown above so the page content was many screens full down the page.

    My server which was recently setup to replace an older one is running PHP 5.4.21 (the previous server was on PHP 5.3.x) now displays errors in tables with an orange header and then lines of the “Call Stack” references all printed out. This is probably some setting in my php.ini file that should be changed to prevent the errors outputting like this?

    I’ve also posted on the blog-in-blog forum with the same question, so hopefully the developer there will see it and figure out a fix.

    Thanks!

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    10 years, 3 months ago

    when both plugins were active, the blog-in-blog content displayed as expected, but the page was preceded by many instances of the warnings as shown above so the page content was many screens full down the page.

    The Blog In Blog plugins authors should be able to look into that Undefined index notice for you.
    In the meantime, you can disable WP_DEBUG in your production site so the notice is not displayed:
    http://codex.wordpress.org/WP_DEBUG

    I don’t know why the the “Call Stack” lines are printed, though. The functions mentioned there are used to build the Open Graph meta tags in Jetpack. They will look for an excerpt to use as an Open Graph meta description, for example. Since there are many posts within a single page, the function is probably going through each post, but I’m not sure why the Call Stack is displayed. A Debug function like debug_backtrace must still be active somewhere on your site.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Jetpack 2.7 and Blog-in-Blog’ is closed to new replies.