LuukPeters
March 25, 2025, 11:43am
1
I have translations in a package and they are working fine. However, when I update to Umbraco 15.3.0, the translations just stop working. When I go back to 15.2.3 they work again. I think it’s bug and I’ve created an issue already:
opened 11:40AM - 25 Mar 25 UTC
type/bug
### Which Umbraco version are you using?
15.3.0
### Bug summary
It seems that… in Umbraco 15.3.0 the backoffice translations in a custom backoffice package are no longer working. Whenever I update Umbraco to 15.3.0, the translation just stop working. I suspect it's something in @umbraco-cms/backoffice 15.3.0 that changed. I can consistently get it working again when downgrading to Umbraco 15.2.3.
### Specifics
I have a custom property editor that has a number of translations. This is the English language file:
```javascript
export default {
editorv2: {
button_search: "Search",
button_clear: "Clear",
button_reload: "Reload",
input_placeholder: "Id of a situation",
...
}
}
```
It's registrered like this:
```
{
"$schema": "../../umbraco-package-schema.json",
...
"extensions": [
...
{
"type": "localization",
"alias": "ProudNerds.Umbraco.PackageName.Localize.EnUS",
"name": "English",
"meta": {
"culture": "en-US"
},
"js": "/App_Plugins/PackageName/localization/en-US.js"
}
]
}
```
This works like a charm in 15.2.3:
However, when I update to Umbraco 15.3.0, this is the result, as if the translation do not exist anymore:
### Steps to reproduce
In my own package.json, it does not matter if I have a dev dependency on "@umbraco-cms/backoffice" version 15.2.3 or 15.3.0, it keeps working when I'm using Umbraco 13.5.2. As soon as I update to Umbraco 15.3.0, the translations don't work anymore. When I revert back to Umbraco 13.5.2, everything works again.
Rebuilding my vite app doesn't work either and clearing browser cache doesn't make a difference.
### Expected result / actual result
Obviously I expect the translations to keep working. This is a minor update that should not have any breaking changes.
I was just wondering if anyone here has come across it yet, or that i’m doing something wrong.
LuukPeters
March 27, 2025, 1:28pm
2
It appears to be a bug in Umbraco 15.3.0. So I’ll wait for a fix. There is a workaround available in the linked issue.
jacob
March 27, 2025, 3:15pm
3
For anyone curious: It is a regression and is caused by a case-sensitive check. If you write the culture in all lowercase, it will work.
"en-us"
"en-US"
3 Likes
system
April 1, 2025, 3:16pm
4
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.
