Relevanssi search conflict

  • Resolved olegburakov

    (@olegburakov)


    4 years, 4 months ago

    Hi guys!
    I’ve installed Relevanssi plugin (for search customization) and got this error when I navigate to Search page:

    Notice: is_amp_endpoint was called incorrectly. is_amp_endpoint() was called before the wp action which means it will not have access to the queried object to determine if it is an AMP response, thus neither the amp_skip_post filter nor the AMP enabled publish metabox toggle will be considered. Please see Debugging in WordPress for more information. (This message was added in version 1.0.2.) in /nas/content/live/dglofox/wp-includes/functions.php on line 5167

    On the same site but without AMP all works good. And when I deactivate Relevanssi on AMP site – notice also gone (thats why I decided this is because of plugin conflict).

    Have you any ideas what cause the problem, or I should ask Relevanssy suport?

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Pascal Birchler

    (@swissspidy)

    Hi there

    The Relevanssi is apparently calling the is_amp_endpoint function too early, which causes this notice.

    Indeed I recommend you to contact their support to fix this in the Relevanssi plugin, as it’s not an issue in the AMP plugin itself.

    Thread Starter olegburakov

    (@olegburakov)

    Big thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Relevanssi search conflict’ is closed to new replies.