• Resolved moisb

    (@moisb)


    hello, I found a conflict that I’m sure to be caused by the Redis Cache plugin.
    I use Gravity Forms connected with the add-on:
    https://docs.gravityforms.com/category/add-ons-gravity-forms/help-scout-add-on/

    This addon allows Gravity Forms to connect to the Help Scout API and record submissions as support calls.

    After I installed and activated Redis Cache a few weeks ago, I saw that most forms were not arriving in Help Scout.

    I made several test submissions with Redis Cache enabled and the Gravity Forms log errors connecting to the Help Scout API. And the messages didn’t arrive in Help Scout.

    I disabled Redis Cache and everything went back to work, no more error logging. All messages are coming to Help Scout perfectly.

    Has anyone else had the same problem? Do you know of any way to fix this and continue using Redis Cache?

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

    (@tillkruess)

    That sounds like the Gravity Forms plugin doesn’t use the WordPress object cache API correctly. It’s something they must fix on their end. This plugin is just an Redis driver.

    Thread Starter moisb

    (@moisb)

    Ok Till. But in this case, how do I solve? Is there a way to “ignore” Redis just for Gravity Forms and their addons?

    Plugin Author Till Krüss

    (@tillkruess)

    If that plugin uses a dedicated cache group, you could just add that group to the list of ignored groups.

    Their support team can help you with that question.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict with Gravity Forms Help Scout addon’ is closed to new replies.