Translation user settings missing #196

New Issue

Closed

opened 2022-11-08 12:09:14 +00:00 by nninja · 4 comments

nninja commented

2022-11-08 12:09:14 +00:00

Although /api/v1/akkoma/translation/languages is returning lists of source, target languages, in pleroma-fe > Settings > General, the "translation target language" selection is missing:

Both pleroma-fe and akkoma are on latest develop branch. FE is fetching the languages lists OK:

Although `/api/v1/akkoma/translation/languages` is returning lists of `source`, `target` languages, in __pleroma-fe > Settings > General__, the "translation target language" selection is missing: ![image](/attachments/fd2e3df8-a477-401e-9056-67b2f177250a) Both pleroma-fe and akkoma are on latest `develop` branch. FE is fetching the languages lists OK: ![image](/attachments/60ee1246-e139-4e37-b1a1-920ee00b2f14)

image.png

38 KiB

image.png

56 KiB

floatingghost referenced this issue from a commit

2022-11-08 12:26:10 +00:00

use correct key for languages

floatingghost closed this issue

2022-11-08 12:26:10 +00:00

floatingghost commented

2022-11-08 12:26:25 +00:00

Owner

fixed via 8713f1870f

update your FE when that CI job finishes

fixed via 8713f1870f52c7 update your FE when that CI job finishes

floatingghost referenced this issue from AkkomaGang/akkoma

2022-11-11 10:34:30 +00:00

LibreTranslation: API endpoint HTTP 500 error #257

nninja commented

2022-11-12 12:59:51 +00:00

Author

Hmm, I've updated FE a few times, still getting the old code (without the changes in 8713f1870f)

sudo -Hu akkoma MIX_ENV=prod mix pleroma.frontend install pleroma-fe --ref develop

but I can see the files under /opt/akkoma/instance/static/frontends/pleroma-fe/develop/ have new timestamps after the command finishes. Not sure what I did wrong?

Hmm, I've updated FE a few times, still getting the old code (without the changes in 8713f1870f52c7) ``` sudo -Hu akkoma MIX_ENV=prod mix pleroma.frontend install pleroma-fe --ref develop ``` but I can see the files under `/opt/akkoma/instance/static/frontends/pleroma-fe/develop/` have new timestamps after the command finishes. Not sure what I did wrong?

floatingghost commented

2022-11-12 17:06:13 +00:00

Owner

ah, my hunch would be that you had the ref

set to stable

you can change ref either via frontends or via admin-fe

but anyhow stable release was today, so just update your stable FE and it should be there :upside_down:

ah, my hunch would be that you had the `ref` set to `stable` you can change ref either via `frontends` or via admin-fe ![image](/attachments/2db85cc4-6ebb-473b-ab53-6efdb98b4c04) but anyhow stable release was today, so just update your stable FE and it should be there :upside_down:

image.png

16 KiB

nninja commented

2022-11-13 10:28:54 +00:00

Author

Spot on, in the config, the ref was set to stable. I misunderstood --ref develop in the CLI was going to update the active FE 😄

Now I see that the install command is for downloading and extracting the FE package, and the config "Reference" field is for switching to different installed FE "branches"

Spot on, in the config, the ref was set to `stable`. I misunderstood `--ref develop` in the CLI was going to update the active FE 😄 Now I see that the `install` command is for downloading and extracting the FE package, and the config "Reference" field is for switching to different installed FE "branches"