ɃØĦɆᵾS
ɃØĦɆᵾS
TTwenty
Created by Prince on 2/2/2025 in #❓︱help
Start Localization (Lab panel)
If you think so, then please report it in repo
23 replies
TTwenty
Created by Prince on 2/2/2025 in #❓︱help
Start Localization (Lab panel)
Then you have to run provided query
23 replies
TTwenty
Created by Prince on 2/2/2025 in #❓︱help
Start Localization (Lab panel)
But before running this query, please check if there's already a feature flag in your database linked to your workspace by running this query select * from core."featureFlag" where key='IS_LOCALIZATION_ENABLED';
23 replies
TTwenty
Created by Prince on 2/2/2025 in #❓︱help
Start Localization (Lab panel)
Alternatively, as I'm checking in code, you can add a additional record in your database by running this query in your database (replace displayName with the name of your workspace) insert into core."featureFlag" values (uuid_generate_v4(), 'IS_LOCALIZATION_ENABLED', (select id from core.workspace where "displayName"='<workspace_name>'), true, now(), now());
23 replies
TTwenty
Created by Prince on 2/2/2025 in #❓︱help
Start Localization (Lab panel)
None, literally copy paste like I wrote, I took it from the .env.example
23 replies
TTwenty
Created by Prince on 2/2/2025 in #❓︱help
Start Localization (Lab panel)
Try adding TRANSLATION_IO_API_KEY=xxx in twenty-front/.env file, maybe that's the reason
23 replies
TTwenty
Created by Prince on 2/2/2025 in #❓︱help
Start Localization (Lab panel)
Weird, it's working for me
23 replies
TTwenty
Created by Prince on 2/2/2025 in #❓︱help
Start Localization (Lab panel)
Did you try turning this option on?
23 replies