Hi,
Make sure you are using the latest development version, from the screenshots you have sent it seems to be the old version.
1. Not sure how you came to that conclusion – your CDN is proxying our data (entire site). The CDN is there to load the static contents only (flags and js files). If you are referring to x-proxy-cache-info header, then it has nothing to do with GTranslate. I have tried it with SG Optimizer plugin and do not confirm it does not cache the pages.
2. Cannot confirm that, when I disable it the flags and js files are being loaded locally.
3. Do not confirm. I guess you forgot to clear your website and browser cache after the setting was changed. Make sure to do CTRL+F5 hard refresh, so browser can refresh the cache.
4. Please provide more details, I do not see any language flags are being loaded when I check the browser console. However I notice that 2 js files are being loaded: fc.js and base.js, I believe you have changed the Wrapper Selector setting, make sure it is set to the default value .gtranslate_wrapper or it is empty. With what I see on your staging website only base.js should be loaded.
5. That is correct, it should be there when Enable CDN option is enabled.
6. There is no need to preconnect in advance, dns-prefetch is enough.
Thanks! 🙂
Hi @edo888,
As always, thank you for the quick reply.
Following your input, we’ll download the latest development version later today or tomorrow, and update our feedback accordingly.
Meanwhile, would it be possible for you to assign a version number to the development file listed in WP? That will ensure we’re using and testing the latest development version before giving you feedback.
Can you comment on Item 7 above?
Thank you!
Hi,
This is the procedure you need to take when testing and reporting the issues.
1. Download the latest development version.
2. Make sure to disable all cache/optimization plugins.
3. If the something not expected happens, open a new support ticket, mention the steps you take, the expected behavior and the reality.
4. If everything works as expected, you can gradually enable cache plugins one by one and test again. In that case you will know if the issue is caused by a specific cache plugin or not. When you find an issue with cache plugin enabled, open a separate support topic and provide the steps to reproduce the issue.
6 & 7 are related, when the CDN option is enabled, we let the browser know that it needs to prefetch the IP record for our CDN, so that future requests happen faster. If you do not want that to be in the header, then you need to disable the Enable CDN option.
Thanks! 🙂