Conflict with Caching and Awesome Support Plugin

  • Resolved kateeba

    (@kateeba)


    1 year, 6 months ago

    Hi,

    we already had the error described here once. We suspect that awesome support and caching is causing the problem. Possibly also the combination with Polylang seems to cause an error. The plugin overwrites the Woocommerce end pages such as Shop Home / Shopping Cart / My Account etc…. A blog page is then called up. If we deactivate the awesome plugin, the error no longer occurs. In any case, we do not know exactly why the error occurs. It is definitely caused by awesome support. As mentioned, it could be that it is not compatible with Polylang. What can we do now. I guess the pro version won’t solve the problem?

    Thanks. lg Elena

    • This topic was modified 1 year, 6 months ago by kateeba.
Viewing 5 replies - 1 through 5 (of 5 total)

  • Hello @kateeba , I’m sorry to hear that you are having trouble with the awesome support plugin.disappointed

    It sounds like there might be a conflict between the plugin and Polylang, which is a multilingual plugin for WordPress. This could cause the plugin to overwrite the Woocommerce end pages with a different language or page.

    One possible solution is to check the settings of both plugins and ensure they are compatible. For example, you could try to set the same default language for both plugins or exclude the woocommerce end pages from being translated by Polylang.

    Another possible solution is to clear the cache of your website and browser, and see if that resolves the issue. Sometimes, caching can cause outdated or incorrect information to be displayed on your website.

    If none of these solutions work, please let me know.

    I hope this helps. Please let me know if you have any other questions or concerns.

    Regards

    Thread Starter kateeba

    (@kateeba)

    Hi Jawad, first of all, thank you for your answer. There does seem to be a conflict with Polylang and additional caching. However, we can’t do both solutions because we need the Woocommerce end pages translated (these are very important pages) and also caching is important for our site. During the time when we did not use caching, this error did not occur. Is there another solution?

    Hi @kateeba

    Can you please share the production environment details? I will try to reproduce and investigate this further.

    Regards

    Thread Starter kateeba

    (@kateeba)

    https://fridgegrow.com/phpinfo.php

    Thank you ??

    lg Elena

    Thread Starter kateeba

    (@kateeba)

    It would be great if we could find a solution here. We would generally like to continue using the plugin. I also noticed that when the cache system is deactivated, the error hardly ever occurs.

    ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Conflict with Caching and Awesome Support Plugin’ is closed to new replies.