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

Jump to bottom

Fix bazinga usage #2500

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

Fix bazinga usage #2500

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4e2e98c
project_organization.md: Fix bazinga path
adriendupuis Sep 19, 2024
19cdded
project_organization.md: translations not in this dir
adriendupuis Sep 23, 2024
19a275b
back_office_translations.md: post-update-cmd
adriendupuis Sep 23, 2024
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
9 changes: 0 additions & 9 deletions docs/administration/project_organization/project_organization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,15 +28,6 @@ They can be referenced as relative to the root, for example `assets/js/script.j

All project assets are accessible through the `assets` path.

??? note "Removing `assets` manually"

If you ever remove the `assets` folder manually, you need to dump translations before performing
the `yarn encore <dev|prod>` command:

```
php bin/console bazinga:js-translation:dump assets --merge-domains
```

## Configuration

You project's configuration is placed in the respective files in `config/packages`.
Expand Down
4 changes: 2 additions & 2 deletions docs/multisite/languages/back_office_translations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ If your browser language is set to French, the Back Office will be displayed in

`ibexa.system.<siteaccess>.user_preferences.additional_translations: ['pl_PL', 'fr_FR']`

Then, run `composer run post-update-cmd` and clear the cache.
Then, run `composer run post-update-cmd` which include a cache clear.
Copy link
Contributor Author

@adriendupuis adriendupuis Sep 23, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

Mayne cache:clear for other SiteAccesses than the default one?

Suggested change
Then, run `composer run post-update-cmd` which include a cache clear.
Then, run `composer run post-update-cmd` and `php bin/console cache:clear --siteaccess=admin`


### Contributing Back Office translations

Expand Down Expand Up @@ -120,4 +120,4 @@ The language to display will then be selected automatically based on [user prefe

!!! note

You may need to clear the cache after adding new translations, before they are available in the Back Office.
Run `composer run post-update-cmd` which install your translations to JavaScript through Bazinga, and also clear the cache.
Loading