Jetpack bug interacting with Relevanssi, AMP

  • Resolved cedialogs

    (@cedialogs)


    4 years, 3 months ago

    When using the search widget in https://www.oberlinchaos.com the following 3-way interaction occurs between Jetpack, AMP, and Relevanssi search:

    Notice: amp_is_available was called incorrectly. amp_is_available() (or amp_is_request(), formerly is_amp_endpoint()) was called too early and so it will not work properly. WordPress is currently doing the the_content hook. Calling this function before the wp action means it will not have access to WP_Query and the queried object to determine if it is an AMP response, thus neither the amp_skip_post() filter nor the AMP enabled toggle will be considered. It appears the plugin with slug jetpack is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/oberlinc/public_html/wp-includes/functions.php on line 5229

    Disabling jetpack makes the bug go away when Relevanssi is activated, and disabling Relevanssi with JetPack activated also makes the bug go away. When both plugins are activated the bug appears. What on earth could be making these 3 plugins interact in this way?

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer ??

    @cedialogs can you confirm that you tested that behavior with just those plugins active and all others disabled?

    Additionally, with Jetpack disabled, do you get the same amp_is_available was called incorrectly error message and does the error always refer to Jetpack under the It appears the plugin with slug jetpack is responsible error?

    If you didn’t test with all other plugins disabled, please do that and get back to us with those results.

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘Jetpack bug interacting with Relevanssi, AMP’ is closed to new replies.