Today I added automatic translation to my Glide app with Weglot within 5 minutes and because I think that’s pretty cool, I recorded a little video to show how I did it: Loom | Free Screen & Video Recording Software | Loom
Downside
- You won’t have a language switcher in the app. Each translation lives on a different subdomain.
- Logging in with Gmail for example redirects to the original app so it’s better to use pincodes.
Upside
- Translations happen automatically on all content but are still editable if you think something is off.
- It only takes 5 minutes and Weglot is very affordable.
Steps
- Step 1: add a custom domain to Glide
- Step 2: add a project to Weglot for your custom domain and add a new CNAME record in your DNS settings to add a subdomain to your custom domain for the translated app to live in (it still uses the same Glide App, it’s only the frontend that is translated)
- Step 3: Add the ‘body’ CSS selector under App settings in Weglot to let Weglot know that everything in the body can be translated. If something doesn’t translate (for me the login screen didn’t), add other CSS selectors (you can find them with the inspec tool in Google Chrome)
- Step 4: When you visit the app on the subdomain, it will show you the automatically translated app.
Repeat for as many languages as you’d like 
6 Likes
Hi there,
It seems that Glide is now blocking this method (using the subdomain with Weglot) because of their CORS. They told me I need to make a feature request to change that. Has anybody experienced the same thing?
Does the standard subdomain without custom CSS and JS still works too?
The subdomain using Weglot doesn’t work with or without custom CSS.
I know… I understand it’s not Glide’s priority:
We discussed this with our engineering team. You’re welcome to use Weglot for translations, but unfortunately we don’t have the resources to support or investigate issues specifically related to its integration.
2 Likes
@burningmikey, I have a client who needs to use WeGlot. Is it still not working for you?
Hi there, it’s not working still. I used all my cards with Glide, and I am now waiting for Weglot to tell me if there is anyway to go around (should have an answer tomorrow). I keep you posted.
@Hassan_Nadeem @MaximeBaker
Weglot now works! Here is some context for anybody who may run into this issue later:
Update from Weglot, there were 2 issues that are now solved.
- It seems that Glide CORS were blocking a “double” subdomain structure (e.g fr.app.mydomain.com.mx in my case). So I simplified it to fr.mydomain.com.mx.
- There was 1200+ non necessary translations of “backend” text and translation of javascript strings (e.g ${…}). So I excluded that url from translation, but Weglot was handling it as a redirection which then prevented the app to load normally.
2 Likes
Nice, thanks for investigating !!!
1 Like
