Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translation key not replaced #32918

Open
LoboMetalurgico opened this issue Dec 19, 2024 · 6 comments
Open

Translation key not replaced #32918

LoboMetalurgico opened this issue Dec 19, 2024 · 6 comments
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail topic/ui Change the appearance of the Gitea UI type/bug

Comments

@LoboMetalurgico
Copy link

LoboMetalurgico commented Dec 19, 2024

Description

On the repository page, a translation key appears saying repo.project_board where the project menu should be.

Screenshots

image

Gitea Version

1.22.6

Can you reproduce the bug on the Gitea demo site?

No

Operating System

Debian

Browser Version

Chrome 131.0.6778.205

@LoboMetalurgico LoboMetalurgico added topic/ui Change the appearance of the Gitea UI type/bug labels Dec 19, 2024
@lunny
Copy link
Member

lunny commented Dec 19, 2024

What's your language?

@LoboMetalurgico
Copy link
Author

Brazilian Portuguese, but it happens in English too.

@lunny
Copy link
Member

lunny commented Dec 20, 2024

I can't reproduce this. How did you download and install your Gitea?

@wxiaoguang
Copy link
Contributor

Check your custom folder, have you extracted the assets and now is using out-dated assets?

@wxiaoguang wxiaoguang added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Dec 20, 2024
@LoboMetalurgico
Copy link
Author

I'm running it using pterodactyl, using a debian docker image. The script downloads directly from https://dl.gitea.io/gitea/. Regarding the assets, I didn't extract them.

@wxiaoguang
Copy link
Contributor

wxiaoguang commented Dec 20, 2024

The repo.project_board key is there (in 1.22)

In history, such problems are all caused by out-dated local (in user's deployment) locale files.

Could you check your Gitea's custom&working path (to see whether there are outdated "ini" locale files)? Or, could you provide a reproducible setup with detailed steps to reproduce the problem? Then others could debug it by your detailed steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail topic/ui Change the appearance of the Gitea UI type/bug
Projects
None yet
Development

No branches or pull requests

3 participants