text display issue (getting worse) #1417

New Issue

2023-04-16T15:48:45+02:00

fariouche commented

2023-04-16 15:48:45 +02:00

Hello,

Since the beginning, I've never been able to see texts in external components... It didn't bothered me much until now, were some core functionalities are now also having this issue.
For example, the mqtt integration is now also showing this issue: pressing the re-configure mqtt to bring the mqtt configuration popup, I see all the fields , but not their associated texts.

Digging a bit, I discovered that homeassistant core migrated some internal integrations (like mqtt) to us config flow. And indeed, my previous external integrations were using config flow.

So, for some reason, all config flow elements are having this issue. No error in the log, not error in the browser too which makes it very hard to debug.
All the other UI elements are working.

If you have any idea that can help me, because for now I'm clueless...

Thanks!

Hello, Since the beginning, I've never been able to see texts in external components... It didn't bothered me much until now, were some core functionalities are now also having this issue. For example, the mqtt integration is now also showing this issue: pressing the re-configure mqtt to bring the mqtt configuration popup, I see all the fields , but not their associated texts. Digging a bit, I discovered that homeassistant core migrated some internal integrations (like mqtt) to us config flow. And indeed, my previous external integrations were using config flow. So, for some reason, all config flow elements are having this issue. No error in the log, not error in the browser too which makes it very hard to debug. All the other UI elements are working. If you have any idea that can help me, because for now I'm clueless... Thanks!

onkelbeh added the Bug label 2023-04-16 18:16:00 +02:00

fariouche commented

2023-04-16 19:20:21 +02:00

I think I know why: I'm missing the generated translations (for example in homeassistant/components/mqtt, I'm missing the translations folder)
When download the github version of homeassistant core to help me debug, I've seen a bunch of lines saying "generating translation for ..."

"script/setup" is doing it.

I'm not sure why I'm missing the translations, nor how to fix that yet

I think I know why: I'm missing the generated translations (for example in homeassistant/components/mqtt, I'm missing the translations folder) When download the github version of homeassistant core to help me debug, I've seen a bunch of lines saying "generating translation for ..." "script/setup" is doing it. I'm not sure why I'm missing the translations, nor how to fix that yet

onkelbeh commented

2023-04-17 07:17:16 +02:00

which version do you have installed?
which lang are you using?

have a slight idea, they changed the way the translations are distributed.

which version do you have installed? which lang are you using? have a slight idea, they changed the way the translations are distributed.

fariouche commented

2023-04-17 10:21:38 +02:00

I'm using the 2023.3, but will migrate to latest soon.
I'm using French and English, both have defects.

Seems like when translations/en.json is missing, the text is not rendered.
The setup script is generating them for each integration in homeassistant/components folder that contains strings.json

I'm using the 2023.3, but will migrate to latest soon. I'm using French and English, both have defects. Seems like when translations/en.json is missing, the text is not rendered. The setup script is generating them for each integration in homeassistant/components folder that contains strings.json

fariouche commented

2023-04-17 12:14:30 +02:00

For information, I added this to the ebuild and it is working now:


python_prepare_all() {

        python3 -m script.translations develop --all
        distutils-r1_python_prepare_all
}

For information, I added this to the ebuild and it is working now: ``` python_prepare_all() { python3 -m script.translations develop --all distutils-r1_python_prepare_all } ```

👍 1

Ghost commented

2023-04-19 10:43:50 +02:00

Same problem here with 2023.4.4 all English. Thank you fariouche for the workaround. Everything's fine now. I can't remember when this behaviour first occurred. Back in 2022 this was working well. Would be nice to have this integrated into to the ebuild (Fix or USE flag). Thank you onkelbeh

no text 1.png

12 KiB

no text 2.png

11 KiB

onkelbeh commented

2023-05-01 14:19:30 +02:00

We'll switch to Pypi's SDIST, for a try. It's easier to copy the tests from github than to get an api token for lokalise.

onkelbeh referenced this issue from a commit

2023-05-01 14:26:06 +02:00

use Pypi's src (with translations), fixes #1417

onkelbeh closed this issue

2023-05-01 14:26:06 +02:00

onkelbeh commented

2023-05-01 15:11:49 +02:00

This is caused by https://developers.home-assistant.io/blog/2023/02/06/translations-files-removed-from-core/

python3 -m script.translations develop --all only prepares english language.

We'll now use the translations packed into the SDIST, the fix will be included in the next release.

This is caused by https://developers.home-assistant.io/blog/2023/02/06/translations-files-removed-from-core/ `python3 -m script.translations develop` --all only prepares english language. We'll now use the translations packed into the SDIST, the fix will be included in the next release.

onkelbeh referenced this issue from a commit

2023-05-01 17:50:35 +02:00

update homeassistant-2023.4.6, change SRC_URI for the olds, fixes #1417, fixes #220

Sign in to join this conversation.

Branches Tags

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: onkelbeh/HomeAssistantRepository#1417