• Resolved JPD Studio

    (@jpdstudio)


    We upgraded to version 3.0.2 last week which caused your plugin to stop working so we reverted back to 2.9.15. This version worked fine before we upgraded to 3.0.2 but no longer works, simply stopped working after the upgrade.

    We narrowed it down to a caching issue therefore we emptied the server/browser cache, wp rocket cache and turned off cloudflare cache (developer mode is on) but nothing has helped restore the functionality.

    If you view the site using this “no cache” url, you’ll notice the translations (top right) do work:?https://hungersolutionsny.org/?cache=no

    Do you have a list of resources that need to be excluded from cache such as specific cookies or arguments?

    The site is running WP 6.0.3, PHP 7.4 and is using the Salient theme. You’re currently seeing version 2.9.15 of the plugin in action on the site.

    Please let us know if you’ve seen this issue before and if you have any guidance on possible solutions.

    Many thanks!

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author edo888

    (@edo888)

    Hi,

    We have exclusion rules for most popular cache plugins. You need to exclude gtranslate javascript files from being “optimized”.

    I would recommend you to consult your cache plugin support. Cache plugins should not break the functionality.

    Thanks! ??

    Thread Starter JPD Studio

    (@jpdstudio)

    Thank you, @edo888! Quick follow-up question, which specific files or directories are you referring to by “gtranslate javascript files”?

    Many thanks!

    • This reply was modified 1 year, 11 months ago by JPD Studio.
    Plugin Author edo888

    (@edo888)

    Hi,

    Please open the browser console, go to network tab and search for gtranslate and you will find specific files depending on your configuration.

    Usually exclude rules in caching plugins accept non-specific keywords to match, so just gtranslate should be enough.

    Thanks! ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘New caching issue after upgrading to 3.0.2’ is closed to new replies.