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
Is it possible to translate BREAD BROWSE columns? #5829
Comments
I think so, appears to look that way anyways. https://voyager-docs.devdojo.com/core-concepts/multilanguage You can also add bread to the translations table pretty easily by using "TCG\Voyager\Models\Translation" as a model, or build your own that extends it. If you search the repo here for getTranslatedAttribute The browse blade takes a datatype, which has datarows.
So you should just be able to make translation entries for your table. For example
This will give you a list of data rows with their display_name and corresponding id. You can use 'name' if you don't want the case confusion. Now go into the Bread for translations that you just made and add a new entry. Now when your user changes their locale, that data_row will get translated. |
@Emerica Thank you so much. 🙇🏻♂️🙇🏻♂️🙇🏻♂️ |
@Emerica how to create PR for new unsupported locale?
|
I think you have to commit to your own fork vs master and then submit the pull in github from your fork. |
Laravel version
9
PHP version
7.4
Voyager version
1.4.3
Description of problem
Is it possible to translate BREAD BROWSE columns when user changed his/her language in profile? So how to do it?
For example:
English -> Mongolia:
Order - Дараалал
Name - Нэр
Slug - Слаг
Proposed solution
Is it possible to translate BREAD BROWSE columns when user changed his/her language in profile? So how to do it?
Alternatives considered
Is it possible to translate BREAD BROWSE columns when user changed his/her language in profile? So how to do it?
Additional context
Is it possible to translate BREAD BROWSE columns when user changed his/her language in profile? So how to do it?
The text was updated successfully, but these errors were encountered: