• Resolved sweetrobot

    (@sweetrobot)


    hi there @tillkruess and co.

    it seems there is a conflict with this plugin and facetwp (fwp) which we use for filtering woocommerce products. example: https://new.floridaseating.com/product-category/indoor/ – select a few filters and it will output the error “FacetWP was unable to auto-detect the post listing”. debug is enabled so can prod via the console.

    i reached out to support from fwp, (who have been very helpful in the past). however, in this instance i was told that various object caching plugins tend to prevent fwp from being able to detect the query – and to therefore disable the object cache, or create exclusions.

    i would prefer to pursue a solution where both play nicely before throwing in the towel and opting for either resolve. i figure i’d ask here, seeking support from both sides.

    if needed, i am not opposed to seeking professional/ developer assistance in the matter. i wanted to see if a solution where both are fully compatible is possible in the first place.

    cheers

    • This topic was modified 1 year, 4 months ago by sweetrobot.

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

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    Hey! This is quite common. Some plugins like FacetWP don’t bother supporting persistent object caching which is a huge part of WordPress core. I’d suggest switching away from FacetWP if they refuse to support such an integral part of WordPress. You can also ignore cache groups, check the readme and FAQ for more information.

    Thread Starter sweetrobot

    (@sweetrobot)

    that’s unfortunate…

    @tillkruess, could you recommend an alternative filtering solution- in the off chance you knew off the top of your head?

    before I commence the hunt for an alternative which does work with object cache, is it unreasonable to pursue development of a compatability layer between the two? that is to say, would development time needed be tremendous, or is it solvable with moderate dev hours?

    thanks for the feedback!

    • This reply was modified 1 year, 4 months ago by sweetrobot.
    Plugin Author Till Krüss

    (@tillkruess)

    @tillkruess, could you recommend an alternative filtering solution- in the off chance you knew off the top of your head?

    No, sorry.

    before I commence the hunt for an alternative which does work with object cache, is it unreasonable to pursue development of a compatability layer between the two? that is to say, would development time needed be tremendous, or is it solvable with moderate dev hours?

    If you want to have something custom for your site, sure. I can’t help with that.

    Thread Starter sweetrobot

    (@sweetrobot)

    ok! also, was just asking in general – if something like this would be typically very involved – many dev hours. i have devs in mind, and did not mean to imply you ??

    Plugin Author Till Krüss

    (@tillkruess)

    Yeah, let me know how it goes ??

    LWD

    (@kieranbarnes)

    A quick note from my experience – we have 10s of sites that use Redis and FacetWP perfectly together. I’d suggest there is something else causing the issue.

    Did you have any of the other FacetWP addons enabled too?

    Thread Starter sweetrobot

    (@sweetrobot)

    @ldw – wow, i would really love to see what your config is….

    is there a live site you could share? i’ve been pulling my hair out on this.

    i was specifically told by the fwp devs that object caching is simply not supported. do you perhaps have fwp excluded? pr a special config to get object caching to cache fwp filter results?

    i later enabled fwp’s own caching add-on, but we had the issue prior. we also could not use fwp with object caching on wpengine, and have since changed hosts.

    would really love to get to the bottom of this as filtering is the most used feature and also the slowest for us.

    any and all info would be greatly appreciated.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘issue with ‘facetwp’’ is closed to new replies.