FacetWP conflict

  • Resolved emilyel

    (@emilyel)


    5 years, 6 months ago

    Hi,

    I have recently started to use FacetWP, which fails to refresh after a filter option is checked.

    I’ve traced the problem back to LiteSpeed. The filter works immediately as soon as Litespeed cache is disabled.

    I can see from the Litespeed change logs that this has been addressed in previous updates, but persists with my site. I have the latest version of both plugins.

    Could you please advise?

    Here’s the relevant line from the debug log

    05/19/19 15:37:49.012 [80.7.78.244:52270 1 72B] Footer check passed
    05/19/19 15:37:49.013 [80.7.78.244:52270 1 72B] X Cache_control off – not GET method:POST
    05/19/19 15:37:49.013 [80.7.78.244:52270 1 72B] X Cache_control -> no Cache
    05/19/19 15:37:49.013 [80.7.78.244:52270 1 72B] X-LiteSpeed-Cache-Control: no-cache
    05/19/19 15:37:49.015 [80.7.78.244:52270 1 72B] Footer check failed: 1-{“facets”:{“recipe_index”:”<div class=\”facetwp-checkbox\” data-value=\”cookies-cakes\”>Cookies and
    05/19/19 15:37:49.015 [80.7.78.244:52270 1 72B] Media finalize
    05/19/19 15:37:49.017 [80.7.78.244:52270 1 72B] Optimizer start
    05/19/19 15:37:49.026 [80.7.78.244:52270 1 72B] End response

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Could you please try make backup of file wp-config.php

    and add this code into it ?

    define('LSCACHE_ESI_SILENCE', true);

    Let us know if that works.

    Best regards,

    Thread Starter emilyel

    (@emilyel)

    Thanks. I have just tried that and purged all in LSCache but it has not solved the problem.

    Thread Starter emilyel

    (@emilyel)

    I have managed to get the filter working by putting the value “recipe-index” (without quotation marks) in LiteSpeed Cache Settings > [6] Tuning > URI Excludes.

    This is only a temporary fix, though, as obviously it prevents *all* optimisation of that high-traffic page.

    It would be great to understand which setting is causing the conflict, please.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Please try use this

    fwp_recipe_index

    instead of recipe-index in URI Excludes.

    and see how it goes.

    Best regards,

    Thread Starter emilyel

    (@emilyel)

    Have done that and it works, thanks. The only issue now (with either fwp_recipe_index OR recipe-index in URI Excludes) is that clicking reset or unchecking all the boxes doesn’t work, so not quite there yet.

    https://www.amummytoo.co.uk/recipe-index/

    Hi, could you please join our Slack channel or submit a ticket here for helping us to reproduce the bug, thanks!

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