Skip to content

V15: Localization property translations does not exist #6789

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jan 13, 2025
Merged

V15: Localization property translations does not exist #6789

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions 14/umbraco-cms/customizing/extending-overview/extension-types/localization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ export default {

The sections and keys will be formatted into a map in Umbraco with the format `section_key1` and `section_key2.` These form the unique key they are requested.

If you do not have many translations, you can also choose to include them directly in the meta-object:
If you do not have many translations, you can also choose to include them directly in the meta-object using the `localizations` property:

{% code title="umbraco-package.json" %}
```json
Expand All @@ -62,10 +62,10 @@ If you do not have many translations, you can also choose to include them direct
"meta": {
"culture": "en",
"localizations": {
"section": {
"key1": "value1",
"key2": "value2"
}
"section": {
"key1": "value1",
"key2": "value2"
}
}
},
}
Expand Down
12 changes: 6 additions & 6 deletions 15/umbraco-cms/customizing/extending-overview/extension-types/localization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ export default {

The sections and keys will be formatted into a map in Umbraco with the format `section_key1` and `section_key2.` These form the unique key they are requested.

If you do not have many translations, you can also choose to include them directly in the meta-object:
If you do not have many translations, you can also choose to include them directly in the meta-object using the `localizations` property:

{% code title="umbraco-package.json" %}
```json
Expand All @@ -61,11 +61,11 @@ If you do not have many translations, you can also choose to include them direct
"name": "English",
"meta": {
"culture": "en",
"translations": {
"section": {
"key1": "value1",
"key2": "value2"
}
"localizations": {
"section": {
"key1": "value1",
"key2": "value2"
}
}
},
}
Expand Down
Loading