Support

Hello Frank,

As per our email exchange last night, I can see that the translation JavaScript gets a 403 when trying to access your site's frontend page. This sends me down to a specific troubleshooting path.

The first thing I try in these cases is going to Admin Tools, .htaccess Maker and setting “Protect against clickjacking” to No. Then click on Save & Create .htaccess in the toolbar. The idea is that most of those tools use an IFRAME, and this setting blocks displaying your site in an IFRAME.

The next thing I'd try is setting the “Cross-Origin Resource Sharing (CORS)” to “Explicitly Allowed” and regenerate the .htaccess. This allows your site to be loaded from JavaScript running in a different domain or subdomain than your site. For the gory details see the CORS documentation on MDN.

If this still doesn't help, the next thing to try is setting “Block access from specific user agents” to No and regenerate the .htaccess. The idea is that the third party service you are using (GTranslate.io) needs to fetch your site's content somehow, translate it, and send it back to your site. When they fetch your site's content they do an HTTP request which has a User-Agent string. If that's one of the blocked ones, you get a 403.

Beyond that, the only other setting I can guess might be relevant is “Prevent content transformation” which I would try disabling. This tells proxies to not modify the content of the site. This is normally used to prevent JS and CSS from being minified and compressed by a CDN or caching proxy (e.g. Varnish), and to avoid double compression issues with pre-gzip'ed HTML content generated by Joomla. However, the no-transform HTTP header may be interpreted by the translation proxy as a forbidding factor to translation (translating does change the content by definition) which might cause it to return a 403. I am not sure that's the case, or whether it would make sense.

Beyond that, you get to do troubleshooting the old-fashioned way. Start disabling options one-by-one until you find which one was causing the problem, then try to figure out why it did that and whether you need to adjust something else in your site or server to avoid that being a problem.