• Resolved Dave Loodts

    (@davelo)


    Hi, we have this code that uses the get_terms functions to roll out a product category navigation.

    Since WP6.0 it doesn’t work anymore, only when we deactivate Redis caching.
    We see 2 sympthoms:
    – an empty $product_categories array
    – or the second get_terms in our code outputs always the same (that is the most common)

    This is a screenshot of the code: https://share.woofers.be/d5uOW9GN

    The code was working great before wp6.0 with Redis on. Now it seems that the second get_terms in that loop gets stuck in memory. I tried to empty the parameters, without results.

    Any idea what can be the solution here?

Viewing 4 replies - 1 through 4 (of 4 total)
  • same problem

    Thread Starter Dave Loodts

    (@davelo)

    I ran some more tests today on staging:

    – WP5.9 + Woo 6.6: No Redis issue
    – WP5.9 + Woo 6.4: No Redis Issue
    – WP6.0 + Woo 6.4: Redis Issue
    – WP6.0 + Woo 6.6: Redis Issue

    So, it has clearly something to do with 6.0.
    The launch of 6.0 was mostly all about FSE, but the Performance team has also done some contributions for cache improvements:

    Caching improvements in WordPress 6.0

    The question is: to who should we talk to? Performance or Redis plugin?

    Plugin Author Till Krüss

    (@tillkruess)

    If you guys want fast support post on GitHub. I didn’t get an email about this post ??

    Are both of you using the latest release of the plugin?

    Thread Starter Dave Loodts

    (@davelo)

    Hi @tillkruess, thanks for replying. I will post next time on Github.
    To answer the question: yes, we use the latest plugin.
    We still see the issue when using the Redis plugin, so still is disabled.

    There is also this trac ticket that is maybe interesting for you: https://core.trac.www.ads-software.com/ticket/55837. I guess they are working it out in a solution in WordPress 6.0.1

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘a get_terms not working after wp 6.0’ is closed to new replies.