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.

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

Conversation

mnocon
Copy link
Contributor

@mnocon mnocon commented Feb 25, 2025

Based on Support's feedback:

Hi,
I have not found anything about admin_group.languages in the docs.

# config/packages/ibexa_admin_ui.yaml
admin_group:
   .. 
    # For admin this needs to contain all languages you want to translate content to on the given repository.
    languages: [eng-GB]

Probably this information should be added somewhere ?
(...)
Any (content-) language that is used in Admin Siteaccesses needs to be added imho.

Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants