Support » Plugin: Redis Object Cache » Conflict with WPML

  • Resolved Rookie

    (@alriksson)


    Causes conflict with WPML plugin and when connecting translations. As soon as a translation is connected the page breaks and respond with a 404. The issue is reported to WPML as well. But I think this might be on your side? Works when Redis Object Cache plugin is disabled.

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

    (@tillkruess)

    This plugin is just a backend for WordPress to talk with Redis. All the logic is handled at WPML’s end.

    Can you link to the WPML report here?

    To be fair I don’t know on who ends the bug or conflict is but what I found after the debugging is that I can not have WPML and redis object cache enabled then the connected translations breaks and respond as a 404.

    What report do you refer to? Just sent the final debugging explanation to them in a private ticket. Which basically just says those two plugins does not play as friends anymore. But can all combinations were tested and the only conflict was between yours and wpml.

    let me know.

    Plugin Author Till Krüss

    (@tillkruess)

    What report do you refer to? Just sent the final debugging explanation to them in a private ticket.

    I thought maybe it was a publicly available forum or GitHub post.

    But can all combinations were tested and the only conflict was between yours and wpml.

    Yeah, I’ve seen plenty of cases where plugins would not use the WP’s Object Cache API correctly and run into issues.

    I’m sure they will either patch the issue on their end.

    Yeah, I’ve seen plenty of cases where plugins would not use the WP’s Object Cache API correctly and run into issues.

    So that sounds to be the case and what you think. Thanks!

    I’m sure they will either patch the issue on their end.

    Yeah hopefully, thanks!

    Rookie

    (@alriksson)

    @tillkruess They are very unprofessional in the support, and they are not developers. Seems like they do not even know what redis is. They think your plugin is redis etc. Do you think you could “Ask the Redis plugin developers to contact us using Go Global Program” would you mind?

    they kind of refuse to admin the issue. But since you do not talk with any developer in the support it’s useless.

    Plugin Author Till Krüss

    (@tillkruess)

    Can you post the link to the program?

    Rookie

    (@alriksson)

    Plugin Author Till Krüss

    (@tillkruess)

    Ah, that program doesn’t apply to this plugin, because it’s actually them using the wp_cache_* function that this plugin provides, not the other way around.

    I’d suggest nagging them over and over until they give you a proper response, or alternatively hire a developer to figure out the issue and then submit a patch to WPML.

    Rookie

    (@alriksson)

    What do you mean with it’s actually them using wp_cache_*..?

    Plugin Author Till Krüss

    (@tillkruess)

    This plugin only provides and interface for WPML to talk with Redis and WP’s cache. If there is an issue, it’s 99.95% of the time a bad or wrong use of WP’s cache functions.

    So I’m afraid you’ll have to keep nagging them until they give you a proper response.

    Since it’s a premium plugin, I can’t see the source code to see what they are actually doing.

    Rookie

    (@alriksson)

    Yeah, that’s what I try but they kind of refuse to admit or look further into it. Yeah, premium support it’s not for sure haha! WPML caused me more issue than any plugin and has a very strange approach in their troubleshooting and support approach.

    If you give me a site I can register the site in our account and send the key over to for checking.

    Plugin Author Till Krüss

    (@tillkruess)

    Let’s have a look, send me an email.

    @tillkruess sorry to the late reply. Found the issue and it was connected to https://wordpress.org/plugins/wp-hide-security-enhancer/ compatibility issue which was solved in their latest update.

    Thanks anyhow!

    Plugin Author Till Krüss

    (@tillkruess)

    @alriksson: Fantastic, thanks for letting me know!

Viewing 14 replies - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.