#63340 closed defect (bug) (worksforme)
"Edit site" button is no longer translated
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | 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 (11)
#1
@
7 months 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
@
7 months 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
@
7 months ago
Hi @cixtpide, thanks for raising your issue, However I am unable to reproduce the issue, the translations are working fine for me.
#5
@
7 months ago
I also don't reproduce the problem on a brand new installation with default theme and no plugins.
#6
@
7 months 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
@
6 months 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
@
6 months 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?
#9
@
5 months ago
- Resolution set to worksforme
- Status changed from new to closed
Reproduction Report
Description
❌ This report can't validate that the issue can be reproduced.
Environment
- WordPress: 6.8.1
- PHP: 8.2.10-dev
- Server: PHP.wasm
- Database: WP_SQLite_Driver (Server: 5.5 / Client: 3.40.1)
- Browser: Chrome 137.0.0.0
- OS: Windows 10/11
- Theme: Twenty Twenty-Five 1.2
- MU Plugins: None activated
- Plugins:
- Test Reports 1.2.0
Testing Instructions
- Using Playground with the info provided (WP 6.8, Language Français)
- ❌ Issue can't be reproduced
Actual Results
- ❌ Error condition doesn't occur
Additional Notes
- There are a ton of failed reproduction reports and only one successful, @cixtpide please try my testing instructions and see if you can reproduce this there; otherwise, it's just your installation. If you happen to be able to reproduce this there, just re-open this ticket to comment.
- There is something more interesting: I'm the Updates page (Mises à jour page) andI can't see the Edit Site button there:
Something says to me that he is using some sort of modifcation that is probably causing this issue or some theme.


Screenshot