jetpack causes AMP errors

  • Jetpack is fingered by AMP for causing the following error message when the relevanssi plugin is used to search a WordPress blog:

    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

    Can anyone help untangle this mess? Note: The plugin “AMP for WordPress” was recently uninstalled and replaced by the plugin “AMP”.

Viewing 1 replies (of 1 total)

  • Turn off The Relevanssi (sp?) plugin and try whatever you did without it (was that a search?).

    Jetpack may have triggered that but the problem may be something else actually.

    If need be you might turn off JetPack next when you turn Relevanssi back on and then contact the plugin seeming to cause that problem.

Viewing 1 replies (of 1 total)
  • The topic ‘jetpack causes AMP errors’ is closed to new replies.