Opened 4 weeks ago
Last modified 2 weeks ago
#63340 new defect (bug)
"Edit site" button is no longer translated
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | minor | Version: | 6.8 |
Component: | General | Keywords: | close reporter-feedback |
Focuses: | Cc: |
Description
Hi there,
I hope this is the right place to report this.
Since updating to WordPress 6.8, the "Edit site" button in the header shows up in English, despite my WordPress admin console set up in French.
The other buttons show up in the correct language.
Attachments (1)
Change History (9)
#1
@
4 weeks ago
Hi @cixtpide,
this is interesting. Are you set to 'french' or french canadian or belgian? However, I cannot reproduce the issue. The strings have been translated in any locale, see
When you click on the cirle next to the number 1 and go to /wp-admin/update-core.php
, do you see a section down the page saying "Traductions", "De nouvelles traductions sont disponibles."
and a button "Mise à jour des traductions"? If so, try to push it and see it you get the translation after.
#2
@
4 weeks ago
Thank you for your answer!
The language is set to "French" in settings.
There were translation updates, but for other languages. I have done those but it didn't fix it.
I see that this string is translated properly on my other website, which I also upgraded to 6.8 today, so it's very strange.
I tried disabling all plugins but that didn't fix it.
#3
@
4 weeks ago
Hi @cixtpide, thanks for raising your issue, However I am unable to reproduce the issue, the translations are working fine for me.
#5
@
4 weeks ago
I also don't reproduce the problem on a brand new installation with default theme and no plugins.
#6
@
4 weeks ago
- Keywords close reporter-feedback added
Hello and welcome to WordPress Core Trac, thank you for your report.
I can't reproduce the issue either, on both a fresh install and on an exiting install that was updated to 6.8.
#7
follow-up:
↓ 8
@
2 weeks ago
Hey,
I just encountered the same issue on my development environment and several of my sites.
After some debugging, I found the following:
The bug seems to be related to this change:
https://github.com/WordPress/wordpress-develop/commit/3f4d3585c31a72eab5e32afa057a458426aa42fd
The updated string can be seen here:
https://wp-languages.github.io/
I'm using the German version of WordPress. I set up a fresh Docker container with version 6.7.2 and then upgraded it to 6.8 via the admin interface.
Here's the issue: the .mo files in the wp-admin/languages folder weren't updated during the initial upgrade.
Clicking on "Reinstall version 6.8.2" resolved the issue.
I haven't had time to investigate why this happened.
Maybe someone else can look into it further?
#8
in reply to:
↑ 7
@
2 weeks ago
Update:
PO Header: # Translation of WordPress - 6.7.x - Administration in German # This file is distributed under the same license as the WordPress - 6.7.x - Administration package. msgid "" msgstr "" "PO-Revision-Date: 2025-05-03 08:03:17+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: GlotPress/4.0.1\n" "Language: de\n" "Project-Id-Version: WordPress - 6.7.x - Administration\n"
While updating the update system from WordPress updates the language core file but why the 6.7 branch and not the language file from/to 6.8 branch?
Replying to canic:
Hey,
I just encountered the same issue on my development environment and several of my sites.
After some debugging, I found the following:
The bug seems to be related to this change:
https://github.com/WordPress/wordpress-develop/commit/3f4d3585c31a72eab5e32afa057a458426aa42fd
The updated string can be seen here:
https://wp-languages.github.io/
I'm using the German version of WordPress. I set up a fresh Docker container with version 6.7.2 and then upgraded it to 6.8 via the admin interface.
Here's the issue: the .mo files in the wp-admin/languages folder weren't updated during the initial upgrade.
Clicking on "Reinstall version 6.8.2" resolved the issue.
I haven't had time to investigate why this happened.
Maybe someone else can look into it further?
Screenshot