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.

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

Added mention about language configuration for the back office #2639

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Added mention about language configuration for the back office #2639

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
4 changes: 2 additions & 2 deletions docs/multisite/languages/languages.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,15 +22,15 @@ However, even if work on a draft takes time and other translations are updated i
### Adding available languages

The multilanguage system operates based on a global translation list that contains all languages available in the installation.
Languages can be [added to this list from the **Admin** panel](https://doc.ibexa.co/projects/userguide/en/latest/content_management/translate_content/) in the back office.
Languages can be [added to this list from the **Admin** panel]([[= user_doc =]]/content_management/translate_content/) in the back office.
After adding a language be sure to dump all assets to the file system:

```
yarn encore <environment>
# OR php bin/console ibexa:encore:compile
```

**The new language must then be added to the [SiteAccess](multisite.md) configuration**.
**The new language must then be added to the [SiteAccess](multisite.md) configuration, both for the frontend and back office SiteAccesses.**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In our docs we have equal numbers of "frontends" "front ends" and "front-ends".
We might want to decide on one, wdys?

Once this is done, any user with proper permissions can create content item versions in these languages in the user interface.

### Translatable and untranslatable fields
Expand Down
3 changes: 3 additions & 0 deletions docs/multisite/set_up_translation_siteaccess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,10 +60,13 @@ ibexa:
languages: [fre-FR, eng-GB]
site:
languages: [eng-GB]
admin_group:
languages: [fre-FR, eng-GB]
```

With this configuration, the main English site displays content in English and ignores French content.
The French site displays content in French, but also in English, if it doesn't exist in French.
The back office SiteAccess uses all languages used by the frontend SiteAccesses.

Clear the cache by running: `php bin/console cache:clear`.

Expand Down
Loading