I18n and private piece

[aguerin]

hello there

We’re currently adding translations to our custom piece (called “Sellsy”). I followed the i18n doc and ran:

npm run cli pieces generate-translation-file sellsy

Then duplicated the generated translation.json into a fr.json file and filled in the French strings.On my local dev environment, everything works fine — translations show up as expected.

But on our test and preprod instances (based on your Docker image), the translations are not picked up. (Other pieces translations works fine)

I’ve double-checked: the piece archive does contain both translation files.This happened initially on 0.64.2, and I just tested again with 0.68.1 — same issue.

Any idea why private piece translations would work locally but not on Docker-based environments?

I can share the archive if that helps.Thanks !

[Abdul]

Let me check this and get back to you @aguerin, you installed the piece to your docker based environment using Archive or NPM ?

[aguerin]

hello Abdul, we’re using archive (the piece is currently private/custom)

[aguerin]

It has been fixed on 0.68.2 / fix: Installing custom pieces didn't include translations by AbdulTheActivePiecer · Pull Request #8969 · activepieces/activepieces · GitHub

Thanks